Derek has kindly provided a replacement PCB for the Livebox, after I fried the old one.
I wanted to post the internal temp to Pachube, but having no luck.
Have set up a new feed, and provided the API key, but the Pachube Debug Info isnt even registering an attempt to post to it.
(My existing Current Cost, not yet attached to HAH) is posting OK.
XFX Viewer doesnt seem to be sending anything, although I did have a Pachube heartbeat, but that seems to have disappeared now as well.
Any thoughts?
Member for
16 years 10 monthsSounds like a configuration issue somewhere
If xFXViewer is not seeing any 1wire events I'm not sure why you think Pachube would see them? I would proceed in this order
At each step do not proceed to the next until each has been completed.
With the information you've supplied is pretty hard to figure out what you've done, not done, or where you are at. Pachube will only POST when it has receive some valid data, if your 1wire sensor is not setup there is no reason for it to post as no data would have been received by this service.
Brett
Member for
15 years 2 months1 wire ok
1-3 are all working, with Viewer observing the correct temps. Thats where it stops though - should there be any Pachube events for it see? How can I check if the service is running on HAH?
Member for
16 years 10 monthsI don't understand
Pachube does not generate events it receives events generated from xAP endpoints. If the pachube screen is allowing you to enter datastreams then the process is enabled. If the 1wire sensors are setup and reporting information on the web page then you have a pachube configuration problem if they are not appearing on pachube. Have you looked at the wiki page for pachube configuration and setup? Which part is confusing?
Brett
Member for
15 years 2 monthsViewer
Sorry, I meant does the HAH Pachube sevice generates event - I had seen a Pachube.heartbeat,but a reboot has made it disappear. I'll upgrade to 301, and start a new feed.
Member for
16 years 10 monthsI'm really confused!?
You seem to be trashing about instead of make educated decisions about what you are doing why you are about to do it because I can't understand clearly where you problem is. Every process generates a heartbeat message this is part of the xAP specification. Sorry I'm missing your point. What is your point?
Yes a reboot will make it disappear for about 30sec whilst the HAH reboots and then when the xap-pachube process startup again so too will you see heartbeat messages from it. These are part of the Auto-discovery nature of xAP. Updating to 301 isn't goign to solve your problem if indeed you have some sort of problem with its configuration. In fact now you are just going to get even more options and more confused about how to set it up.
Brett
Member for
15 years 2 monthsMy point is
Member for
16 years 10 monthsCheck the logs
Check /var/log/xap-pachube.log to see if there is a valid reason for it shutting down.
Try starting tit manually and see what output you get.
Brett
Member for
15 years 2 monthsWorking....
Member for
16 years 10 monthsFTP and Pachube
These are most definately in now way connected at all. Even their startup scripts are separated. Perhaps you had a xap-livebox.ini corruption and by starting another service it caused the file to be re-read and re-written removing whatever corruption was in there. I'm at a lost to explain why restarting FTPD would have any affect on xap-pachube at all.
Brett