Shelly BLU Motion Sensor Decoding Issue

Theengs Decoder
,
1

I have 5 MQTT gateway devices in my system that send topics to the same broker. 2 ShellyPlugUS, 1 TheengsBridge and 2 Theengs Plugs. The issue I’m running into is that the OMG products are not decoding my ShellyBLU motion sensor data the same way as the ShellyPlugUS gateways are.

Here is the topic and data as seen by the broker for the same BT device:

OMG Gateways

topic:
BLU/theengs_br01/BTtoMQTT/3C2EF5BD771A

value:
{“id”:“3C:2E:F5:BD:77:1A”,“name”:“SBMO-003Z”,“rssi”:-66,“brand”:“Shelly”,“model”:“ShellyBLU Motion”,“model_id”:“SBMO-003Z”,“type”:“CTMO”,“packet”:46,“batt”:100,“lux”:37,“motion”:false,“mac”:“3C:2E:F5:BD:77:1A”}

ShellyPlugUS Gateways

topic:
ShellyBLU/shellyplugus-083af200807c/BTtoMQTT/3C2EF5BD771A

value:
{“encryption”:false,“BTHome_version”:2,“pid”:45,“batt”:100,“lux”:37,“mot”:0,“rssi”:-61,“id”:“3c:2e:f5:bd:77:1a”,“brand”:“Shelly”,“version”:“1.2”,“ip”:“192.168.10.101”}

The specific issue seems to be that the OMG gateways are decoding “motion” and labelling it “motion” whereas the ShellyPlugUS gateways are calling it “mot”. HA seems to be expecting it to be “mot” and throws a parse error.

I could blacklist the ShellyBLU Motion sensors in the OMG gateways, but that would seem to be more of a band-aid than a real fix.

Cheers,

Craig

2

After some further digging, I’m thinking its an issue with the ShellyBLU gateways. The HA log where the error occurs is:

2026-05-13 15:54:15.813 ERROR (MainThread) [homeassistant.helpers.template] Error parsing value: ‘dict object’ has no attribute ‘motion’ (value: {“encryption”:false,“BTHome_version”:2,“pid”:11,“batt”:100,“lux”:88,“mot”:0,“rssi”:-64,“id”:“e8:e0:7e:d0:99:31”,“brand”:“Shelly”,“version”:“1.2”,“ip”:“192.168.10.101”}, template: {{ value_json.motion | is_defined }})

It’s apparently looking for “motion” but getting “mot” instead.