(added for clarity)
Setup:
Phillips Hue Bulbs
Blue switches
Hubitat
Homebridge
Homekit
Both the switches and Hue bulbs are connected to Hubitat (no Hue hub)
This setup has been working well for months
This evening I came home and none of my switches are responding. All of my switches are hooked up to hubitat and connected to Apple Homekit via Homebridge.
When I press the switch, the LED bar works as if it is turning on and off the lights, but the lights do not turn on or off. When I check the logs in Hubitat, there is no logging of the button being pressed.
When I turn the light on or off in either Homekit or in homebridge. The lights do not turn on or off, but the on or off command is logged in hubitat.
When I open the switch device in hubitat and use hubitat to turn on or off, nothing is logged (very strange), but if I mess with the LED (in hubitat), it logs it (the LED does not follow the command though).
If I switch on the lights (bulbs not switch) in hubitat they respond fine.
Iām at a loss here and would appreciate any advice.
I just factory reset one switch. When I re-added it, hubitat recognized it.
With āsmart modeā disabled and it set to āon/offā switch mode, the light now responds, however it still appears to think that it is a dimmer (the lights flicker between on and off).
When I switch to āsmart modeā enabed, the light no longer responds.
For a separate, non-factory reset switch, when I attempt to set āsmart modeā to disabled and set it to āon/offā switch mode, the switch will not change these settings after a save. It continues to not work.
You say āsmart modeā several times, but I think you may be referring to āsmart bulb modeā? Thereās no āsmartā (vs ādumbā) mode per se.
I think @MRobi and I are both heading in the same direction with our questions hereā¦
If the switches are in SBM and controlling zigbee bulbs, and you have multiple switches suddenly not responding and showing nothing in the logs, you need to be looking at your zigbee network.
Check for interference with things like WiFi. I believe hubitat has now integrated a zigbee map and Iād bet money if you check it youāll see a bunch of dropped devices.
How many zigbee router devices do you have? (aka how dense is your zigbee network?)
But there is no logging in Hubitat correct?
From what Iām gathering here, Hubitat is acting as your zigbee coordinator, and homekit/homebridge are connecting to Hubitat to control devices. So when you are toggling something in homekit/homebridge, it is logging that attempt, sending the command to Hubitat which has no logs indicating itās passing that along to the switch itself.
When Iām talking Zigbee map, Hubitat recently launched a visual tool for this (Not my map below, I use Home Assistant)
Do you know which channel your wifi router is on and also which zigbee channel your hubitat is using? Also, how close to each other are they? Zigbee and WiFi compete for the same frequencies and channels can overlap which can cause messages to get dropped, devices to drop off the network, etcā¦ Unfortunately, this kind of stuff can happen in smaller networks. But thereās lots of things to help improve it. So letās start with checking the channels on both and see what weāve got.
Sorry for being unclear, the logs in the original post are from hubitat. I have attempted to control the switch (on and off) using both homekit and homebridge. The logs on hubitat for the switch (device logs) show that the switch has received the command (as shown on the bottom of the hubitat log shown on the original post), but the lights do not actually turn on or off and the physical switch does not change itās LED bar to match that state.
Could be me misinterpreting the original post as well.
This may be a simple setting.
Unsure what it looks like in Hubitat, but look for something around remote protection. This prevents the switches from acting on remote commands.
The wifi router is using Channels 5 and 40
The Zigbee is Channel 25
All the switches that are in SBM and failing are within 30 feet, including some that are within 10 feet of the hubitat. The Hubitat and wifi are connected, so they are in close proximity to each other.
Thanks @mark.kunitomi for sharing your issue. You just gave me hope that possibly we share the same struggle. I donāt think we should mark it as solved yet. You propose a work around but what if, like me, you have 50 switches, and many groups and much automation. Reseting everything, wasting a long day, and praying it wont happen again drives me a bit crazy.
I have a very different setup but am experiencing the exact situation. I use the Aeotec Hub v3, not Hubitat. andI donāt have any SMB config. My network that was working just fine, all of a sudden stopped. All switches work manually, they all appear to be online but none of my scene automation is working. Sending commands through SmartThings has 0 effect. Like you, event logs have stopped to capture anything since about August 15.
In term of debugging, I added a non-provisioned switch to my hub, no problem there, but, like for the other switches, unable to remote control. I unpaired that switch and paired it then with a faraway secondary Samsung SmartThings station, and then I able to remote control it. Existing Zigbee binding is still functional. I also changed the Zigbee channel a few times without any difference. I believe that the Zigbee mesh is still functional, there is however something going with the driver.
I am getting more and more the sense that I will have to wipe my Aeotec hub and that the issue will then be gone. Yet, why did it happen? Was there a firmware update that messed up everything? FYI Edge driver available through the huib is 2023-08-17T22:28:06.820642294
I also changed the Zigbee channel a few times without any difference.
Any time you change the zigbee channel on your coordinator, all devices will need to be re-paired.
Each channel represents a slightly different frequency. Your devices were all paired on frequency A, but now your coordinator is communicating on frequency B.
It seems highly unlikely that it was a connectivity issue for my problem.
Logging did occur on Hubitat from remote activation via HomeKit and homebridge, but didnāt actually trigger the lights. I think that my post have been pretty clear in that respect.
