Closed bm500 closed 9 months ago
Also tried this . Same result with no controls showing. The sensor is really nice looking so hope it will work
I've got one on it's way in the mail, so I'm sure this will be fixed...
Ok. Nice!
If i can help in some way i would be happy to do so. Just let me know.
Aleksander Norway
lør. 17. feb. 2024 kl. 10:56 skrev Thomas Lovén @.***>:
I've got one on it's way in the mail, so I'm sure this will be fixed...
— Reply to this email directly, view it on GitHub https://github.com/thomasloven/hass_plejd/issues/54#issuecomment-1949920544, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNUOIDRQ4DHWRKMUGZQPITYUB5FLAVCNFSM6AAAAABC6ISVYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZHEZDANJUGQ . You are receiving this because you commented.Message ID: @.***>
There we go!
I have tried to update the integration and now i see the sensor with entity put i doesnt not reconize movement
Maybe you could help me with the debugging then?
If you add the following to your configuration.yaml
logger:
default: warn
logs:
pyplejd.dev: debug
and then restart Home Assistant. Hopefully, you should see some messages starting with "Unknown LASTDATA cmd" or similar in your Home Assistant log when you move in front of the sensor. Those would probably help me a lot.
If you get nothing there, please try pyplejd.ble
instead of pyplejd.dev
.
I have also tested the new version and the sensor seams to work ok. Movement is recognized as soon as I enter the room.
I have tried to update the integration and now i see the sensor with entity put i doesnt not reconize movement
Wait... you're the one who emailed me and had only a WMS-01 and nothing else, right? So you don't know if your hass machine can connect to your Plejd mesh at all... To answer your email, no a Shelly proxy will not work - as stated in the readme.
Did Plejd pop up for you as autodetected, or did you add it manually?
Yes. I emailed you. I have only this plejd sensor. It did autodetected but when i updated the plugin it was not so i added it manuelt
ons. 21. feb. 2024 kl. 16:41 skrev Thomas Lovén @.***>:
I have tried to update the integration and now i see the sensor with entity put i doesnt not reconize movement
Wait... you're the one who emailed me and had only a WMS-01 and nothing else, right? So you don't know if your hass machine can connect to your Plejd mesh at all... To answer your email, no a Shelly proxy will not work - as stated in the readme.
Did Plejd pop up for you as autodetected, or did you add it manually?
— Reply to this email directly, view it on GitHub https://github.com/thomasloven/hass_plejd/issues/54#issuecomment-1956994452, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUNUOICLRMAAMTYC5ZNBCP3YUYITRAVCNFSM6AAAAABC6ISVYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHE4TINBVGI . You are receiving this because you commented.Message ID: @.***>
Tried to delete the integration and restartet and then it was autodiscovered but it still does not show movement
I have tried with the logger pyplejd.dev and pyplejd.ble put nothings comes up in the log. I use the normal log on the left side of HA. Or is there another log i should check?
Also tried with the built in bluetooth in rpi4 and with esphome bluetooth proxy. but nothing. The sensor says available and ready
Edit: also nothing in the settings- system - log
Edit2: 2024-02-21 this is the only thing i find. 21:50:44.095 DEBUG (MainThread) [custom_components.plejd.plejd_site] Ping failed 2024-02-21 21:50:44.096 DEBUG (MainThread) [custom_components.plejd.plejd_site] Ping failed
I tried alot last night and this morning. But it doesnot react on movement. In the plejd app on the iphone it does show movement. i downloaded the diagnostic file if it can be to any use.
config_entry-plejd-3530f27ba6b2a2b2e5c30be4220e5c97.json
I tried the plejd addon ([hassio-plejd) and i get some date there when i walk past the sensor. But WMS-01 is not a supported device. https://github.com/icanos/hassio-plejd/issues/300
Seems like it wont connect to the mesh. Could it be that i only have one Plejd device?
2024-02-24 12:26:58.540 DEBUG (MainThread) [pyplejd.ble] Saw device F0:3B:87:13:8B:39: F0-3B-87-13-8B-39 (rssi: -71, prev: -1000000.0) 2024-02-24 12:26:58.541 DEBUG (MainThread) [pyplejd.ble] Trying to connect to mesh 2024-02-24 12:26:58.541 DEBUG (MainThread) [pyplejd.ble] Failed to connect to plejd mesh - No valid devices: {BLEDevice(F0:3B:87:13:8B:39, P mesh): -40, BLEDevice(F0:3B:87:13:8B:39, F0-3B-87-13-8B-39): -71} (set()) 2024-02-24 12:26:58.541 DEBUG (MainThread) [custom_components.plejd.plejd_site] Ping failed 2024-02-24 12:27:34.649 DEBUG (MainThread) [pyplejd.ble] Saw device F0:3B:87:13:8B:39: P mesh (rssi: -63, prev: -1000000.0) 2024-02-24 12:27:34.649 DEBUG (MainThread) [pyplejd.ble] Trying to connect to mesh 2024-02-24 12:27:34.649 DEBUG (MainThread) [pyplejd.ble] Failed to connect to plejd mesh - No valid devices: {BLEDevice(F0:3B:87:13:8B:39, P mesh): -40, BLEDevice(F0:3B:87:13:8B:39, F0-3B-87-13-8B-39): -71, BLEDevice(F0:3B:87:13:8B:39, P mesh): -63} (set())
EDIT:
2024-02-24 18:02:18.721 DEBUG (MainThread) [pyplejd.ble] Trying to connect to mesh 2024-02-24 18:02:18.721 DEBUG (MainThread) [pyplejd.ble] Failed to connect to plejd mesh - No valid devices: {BLEDevice(F0:3B:87:13:8B:39, P mesh): -40, BLEDevice(F0:3B:87:13:8B:39, F0-3B-87-13-8B-39): -71, BLEDevice(F0:3B:87:13:8B:39, P mesh): -63, BLEDevice(F0:3B:87:13:8B:39, P mesh): -63, BLEDevice(F0:3B:87:13:8B:39, P mesh): -59, BLEDevice(F0:3B:87:13:8B:39, F0-3B-87-13-8B-39): -70, BLEDevice(F0:3B:87:13:8B:39, P mesh): -68, BLEDevice(F0:3B:87:13:8B:39, P mesh): -68, BLEDevice(F0:3B:87:13:8B:39, P mesh): -70, BLEDevice(F0:3B:87:13:8B:39, P mesh): -64, BLEDevice(F0:3B:87:13:8B:39, P mesh): -62, BLEDevice(F0:3B:87:13:8B:39, P mesh): -68, BLEDevice(F0:3B:87:13:8B:39, P mesh): -70, BLEDevice(F0:3B:87:13:8B:39, P mesh): -68, BLEDevice(F0:3B:87:13:8B:39, P mesh): -64, BLEDevice(F0:3B:87:13:8B:39, P mesh): -69, BLEDevice(F0:3B:87:13:8B:39, P mesh): -71} (set()) 2024-02-24 18:02:18.722 DEBUG (MainThread) [custom_components.plejd.plejd_site] Ping failed
Oh! I see what the issue is now.
Since battery powered devices go to sleep when they are not used, they cannot be reliably used for the mesh connection. Therefore they are ignored when the initial connection is made.
I'll have to think a bit about how to handle this one...
Excellent. Thanks. If there is something i could do in the config or something to "hack" around the issuse it would be great. I guess most people have several plejd devices but i only choose this one because of its smart design.
This should work better in 0.10.0. You may need to walk in front of your device to wake it up for the first connection, and there may be impact on its battery life.
After installing WMS-01 the integration founds the device but there is no controls avalible. Pls see picture as well as diagnistic file in link. If I can help, I will be happy to do so.
config_entry-plejd-aac7e4b63e67aaf4c4a30625da5a5458.json (5).txt