misterleffe wrote:
In System Settings, what is the value for interval? Seconds?
/misterleffe
The interval in System Settings is seconds, when you have changed this setting - the plugin will wait NN seconds and then start publishing variables to Xively.
If you have followed the tutorial, you should not have to do anything. The
channels should be automagically updated.
So, let's start looking for the problem. As you rightly point out, since the metadata is updated - your FeedId and and ApiKey are correct. The metadata is pushed to Xively.com when the plug-in starts at boot, is enabled or when general settings are updated (Longitude, Latitude).
STEP #1 - Looking at Xively feeds
1. At this point, make sure your variables are Float (that's all I have tested with). All non-float variables you can simply "Hide from display" in their respective setting.
2. In automagicallys xively settings (/admin/settings/settingsvalue/) , set interval to something like 10 (seconds)
3. Go to Xively.com and Webtools -> Develop -> "Your Device" and wait. Pay attention to the request log, it should start building up with PUT entries as per the above interval.
- xively_request_log.JPG (15.14 KiB) Viewed 17970 times
4. When you have a few of these there, click on one of them. Hover your mouse over
feed and it turns into a link. The result should look something like this:
- xively_request.JPG (36.52 KiB) Viewed 17970 times
5. Copy/paste the Request Body and publish it here in the forum - it'll help me to debug. A screenshot of your Xively device can also help.
STEP #2 - Restart/refresh the system
To be sure everything is what it should be, follow these steps on your Pi:
Code: Select all
$ sudo /etc/init.d/automagically stop
$ sudo rm ~/source/automagically/site/plugins/xively.py*
$ cd ~/source/automagically/site/plugins/
$ wget https://bitbucket.org/MarcusKarlsson/automagically/raw/ead5b08eb03c36341f9f0f3516f69b6891f11301/site/plugins/xively.py
$ sudo /etc/init.d/automagically start
Enter you settings and make sure that Xively is enabled. Set the value for xively/enabled to "True". Make sure there are no spaces or anything.
Go back to
STEP #1 as described above.
STEP #3 - Forcing a send to Xively
Final test is to send a signal to Xively plug-in and force it to send a value.
1. Make sure the plug-in is enabled as described in STEP #2
2. Open up your device in Xively.com in one browser window and Automagically administration in another (/admin/)
3. Enter
See signals and create handler or device from them in Automagically (/signals/index/)
4. In Test signal, paste the below:
Code: Select all
xively,report:Nena:99:Luftballons;
5. Press Send button
6. At this point, Nena 99 Luftballons should more or less emerge in the Xively page.
STEP #4 - Hard core debugging
This is now the last resort and a bit technical.
1. Turn off Automagically daemon
Code: Select all
$ sudo /etc/init.d/automagically stop
2. Enable debug in xively plug-in
Code: Select all
$ sudo nano ~/source/automagically/site/plugins/xively.py
3. Replace
debug = False with
debug = True in line 9, save and exit
4. Start Automagically in non-daemon mode:
Code: Select all
$ cd ~/source/automagically/daemon/
$ sudo python main.py
5. Perform STEP #1, STEP #2 and STEP #3 and post whatever comes on the Pi here at the forum to help me to debug.
6. Reboot the system
Code: Select all
Press Ctrl-Z and execute the following commands
$ bg
$ sudo shutdown -r now
Optionally you can find the PID of the process, sudo kill it and restart the automagically daemon:
Code: Select all
$ sudo /etc/init.d/automagically start
/Marcus
:
i do My best this weekend. What I am afraid of is its dependency to other software. I would not like to have it to install software automatically nor can it crash systems that doesn't have it installed.