I won't go through all the gory details, but I've determined that (a) I can't control my HB fan controller via Hubitat when debug logging is turned off, and (b) I can control my HB fan controller via Hubitat when debug logging is turned on.
Initially, this sounds fantastic! I can just leave debug logging turned on for the device, and everything works the way it should. Unfortunately, something turns debug logging back off without my input.
Im thinking of buying one of these for my fans, so im following. Im hesitant to get one though because issues like this. I also have zero Zigbee and would have to build out Mesh for these..
That said, everything i have read says that this device requires a zigbee repeater in the same room or it will not stay working. Do you have a repeater?
That said...with the debug logging switch turned on, the controller integration works great. It feels like there's some code path or another that isn't working right with the switch off, which makes me hopeful that it's fixable.
This is strange. I have the HBFC running using the native Hubitat driver and have no issues with the debug logging turning off. Most Hubitat drivers turn off debug logging automatically after 30 minutes. This helps to keep the live logging from getting clogged up.
Tagging @mike.maxwell as he is the Hubitat Driver SME.
I currently have the child devices enabled. I'll poke around a bit tomorrow and see if I can narrow down the exact circumstances that produce the behavior I reported.
I use the child devices too. Are the child devices the ones having an issue? Or is the parent device not working without the debug logging enabled? I have seen an issue with this device in the past where the child devices end up with device network IDs that do not correspond correctly to the parent device. This is caused by the HBFC device temporarily losing its connection to the hub, and when it reconnects it somehow seems to change its device network ID. This then causes the parent to not be able to find its child devices to keep them updated.
I am not saying that this is definitely your issue, but others and myself have seen this issue. In order to fix it, turn off the preference to use child devices and click save. Then turn it back on and click save. If you end up with a grand total of 4 child devices (2 fan and 2 light) then you are another victim of this issue. You can then delete the original two child devices manually and use the new ones.
Hubitat will need to address this issue by changing how the parent device assigns device network ids to its child devices. If the parent’s DNI is not used as part of the child devices’s DNI, this issue can be avoided.
Well, things have been stable all evening, with child devices enabled and debug logging off. I’m not sure what, if anything, changed, but I’m happy for now.
Sorry to have raised a false alarm, and thanks to all who pitched in to help!