Odd that it was tripping over that line, the unschedule should remove the “5 minute poll” before we re-create it. I assume to stop any running concurrently from from creating too many polls.
I’ve been having a 1:1 chat with barron and was going to do some live logging together but we haven’t found a time that works. After that hopefully will have a “stable” version.
re polling too frequently & affecting battery - this isn’t an issue because we are polling the Hive web service, not the TRV’s themselves. So the TRVs via their hub update Hive web, we update against Hive web…
No problem, took me a little while to figure it all out with being new to this but once I figured out how to use the IDE etc, it was pretty straight forward.
@bibbleq I agree it is strange why it trip over on this line of code, now that I understand what it is for. Still, removing it seems to have done the trick
Tried your code alternation and my TRVs are still going offline after 15min
But when they are online I’m getting no data from the TRV’s so makes little difference I guess.
Infact it seems anything on Hive Connect now goes offline randomly even the Thermostat and Hotwater which used to work flawlessly.
No, devices in the Hive App were fine only in Smartthings App did they report offline.
Wonder if the device has changed, only purchased mine last week.
Figured out what was causing it, never had problems before but it turned out to be proximity to other hubs I have. By moving the Smartthings, Philips Hue and Hive hubs apart instead of stacking them all is well now.
anyone got an update on this NULL issue, I seem to be getting it now.
I believe it has happened as I have removed a device from HIVE before removing it from the hive (connect) Smartapp, this left an orphan device in Smartthings, which I removed manually, however this has left a NULL device in the connect app.
Anyone know if there is a way that I can clean up the device list so I can add a new bulb that I have added?