I would like to push the low battery alert/trigger to Cosm so I have added dbzoo.livebox.jeenode:immersion.lobat | xAPBSC.event | input.state | text | to my HAH Pachube Settings however nothing seems to be pushed to Cosm I was expecting to see an on/off state published?
Member for
15 years 1 monthState change
Does it need a state change to fire an update before anything gets sent?
Not sure. Just a thought.
Member for
15 years 11 monthsjust an idea
I can't see the lobat defined on Cosm - at the risk of insulting your intelligence you did define the new tag there as well?
Mine is at - 0 for off 1 for on - at least that's what I think it is - never having had a lobat signal.
https://cosm.com/feeds/13194?pachube_redirect=true
Regards
Kim
Member for
14 years 7 monthsHi Kim, no I haven't set it
Hi Kim, no I haven't set it up in Cosm only because with all the other feeds from HAH they automatically published into Cosm as soon as HAH push data to Cosm, are you saying the lobat needs to be setup differently as it won't do the same as the other feeds from HAH?
Member for
15 years 10 monthsI think you will find
They only change/are updated in cosm after a (hysterisis) change.
Dean
Member for
14 years 7 monthsIs there a way I can send a
Member for
15 years 11 monthsdid some experimenting...
First of all it is interesting that you defined your feeds just by sending data - I had always assumed you had to do it yourself using
console and edit.
Secondly I don't think it is the hysteresis - I think that only applies to the one wire - if I click on the temperature lines on both your and my
feeds I can see lots of times when the data is the same yet a time stamp is recorded.
I HAVE established using the Cosm debug to look at what was actually received, that if you remove the battery to the hahnode everything - including
the "moved" and "lobat" state gets sent. So maybe that is the solution. Rebooting the livebox doesn't do it - I have one livebox for the hahnodes
and another doing the upload (my non experimental livebox) - rebooting either doesn't stimulate sending messages for the "state" feeds.
Finally the COSM api documentation - under FEEDS - UPDATING A FEED gives information on simulating data posting:
"If your client is unable to make PUT requests, then this can be simulated by a POST request and a "_method=put" parameter, e.g. by POSTing to http://api.cosm.com/v2/feeds/1977?_method=put"
Hope that helps.
Kim