I have upgraded to C8 from C5 and since the upgrade I have all type of problems. I am constantly rebooting the C8 everyday. In the Preferences settings I set my devices to enable debug logging and save the changes. The next day I check the preference button and it shows the Enable debug logging not selected. This happens for most of my devices. I simple rule to turn on and off light switches works on ocassions. I am not able to view what is going on with my switches and outlets etc again due to Enable debug logging unchecked by itself.
Can you help.
Debug logging for all built-in drivers/apps and most community ones are normally set to only log for 30 minutes.
2 Likes
I taught everytime a device was actuated it made a log of the time it turn on-offf etc.
You'll want to go to the device page and look at the Events tab. Note that, by default, an event is only recorded when the state changes, i.e. off to on or on to off.
You can also turn on debugging on the rule itself if you want to see its logic path.
1 Like
If a device has a setting for Descriptive Logging, that will stay enabled until you decide to disable it.
Debug Logging, which is much more verbose, only stays enabled for 30 minutes as mentioned by @thebearmay.
3 Likes
Thanks I will try that. maybe you can help with another question on the C8. I have created simple rules to turn on and off switches and the majority of times it does not work. If I create a routine using Amazon alexa for the same switch it works perfrctly. Why does Hubitat C8 constantly needs to be rebooted.
Please make a separate new post for this issue so that it gets attention. In that post you should include:
- A screenshot of the rule that isn't working
- A screenshot of the logs filtered to show the devices and rule when the rule does not work (you should enable logs for the devices and rule)
- Details of the devices that aren't working (make/model)
The above will enable others to assist with your issue. The hub should not need rebooting regularly.
2 Likes
Also please post your z-wave details page in it's entirety. (use windows snip)
What channel is zigbee on? What power is it set at?
1 Like
There are a few possible causes and as many have mentioned debug logging ia not really ment to run continuously. In many driver code is in place to intentionally disable logging after a short period generally 30min
Lets start at the beginning.
Are the devices no longer controlable after 24 hours or are rules you have creates failing to execute.
Why are you rebooting the hub? Is the hub unresponsive? Can you get to the diag page if the regular ui isn't working? If the hub is responsive is it juat the rule is failing and you can still control the device or is the device simply unresponsive?
If you are rebooting the hub are you doing it from the menu, or just pulling power? If pulling power please reboot with the advanced option to rebuild database on reboot.
If devices are simply becoming unresponsive what wireless tech are they usung? (Zwave, zigbee, wifi)
Please provide the device info like make and model for problematic devices. As requested please provide the zwave details page if that the wireless tech used as well.
You had allot of hardware changes going from a c5 to a c8. You went from a zwave 500 radio to a zwave 800 radio and you went from a zigbee 1.2 radio to a zibee 3.0 radio. There were some non standard zigbee devices that didn't like the new radio.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
