homebridge-hatch-baby-rest icon indicating copy to clipboard operation
homebridge-hatch-baby-rest copied to clipboard

Not responding while Online

Open simplytoast1 opened this issue 3 years ago • 14 comments

Since the latest update - my hatch devices (Rest+ & Restore) are ignoring (or not recieving) HB commands. A simple reboot of the Hb instance restores functionality.

Both devices have a static IP and for some reason in a rollback of a previous version of the plugin seems to maintain stability although 3.2.3 only updated dependancies.

simplytoast1 avatar Aug 24 '21 14:08 simplytoast1

Can you try updating to the latest version again to verify that the latest version in fact caused it to break for you?

dgreif avatar Aug 25 '21 03:08 dgreif

Ah it seems the issue persists now in the old and new version. I have both the Rest+ and Restore set with a static IP and no obvious issue in the logs. Will reboot with Debug mode on. A simple reboot of HB fixes the issue with no other changes. Odd.

simplytoast1 avatar Aug 26 '21 03:08 simplytoast1

I ran Homebridge in Debug mode and after about 24 hours of uptime my Hatch+ and Hatch restore no longer respond to HB commands.

I looked at the debug logs but it seems nothing useful is in there.

[8/29/2021, 10:28:05 PM] [homebridge-hatch-baby-rest] Turning off Restore [8/29/2021, 10:28:07 PM] [homebridge-hatch-baby-rest] Turning on first betime step for Restore

(My testing)

After a reboot of the HB service the Hatch devices are responding to commands.

simplytoast1 avatar Aug 30 '21 03:08 simplytoast1

I'm having the same issue. The logs seem to indicate the plugin is sending commands and there is no sign of errors, but the hatch doesn't not respond to the commands. Rebooting home bridge restores functionality for some amount of time, but then will stop responding again.

FlipABit avatar Aug 30 '21 23:08 FlipABit

I am also having issues. Only new to homebridge and this is my first plug in. It worked initially then stopped responding after a few days. Since seeing the above comments I have restarted homebridge and the Rest+ is responding to commands and receiving manual state changes. I will monitor over the next few days to see if it loses connection again.

goobags avatar Aug 31 '21 10:08 goobags

Same exact issue here. I have a Rest Mini and Rest+. After starting HomeBridge, 12-24 hours later the devices stop responding to commands from this plugin. Nothing in the logs. Simple reboot of HomeBridge resolves the problem for another 12-24 hours.

williamw avatar Sep 14 '21 12:09 williamw

I monitored Homebridge over a day or so and it again lost connection to the Rest+. I have since uninstalled this plugin and rely on the Hatch app

goobags avatar Sep 14 '21 21:09 goobags

Hey all, sorry for not getting around to this sooner. I've been noticing this same issue over the past week or two and have been watching my logs closely to see if there are any errors I can go off of. Ultimately, I think I just need to refresh the connection with AWS every 8 hours or so to keep it fresh, and not count on an auth error to tell me to reconnect. I don't have time to get it fixed up today but will get something out as soon as I can. Thanks for your patience!

dgreif avatar Sep 15 '21 02:09 dgreif

Just released v3.2.4 which will automatically reconnect every 8 hours. I'll be keeping a close eye on it over the next few days, but hopefully this resolves the issue!

dgreif avatar Sep 18 '21 22:09 dgreif

Seems to be working great here @dgreif ! Proud to be a supporter!

simplytoast1 avatar Sep 21 '21 03:09 simplytoast1

In installed the plugin, added my login info, added the mac address for the baby rest, and can see the controls in Homebridge and the Home app. But the controls do nothing to the Baby Rest. I turn on the white noise and turn up the volume, but the actual Baby Rest is still off.

hsarji avatar Oct 08 '21 16:10 hsarji

Hate to open this issue again, but it seems the token issue has been reoccurring for me. Same behavior. Simple restart of the plugin fixes it.

simplytoast1 avatar Jul 28 '22 03:07 simplytoast1

I have had this pop up in and out again, I think the issue is if there is ANY interruption to the AWS back end a new token is issued.

Perhaps we can move the refresh to hourly (or at least give the user to change the default). I think that would put this issue to bed (pun intended).

simplytoast1 avatar Jan 04 '24 16:01 simplytoast1

Following up on the token refresh interval being adjustable?

simplytoast1 avatar Mar 09 '24 18:03 simplytoast1