Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shelly BLU Motion and DW sensor do not update after some time #18171

Open
parachutesj opened this issue Jan 24, 2025 · 0 comments
Open

Shelly BLU Motion and DW sensor do not update after some time #18171

parachutesj opened this issue Jan 24, 2025 · 0 comments
Labels
bug An unexpected problem or unintended behavior of an add-on

Comments

@parachutesj
Copy link

I have a Shelly BLU motion sensor which is auto discovered and when configured it seems to be ok. However after a few updates it seems to freeze in OpenHab. No updates on the channels. I can see the messages arrive when looking in the script log of the Bluetooth gateway (e.g Motion changes from 0 to 1 or vice versa).

shelly_notification:208 Event from script:1: {"component":"script:1","id":1,"event":"oh-blu.data","data":{"encryption":false,"BTHome_version":2,"pid":50,"Battery":100,"Illuminance":635,"Motion":1,"addr":"3c:2e:f5:bb:bd:0e","rssi":-67},"ts":1736880362.71}

Further down looking in the OH debug logs, I also see that the status update arrives:
2025-01-15 15:09:06.135 [TRACE] [helly.internal.api2.Shelly2RpcSocket] - shellyplus2pm-b8d61a8b8634 Shutter_AZ: Inbound Rpc message: {"src":"shellyplus2pm-b8d61a8b8634","dst":"openhab-192.168.178.31","method":"NotifyEvent","params":{"ts":1736950146.08,"events":[{"component":"script:1","id":1,"event":"oh-blu.data","data":{"encryption":false,"BTHome_version":2,"pid":103,"Battery":100,"Illuminance":600,"Motion":1,"addr":"3c:2e:f5:bb:bd:0e","rssi":-67},"ts":1736950146.08}]}} 2025-01-15 15:09:06.135 [TRACE] [ng.shelly.internal.api2.ShellyBluApi] - shellyblumotion-3c2ef5bbbd0e: ShellyEvent received: {"src":"shellyplus2pm-b8d61a8b8634","params":{"ts":1.73695014608E9,"events":[{"id":1,"ts":1.73695014608E9,"component":"script:1","event":"oh-blu.data","data":{"addr":"3c:2e:f5:bb:bd:0e","encryption":false,"BTHome_version":2,"pid":103,"Battery":100,"Illuminance":600,"Motion":1,"rssi":-67}}]}} 2025-01-15 15:09:06.136 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyblumotion-3c2ef5bbbd0e: Watchdog restarted (expires in 43260 sec) 2025-01-15 15:09:06.136 [DEBUG] [ng.shelly.internal.api2.ShellyBluApi] - shellyblumotion-3c2ef5bbbd0e: BluEvent received: {"src":"shellyplus2pm-b8d61a8b8634","params":{"ts":1.73695014608E9,"events":[{"id":1,"ts":1.73695014608E9,"component":"script:1","event":"oh-blu.data","data":{"addr":"3c:2e:f5:bb:bd:0e","encryption":false,"BTHome_version":2,"pid":103,"Battery":100,"Illuminance":600,"Motion":1,"rssi":-67}}]}} 2025-01-15 15:09:06.136 [DEBUG] [ng.shelly.internal.api2.ShellyBluApi] - shellyblumotion-3c2ef5bbbd0e: BLU event oh-blu.data received from address 3c:2e:f5:bb:bd:0e, pid=103 2025-01-15 15:09:06.136 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellyblumotion-3c2ef5bbbd0e: Channel sensors#motion updated with ON (type class org.openhab.core.library.types.OnOffType).

It seems all is good, only the channels won't get updates.
Basically I have 20 Shelly (wired) devices and all others work flawless. Only the BT ones. Also same behaviour with a Door/Window sensor. It gets correctly discovered, configured and after a few minutes the updates stop.

I made a fresh installation of OH 4.3.2 with only the shelly binding to verify if there is something else broken. No, same issue.
I then installed the latest dev build 4.3.5 with no luck

I recently found a Bluetooth Gateway (Theengs) which also ready the sensors and sends updates via MQTT. This works very well for the moment, so I can somehow rule out that the devices do not send updates as I am getting them via MQTT (mapped to different things and channels).

Let me know if you need more logs etc.

Your Environment

  • Version used: (e.g., openHAB and add-on versions)
  • Environment name and version (e.g. Chrome 76, Java 8, Node.js 12.9, ...):
  • Operating System and version (desktop or mobile, Windows 10, Raspbian Buster, ...):
@parachutesj parachutesj added the bug An unexpected problem or unintended behavior of an add-on label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on
Projects
None yet
Development

No branches or pull requests

1 participant