Is Xively fully functional
23 November, 2013 - 13:55
I would be very grateful if someone could confirm Xively is fully functional. I have read on the forum that there have been some issues with Feed ID number of 10 digits and graphs not working. I have just set up Xively for the first time and run into a problem.
Please note I am a relative novice to HAH.
My problem is once the data is up loaded to Xively (5 different 1 wire temperatures) they are registered and seen on Xively, but after a while, all uploaded data is the same as the first. i.e. same temperature straight line graphs. Each Xively Graph says “Last updated a few seconds ago”, so one would assume with the latest data, but it’s not. Bizarrely if there is a major change in temperature this is then uploaded ok, but again after a while this gets stuck on the same value.
I have observed the following:-
If you are issued with a 10 digit Feed ID and enter this into the Xively Web interface and “save” the configuration, only 9 digits are visible. The LSD is missing and HAH WEB I/F Graphs do not populate. If you are issued with a 9 digit Feed ID all appears to be OK including graphs.
I have to reboot the HAH to get the uploading process started. Saving then Restarting do not have this affect.
Also while configuring the Xively my HAH configuration has been corrupted a number of times. I have seen on the forum, that I am not the only one to have experienced this.
HAH ver 310/3.4
Many thanks.
24 November, 2013 - 04:29
#2
I've pushed a beta to see if
I've pushed a beta to see if this will fix the xively issue. Try 310.1
Brett
24 November, 2013 - 10:39
#4
Have you set a large
Have you set a large hysteresis on the temp sensors?. Do you see xap messages showing different temps than on xively? If it says updated on web then hah is sending data, need to understand if it's missing data or data not generated in first place.
Garry
24 November, 2013 - 10:44
#5
A little background on the
A little background on the operation of the xap-xively feeder.
The temperatures sensors are generating an event on every .1 of a change, however data to xively is only pushed every 1 minute. The way this timing difference is resolve is for xap-xively to monitor all the events and constantly update its internal cache to record the value. When the time comes to push a new reading to xively the last value from each sensor is pushed up.
If you temperature hovers from 15.5->15.8->15.5 its possible that 15.8 won't be see if this wasn't the latest value. You're temperatures reading have to change and hold for at least a minute before you'll see something different being reported to xively.
If this isn't your issue then at least are know aware of the way in which is must operate.
Possibly xively should monitor all readings between its reporting cycles and push the average of all value seen in that time. So in my example (15.5+15.+15.5)/3 = 15.6
How to run in debug mode.
At the command line you can manually start a process but first you must stop the process so you can restart it.
# kill xap-xively
# xap-xively -i br0 -d 6
For example you will see a 1-wire sensor constantly reporting in until such time as xively determines it time to push the latest value up. For me I see this.
[inf][dscache.c:87:addFeed] Adding Feed 1970985268
[inf][dscache.c:109:updateDatastream] feed=1970985268, id=0, tag=Office - Temp, value=28.40
[inf][dscache.c:109:updateDatastream] feed=1970985268, id=0, tag=Office - Temp, value=28.30
[inf][dscache.c:109:updateDatastream] feed=1970985268, id=0, tag=Office - Temp, value=28.40
[inf][dscache.c:109:updateDatastream] feed=1970985268, id=0, tag=Office - Temp, value=28.30
24 November, 2013 - 14:30
#7
How xap-xively feeds
The xap-xively service watches out for xAP messages that conform to the 'source' and 'class' filters that you setup on the 'Xively' tab on the HAH UI. When it finds a match, it pushes up the data as described by Brett.
If you specify a hysteresis on the 1-wire setup, you are effectively asking for the suppression of xAP messages that represent a smaller increase/decrease than the hysteresis value. No messages = nothing for xap-xively to catch. You can see the code for this at https://code.google.com/p/livebox-hah/source/browse/trunk/userapps/hah/xap-livebox/ini.c#84
If you want xively to be updated with 0.1C changes, then don't specify a hysteresis on the 1-wire setup. You can develop your own Plugboard script that applies your own hystersis value (or some sort of moving average) as part of the overall control for your heating.
Also, remember that the DS18B20 parts have an accuracy of +/- 0.5C Two DS18B20s, sitting side by side, will often give different readings.
Cheers,
Derek.
25 November, 2013 - 13:43
#9
ON/OFF works, but with a slight quirk
I setup a feed to monitor a relay, just as you described. Restarted the xap-xively service. Didn't see any sign of the relay state in the messages being posted to xively.
Then, I used the HAH UI to toggle the relay. After doing this, the relay state was included in the xml feed to xively. 0.00 for off and 1.00 for on.
This behaviour is consistent with the 'data cache' (that is used to track endpoint values) being empty. We are, after all, filtering on 'events' and until the relay changes state there are no xAP events to catch.
However, it might be better if the cache was initially populated via a query.
I'll have a chat with Brett & see where we want to go on this one.
Cheers,
Derek.
25 November, 2013 - 20:48
#11
Glad your getting on well
Glad your getting on well with it all.
i also use a script for thermostat setting so can send you my implementation for examination if you'd like.
when you say your purchasing a jeenode, I assume you meant HAHnode from the shop ;)
On a serious note though, these are great when you get into them, I use them now for switching relays on my heating and water. Very reliable, wireless and remote. Perfect.
Brett and Derek really have built a do everything box here, just needs some dedication to understand it all!
G.
Thanks for the detailed info.
I've been a Pachube/Cosm/Xively user, so my experience (as a 'legacy' user) might be different from yours.
As you mention, there is an issue with the 10digit FeedID. I created a new FeedID and was assigned a 10 digit one. The ID was entered on the HAH UI and correctly stored to the xap-livebox.ini file.
However, subsequent display on the HAH web UI was truncated to 9 digits. Also, the HAH graphing was broken for the same reason.
All looks good on the xively site. Graph updating and data points as expected.
I've raised a code issue https://code.google.com/p/livebox-hah/issues/detail?id=50 for the 9/10 digit piece.
Do keep a backup of your xap-livebox.ini - it's a textfile, so easy to work with.
Less sure of the 'not the latest data' issue that you report. You might run the xively service in debug mode (-d6 is a reasonable level) to see what it's actually posting to the xively service.
Cheers,
Derek.