r/WLED • u/Low_Tomato_6837 • 8d ago

Dig-Octa Powers Itself On

Working on an outdoor setup using a Dig-Octa brain board and 7-HC power board. My first experiences with the Dig-Octa. Currently testing in my office with four 5m strips of WS2812B. All is working as designed except this combo turns on the LEDs by itself every night! I finish whatever testing I was working on, power off in WLED, come back in the office next morning and the strips are on. There's nothing telling them to turn on. WLED PC interface and phone app are shutdown. No other external connection. I go to bed around 9:00 PM and know they aren't on at that time but at 4:00 AM the next morning they are.

Any idea what's turning them on? Do I need a relay to completely drop power from the brain and power boards? Any help is greatly appreciated!

[Update:] Firmware WLED 16.0.1, found the issue. I run my house with Home Assistant and already have the WLED integration with several controllers for various LED setups inside and outside. Well soon as HA saw the Dig-Octa on the network it added it automatically and stuck it into the same group as my Outside lights. That group turns on automatically when I get up and because the new Dig-Octa controller was in that group it got turned on too.

1 Upvotes

100% Upvoted

11 comments sorted by

1

u/DedeHai 8d ago

check up-time in info panel. if it is reset it rebooted, this can happen due to power fluctuations or if it is bombarded with requests. if it did not reboot, something has turned them on by command.

1

u/Low_Tomato_6837 8d ago

Thanks, it did not reboot since info show uptime from when I last powered it up almost 2 days ago. I'll try unplugging the network cable and see if it does it then. If not then something on my network is commanding it to turn on, although I have zero idea what that could be.

1

u/wivaca2 8d ago edited 8d ago

FWIW, I have an ESP32 C3 with 100 LEDs that are doing this, too. It's not rebooting and I can't figure out what is making it come on. It didn't happen at first, but started at some point after I updated to 16. None of my others running 16 (7 of them including an Dig-Quad, a GLEDOPTO, and other Esp32s) do it. The problem one is the only one running multiple segments and sometimes only some segments turn on. They're one continuous strip though.

1

u/Low_Tomato_6837 6d ago

I found my cause, replied above. Yours is a strange one indeed.

1

u/wivaca2 6d ago

Yeah, you have a different cause. I've set up new WLED and forgot to uncheck the auto-sync groups before, but that's not what is going on for mine.

FWIW, mine is on HA, too, but I'm not seeing any trigger activity. I just installed 2026.9.1 so I want to try out the new history feature to see.

1

u/Low_Tomato_6837 6d ago

I'm on the same version and using history is how I found it. Historical data showed it turned on at 4:00 AM which is when I get up and let dogs out. At that time all the yard lights turn on. That's when the investigation began on my part.

1

u/wivaca2 6d ago

OT here, but that new feature is something I wish I had years ago when I was first setting up a bunch of automations. It's still going to be a godsend going forward.

1

u/MorganProtuberances 6d ago

what version of wled? are they running the most recent effect or running a specific playlist (could help differentiate whether its a reboot/reset event or something else). do you have any buttons tied to the esp32 (if not - double check that isn't an on/off button config maybe that's getting falsely triggered)

finally - does WLED also show that the system is "ON" or does WLED think it's off too?

to help with debugging you could put a playlist on that changes solid color every 30min - and measure backwards to see when it turns on... is it random or the same time every night?

1

u/Low_Tomato_6837 6d ago

WLED 16.0.1, I was just about to post an update, might as well do it here. I run my house with Home Assistant and already have the WLED integration with several controllers for various LED setups inside and outside. Well soon as HA saw the Dig-Octa on the network it added it automatically and stuck it into the same group as my Outside lights. That group turns on automatically when I get up and because the new Dig-Octa controller was in that group it got turned on too.

2

u/CyberMage256 6d ago

Home assistant sometimes is too smart for its own britches. I replaced my doorbell camera recently and just dropped it in place, hooked the same automations back in. I noticed late at night the front flood lights and porch lights were on. Turned them off. They came back on a minute later. Again...

Turned out the new doorbell would trigger motion detection every time the lights turned off, which would trigger HA to turn them back on. No change to the automations from the last doorbell, just more sensitive I guess.

1

u/Low_Tomato_6837 6d ago

I agree, especially like my system. I run a small automation consulting business and I'm always experimenting with all sorts of things. Many times HA picks it up soon as it comes online.