Enheter växlar läge vid omstart

[ChristianNiklasson]

Jag har ett antal enheter som vid omstart tex vid HA uppdateringar har en tendens att växla läge, jag ser inget sammanhang mer än att de ligger i olika Plejd scenarion, tex så släcks ofta all belysning, timer utgångar stängs av osv.

[TrekBonanza]

Same for me, in my case there are allways 3 units that get trigged when HA restarting! The bad thing is I have one unit to my garage door that allways triggers and opens the door after a restart... But I think it is in the MQTT and not plejd that triggers new status when restarting.

[Mats1717]

Same for me, in my case there are allways 3 units that get trigged when HA restarting! The bad thing is I have one unit to my garage door that allways triggers and opens the door after a restart... But I think it is in the MQTT and not plejd that triggers new status when restarting.

Had that problem to, made a work around automation so last state is off always, time om plejd more then 1 second I set it to 4

alias: Turn Garageport Off description: "" trigger:

• platform: state entity_id:
  • switch.garageport from: "off" to: "on" for: hours: 0 minutes: 0 seconds: 0 condition: [] action:
• delay: hours: 0 minutes: 0 seconds: 1 milliseconds: 0
• service: switch.turn_off data: {} target: entity_id: switch.garageport mode: single

[timjackson]

This sounds similar to what is described in #218 . Could it be a duplicate?

[ChristianNiklasson]

This sounds similar to what is described in #218 . Could it be a duplicate?

That issue seems to affect all units though.

My problem is that only a few units are latched on reeboot

[Sway-SWE]

Hello!

I am experiencing slightly similar issue as @ChristianNiklasson.

When rebooting my system or restarting HA, one of my Plejd device automatically turns on the light. This is also happening when just restarting the Plejd add-on. I have 4 Plejd devices and only one of them is acting that way.

I am currently running HA Supervised on Debian 12 on a laptop but I was also experiencing the same issue a few days ago when I was still on a Raspberry Pi 3B running HAOS.

I am not using any scenes or automation for the device experiencing the issue so the behavior is weird and I am not too sure what's triggering the device's state from switch from off to on.

Core 2024.3.3 Supervisor 2024.03.1 Plejd add-on 0.11.0 version

Please let me know if you need any further information to help troubleshoot or if this was already identified as a known issue without any current fix in place.

One additional thing I noticed is an error beeing displayed in my Zigbee2MQTT logs pointing to Plejd but I have no idea if this is somehow related to the issue or not.

Thanks!

[Sway-SWE]

I think I may have found something interesting. Although I have 4 physical Plejd devices, the Plejd add-on logs were displaying the following:

2024-03-28 19:20:20 INF [plejd-mqtt] Sending discovery for 6 Plejd output devices

The 2 additional devices are not physical devices but actually a result of this option being ticked in the Plejd add-on configuration tab:

Now, what I found out is that the light turning on after restart is not actually triggered by the devices from the room but by the room itself.

2024-03-28 19:20:20 DBG [plejd-mqtt] Sending discovery for Badrum 2024-03-28 19:20:20 INF [plejd-mqtt] Discovered Room (light) named Badrum (10 : d0e34b5c-2749-45d5-a1f4-31b7ce50c4ba). ... 2024-03-28 19:20:20 INF [device-comm] Plejd got turn on command for Badrum (d0e34b5c-2749-45d5-a1f4-31b7ce50c4ba), brightness undefined 2024-03-28 19:20:20 DBG [device-comm] Queueing turn on Badrum (d0e34b5c-2749-45d5-a1f4-31b7ce50c4ba). No brightness specified, setting DIM to previous. ... 2024-03-28 19:20:50 DBG [device-comm] Write queue: Processing Badrum (d0e34b5c-2749-45d5-a1f4-31b7ce50c4ba). Command Turn on. Total queue length: 1

A workaround to skip the light from turning on upon restart in my case was to disable includeRoomsAsLights.

Now this is only a workaround and I am not able to tell why that specific room is getting that ON state upon restart while my second room doesn't.

2024-03-28 19:20:50 DBG [device-comm] Write queue: Processing Badrum (d0e34b5c-2749-45d5-a1f4-31b7ce50c4ba). Command Turn on. Total queue length: 1 2024-03-28 19:20:50 DBG [device-comm] Write queue: Processing Badrum/Tvättstuga (fa01c08c-2d72-45b9-b5a1-e1ba7392e6c2). Command Turn off. Total queue length: 0

I will continue to monitor the behavior in the meantime while having includeRoomsAsLights disabled and I'll update you.

[Sway-SWE]

3 tests done while having includeRoomsAsLights disabled. HA restart = the Plejd device remains turned off Laptop reboot = the Plejd device remains turned off. Plejd Add-On restart = the Plejd device remains turned off

[ChristianNiklasson]

3 tests done while having includeRoomsAsLights disabled.

HA restart = the Plejd device remains turned off

Laptop reboot = the Plejd device remains turned off.

Plejd Add-On restart = the Plejd device remains turned off

I have always had the "room as light" setting "off" and is experiencing the problem with lights switching modess

[Sway-SWE]

I have always had the "room as light" setting "off" and is experiencing the problem with lights switching modess

@ChristianNiklasson: Sorry to hear it doesn't help in your case. It did fix my issue but as mentioned, it was only a work around and not ideal. I am still unsure why one of the room was switching one device to ON upon each restart. I am barely using the Plejd mobile app but maybe the state of the room was always ON there and HA remembered that after each restart. Rather unlikely but just trying to help and I am novice when it comes to reading logs so hope somebody else can offer more help. I'll keep watching this thread though because I am curious what could cause such issue.