Ludicrous0251

@ Ludicrous0251 @piefed.zip

Posts

66
Comments

275
Joined

6 mo. ago

4h ago

Chat am I cooked?
Jump
2

Ludicrous0251 @piefed.zip 4h ago
Have you thought about just putting the episodes on a thumb drive instead? Most things that can play DVD/BD can play videos from a USB.

5h ago

Teams’ invasive Wi‑Fi tracking sparks backlash as users say Microsoft crossed a line — “There must be a team at Microsoft tasked with making Teams worse”

Jump

Ludicrous0251 @piefed.zip 5h ago

If people moved to Linux

When users connect to their organization's WiFi...

You think my employer would let me use Linux? Creeping on employees is how management feels important.

I wouldn't use Teams personally unless under extreme duress. Unfortunately professionally it is the norm.

Can you not see in the activity log, either of HA itself or of the device, what is causing the action to be carried out?

Normally, yes, it would say what automation is triggering it, in this case it does not seem to be triggered by an automation.

The devices being rebooted are not associated with any on/off automations, but the device that used to receive those commands is no longer connected.

If it is a backlog of stuff, maybe restart Home Assistant, or better yet, the server itself

Done and done. FWIW, the on/off behavior seemed to continue during the reboot indicating it may be lurking in the ZigBee network?

What's also possible is that something is up with the electricity in your home. Maybe these devices are getting power surges or cutouts and defaulting to whatever you have that Power On setting set to.

It's too organized for that, and status is toggling off/on not unknown/on. Also the impacted devices are on separate circuits and seem to be impacted one-at-a-time.

Also also, voltage seems generally stable:

Last thing I can think of is an errant Zigbee controller. Maybe it's picking up Bluetooth or WoFi signal interference and sending garbled messages to anything that'll listen.

I'm generally in agreement, what's suspicious is it is very closely following the on/off pattern of a previous, long disabled, script (on/off/on/off in quick succession followed by ~1h on, then repeat).

What I don't know is how to find the errant device - if its truly the controller, I have a replacement on order (guess I gotta upgrade to the ZBT-2... twist my arm...). If it's a relay somewhere in the chain thinking it's passing along useful info then I have to reset everthing.