![]() ![]() It appears that when activating the physical switch (after an unknown period of time), the Shelly is sending the GET request as it is configured to do so, but Hubitat doesn't respond straight away with HTTP 200. Once that first use of the switch has finally gone through after the initial delay, then all subsequent uses of the physical switch work with almost instantly.Īfter lots of trying to debug many different configs (and firmware updates) in Hubitat and the Shelly itself, all with no improvement, I decided to switch my focus to seeing where the actual delay was being introduced by doing a wireshark capture and this has revealed where the problem may be. What we are seeing is that after a unknown period of time of not using the physical switch, the first use of the physical switch has a delay of approx. The specific shelly devices I am having issues with are the ones that are in "detached" mode which means that any action taken upon a switch press is essentially handled by Hubitat (specifically button controllers), rather than the switch directly controlling the relay. The setup I have is a C5 in vlan X and my Shelly devices are in vlan Y. It seems to have started occurring since updating to either 2.3.4.x or 2.3.5.x, as I was running 2.3.3.x for a very long time without issue, but I needed to upgrade to fix a few other things. As time has gone on, this delay is starting to drive everyone in the family insane. It was originally picked up by my wife who mentioned it one day so I'm unable to fully pinpoint when it started, and at first I thought it was hub resource related, but I graph hub resources in Grafana and couldn't correlate anything here. I've been having issues with a couple of my Shelly devices (using built-in Hubitat drivers) recently.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |