Reconnecting loop keeps going after devices found, this makes them unavailable.

[ProgrammerChris]

After staring, it finds devices, then these lines come next:

2022-11-30` 01:20:27 INF [plejd-ble] BLE init done, waiting for devices.
2022-11-30 01:20:27 INF [plejd-main] Main init done
2022-11-30 01:20:27 INF [plejd-main] main() finished
2022-11-30 01:20:29 ERR [plejd-ble] Discovery timeout elapsed, no devices found. Starting reconnect loop...

and this loop keeps going.

• Power cycleing the adapter does not help.
• Restarting the addon does not help,
• Restarting Home Assistant does not help.
• Re-installing app does not help.

[Mikro007]

I´m also having this problem...
To bad that it brakes down all automation for the lights and Plejd app need to go in for backup schedules.

[ErikThorsell]

System Info:

Raspberry Pi 4
Home Assistant 2023.1.0
Supervisor 2022.12.1
Operating System 9.4
Frontend 20230104.0 - latest

Addon version: 0.9.1

Today I migrated my installation from an SD Card to an SSD. I did a full backup (System > Backups > Create Backup) which I later restored using the "Restore from backup"-functionality in HA.

I am now having similar issues as seen above.

These are the last logs from the addon before I migrated:

Everything was working fine :)

Now, after the initial discovery (where all my devices are correctly found) I see the following in the logs:

NOTE

I also had issues, initially, with deConz and my Conbee USB stick. I learned that there's an issue with USB-3 that I don't quite understand, but moving the SSD to a USB-2 port seem to have solved my deConz-problems.

However, the Plejd addon is still missbehaving.

Any help is greatly appreciated.

[ErikThorsell]

UPDATE

Ehr. Maybe moving the SSD to USB-2 solved the Plejd issues too. I just had to manually restart the addon. (Would be a PITA if the Pi cannot handle a reboot without me having to manually restart addons though...)

I won't call this a win yet but at the moment Plejd is working again.

[hultr]

Just got the add-on and got this too :/ (on an x86 machine, onboard BT adapter, HA running in a proxmox VM, only other USB device is the Sonoff Zigbee dongle)

[ProgrammerChris]

Just got the add-on and got this too :/ (on an x86 machine, onboard BT adapter, HA running in a proxmox VM, only other USB device is the Sonoff Zigbee dongle)

What fixed this for me was extending the BT dongle to be closer to the first node. No issues after that.

[hultr]

ended up buying an external BT adapter (from the "tried" list), now it seems to work :). Guess it still could be a signal strength issue. The first Plejd device is only about 4 m away, but maybe the external adapter got better SNR or something.

[Lupi00]

ended up buying an external BT adapter (from the "tried" list), now it seems to work :). Guess it still could be a signal strength issue. The first Plejd device is only about 4 m away, but maybe the external adapter got better SNR or something.

Which one did you end up buying? And from where?

[ProgrammerChris]

Bought an Asus USB-BT500. Been stable ever since. man. 14. aug. 2023 kl. 12:53 skrev Lupi00 ***@***.***>:

…

ended up buying an external BT adapter (from the "tried" list), now it seems to work :). Guess it still could be a signal strength issue. The first Plejd device is only about 4 m away, but maybe the external adapter got better SNR or something. Which one did you end up buying? And from where? — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK2N5VISBCN2IVGAHQRP5YLXVH7T7ANCNFSM6AAAAAASPBY2YM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Med vennlig helsing *Chris Tvedt* Tlf: +47 906 55 559

[SweVictor]

Good to hear. Closing this issue as solved.