Hi,
I'm working on a project to monitor my temperatures using the comet blue devices. All is OK so far, I have a ll my scripts and get a Cacti/RRDtool graph.
Here's my issue: I call all my devices ervery 15 minutes to get a backup (and I extract the info from there in bash). Doing this I notice that my devices have screwed up schedules. Looking closer there are 2 scenario: one of the steps is missing and so my devices are ending up closing when they should open - a timing over 24 appears (so the devices should open/close at 37:20...)
Could this be fixed? Can I help with the debug? (the same happens when you read a measure rather than taking a backup, this is why I moved to backup at first place)
BR
Benjamin
Hi,
I'm working on a project to monitor my temperatures using the comet blue devices. All is OK so far, I have a ll my scripts and get a Cacti/RRDtool graph.
Here's my issue: I call all my devices ervery 15 minutes to get a backup (and I extract the info from there in bash). Doing this I notice that my devices have screwed up schedules. Looking closer there are 2 scenario: one of the steps is missing and so my devices are ending up closing when they should open - a timing over 24 appears (so the devices should open/close at 37:20...)
Could this be fixed? Can I help with the debug? (the same happens when you read a measure rather than taking a backup, this is why I moved to backup at first place)
BR
Benjamin