I too use a Hubitat C8 (non-pro) hub, but I never had a lot of luck getting them to work together, mainly due to the available drivers only being able to handle one segment at a time.
Anyway, you can troubleshoot by looking at the device logs. You may need to turn debug logging on the device page. If the reboots are in regular intervals, you may have a cron job running that reboots or crashes the ESP32.
Thanks for the input. Iāll definitely take a look at that when I get back home. Iām just getting started with both Hubitat and WLED.
Interestingly, I after looking through the Hubitat literature to insure comparability, I bought my first smart switch. But despite all my trying, I canāt get those two to recognize each other. Yet, the Hub/WLED - Iād be happy right now if they would just leave each other alone - but of course they seem to be trying to link up or something!
Instead of the driver, I have a rotary scene switch and use it to send HTTP API commands. This way you donāt need the driver, but you canāt react to changes initiated elsewhere. This is some of what my rule machine looks like, so you cn get an idea:
Had some time to do some testing⦠just as a watched pot never boils, I guess a watched WLED never reboots! I let things go for an hour or so and I did get one reboot. (seemed like I was getting reboots 4-5x per hour initially, which led to this post)
Curiously, the reboot happened right at a 5-minute time interval⦠1755, IIRC. It seems the hub is running a āperiodicCleanupJobā every 5 minutes, so possibly that had something to do with it. (Iāve barely started with the hub - so nothing custom running)
I tried updating the hub and WLED to latest versions and even latest beta for WLED. I ran until about 1840 with no additional reboots. Then it was time to turn the lights on for the night. Out of caution, I shut down the hub and everything ran through the night fine.
The next day, I wanted to work on some additional effects, so was clicking various controls in WLED and got another reboot⦠though Iād call this more of a ācrashā because the hub wasnāt even on at the time. After more testing, it seems like WLED does not like running the āPeekā function while changing effects paletts, etc.
So overall, maybe I was getting 1-2 crashes from the hub and 4, 5 or 6 from WLED/Peek combo. Anyway, hub off for now and donāt do too much while WLED is actively running!
It sounds like there might be some interference or a power issue causing the ESP32 to reboot when the Hubitat is running. Here are a few things you can check:
Power Supply: Ensure that the ESP32 is getting adequate power. If the Hubitat and the ESP32 are sharing a power source, it might be worth trying a dedicated power supply for the ESP32.
Grounding: Make sure that the ground connections between the Hubitat and the ESP32 are solid and common. A poor ground can cause instability.
Wi-Fi Interference: Check for Wi-Fi interference. If both devices are on the same frequency channel, they could be causing issues. Try changing the Wi-Fi channel on your Hubitat.
Firmware Updates: Ensure both the Hubitat and the ESP32 are running the latest firmware. Sometimes, bugs are fixed in newer versions.
Network Configuration: Check your network settings, such as DHCP leases or static IPs, to ensure they arenāt conflicting.
Serial Monitor: Use the Arduino IDE or a similar tool to monitor the ESP32ās serial output. This might give you clues about why itās rebooting when the Hubitat is running.
Library Conflicts: Ensure that any libraries you are using in your WLED setup are compatible and updated. Conflicts can sometimes cause instability.
If you try these steps and still face issues, please share any error messages or behaviors you observe, and we can troubleshoot further!
Thanks for the info. Iāll put some additional info inline below.
Definitely no sharing of power source. The ESP is on a completely dedicated 5V power supply with large filtering caps on-board.
The ESP and Hub are 30 feet across a room to each other, so they donāt share power or ground. Though the ESP is grounded to the 12V/40A power supply for the LEDs. Actually everything on the LED side shares a common ground. ā¦power supplies, ESP, SSRs, etc.
Iāll double check. Possibly they happen to default to the same channel.
Done! Still have the issue.
I set the Hub and the ESP to have their own unique static IP addresses from the beginningā¦though still have the issue.
OK, Iāll look into it.
This is basically the stock / OEM config for the Hub and stock / OEM config for the ESP.
Interestingly, yesterday I noticed the WLED lights were on during the day. Curious, I thought so I went into the web interface and shut them off. About 15 minutes later, I noticed they were on again and shut them off again. Within a few minutes they were on again. Then it hit me!
This is what happens when WLED runs a certain preset on boot. I started looking around and I guess we had a short grid power blip which rebooted the Hub and it was once again causing the ESP to reboot at 10-15 minute intervals.
Adding my experience here. I also have a Hubitat C8 Pro and itās also causing my WLED light to reboot constantly. Also around the 5ās. For example it last restarted at 9:55.
Iām thinking it has something to do with that āclean-up jobā running on the 5ās. Presume your Hub is defaulting to the same? I am wondering if the Hub is sending a command to the effect of āHey, stop bothering meā¦why donāt you reboot and try from the beginning.ā which causes the ESP to reboot and try again.
I almost wonder if it would be better to try and pair the Hub and the ESP.
Had a little more time today to goof around with this. Since I had the Hub turned off this past week, I had almost 7 days of up-time on the WLED ESP. So the WLED system on its own seems to be stable.
I started up the Hub today and grabbed what seems to be a workable WLED driver at
Then I added the WLED ESP as a device in the Hub and provided the IP address of the ESP. This seems to have linked the two and the Hub reported some info from the WLED ESP. The Hub doesnāt really seem to control the ESP - at least not yet. Iām probably goofing something up with that⦠but I really donāt need the Hub to control anyway. I really just want it to leave the ESP alone!
Another thing to keep an eye on is that every time I make a new preset, the āApply at bootā option is automatically checked. So you need to uncheck that⦠everyā¦singleā¦time. Or else you could write a preset which will pop on when WLED reboots - and suddenly you get the āRandom turning onā behavior again.
Anyway, itās been a bit over 6 hours now and have not had a reboot yet. So fingers crossed!
@gitter2741
Ok, so my husband did some sleuthing on the Hubitat end. Apparently this issue started happening a few months ago as a result of an update that was meant to make the HomeKit connection more reliable. This created a mDNS āstormā that started interfering with other devices, particularly the ESP boards.
The good news is people have found a temporary workaround until the Hubitat fixes their software. It is basically to disable Bonjour on the Hubitat. We switched that off and see how it goes.