Send device options via ZigBee2MQTT

DivineJimmi · August 9, 2023, 3:51pm

Hey, i have an IKEA motion sensor and want to set the occupancy_timeout via an item. Unfortunately the occupancy_timeout is being controlled by “device specific options” and not via a /set request.

Adding this to a .things file, does not change anything at all. Its still not working. Is there even a way to change this via an item?

Thing mqtt:topic:Bewegungsmelder_Badezimmerspiegel "Z2M: Bewegungsmelder Badezimmerspiegel" (mqtt:broker:823098e4c9) [availabilityTopic="zigbee2mqtt/Bewegungsmelder_Badezimmerspiegel/availability", payloadAvailable="online", payloadNotAvailable="offline", transformationPattern="JSONPATH:$.state"] {
    Channels:
    Type switch : occupancy "Bewegung" [stateTopic="zigbee2mqtt/Bewegungsmelder_Badezimmerspiegel", transformationPattern="JSONPATH:$.occupancy", on="true", off="false"]
    Type number : occupancy_timeout "Timeout wenn keine Bewegung" [stateTopic="zigbee2mqtt/Bewegungsmelder_Badezimmerspiegel", commandTopic="zigbee2mqtt/Bewegungsmelder_Badezimmerspiegel/set", transformationPattern="JSONPATH:$.occupancy_timeout"]
    Type number : battery "Akkustand" [stateTopic="zigbee2mqtt/Bewegungsmelder_Badezimmerspiegel", transformationPattern="JSONPATH:$.battery", formatBeforePublish="%d%%"]
}

The battery/switch channels are working. the timeout channel does not.

Looking into my zigbee2mqtt-configurations.yaml i am getting this information:

  '0x70ac08fffe9ca116':
    friendly_name: Bewegungsmelder_Badezimmerspiegel
    occupancy_timeout: 90
    illuminance_below_threshold_check: false

I never had those informations in the .yaml file. Normally the devices are listed without any options like this:

  '0x00158d000839bc3b':
    friendly_name: Wassersensor_Aquarium
  '0x70ac08fffe94f241':
    friendly_name: Reinigungsschalter_Badezimmer
  '0x84182600000c2997':
    friendly_name: Filterpumpe_Pool_Terrasse
  '0x001788010219dbc9':
    friendly_name: Fernbedienung_Schminktisch_Hobbyraum

Regards,
Jimmi

DivineJimmi · August 9, 2023, 4:07pm

Changing it to

Type number : occupancy_timeout "Timeout wenn keine Bewegung" [commandTopic="zigbee2mqtt/bridge/request/device/options", formatBeforePublish="{\"id\":\"0x70ac08fffe9ca116\",\"options\":{\"occupancy_timeout\":%s}}"]

worked finally.
Theres been a request for ZigBee2MQTT. And a little “tutorial” in the answers.

github.com/Koenkk/zigbee2mqtt

Feature request: Ability to set device specific options in runtime using mqtt

opened 08:55PM - 20 Feb 19 UTC

closed 01:39PM - 02 May 19 UTC

Filipok-A

stale

First I would like to thank Koen for zigbee2mqtt, I've started using it about tw…o weeks ago and it has been very stable since then. All of the devices I am using are Xiaomi and it is great than I can go away from using their gateway. There is only one feature that is preventing me to completely switch to zigbee2mqtt and switch off Xiaomi gateway; therefore a feature request: Ability to set device specific options in runtime using mqtt. My use case: Almost all of my lights are controlled by presence sensors with no physical switches. In some areas it is more complex to accurately detect if there is no one present or just the people there are not moving and I am using auxilary presense indicators to control the timeout when presense (and therefore lights) are turned off. For example in living room default timeout is 180s but if TV is on the timeout is changed to 600s which allows enough time to detect movement without accidently switching lights off. This works great for me using Openhab with addon for Xiaomi gateway. But with zigbee2mqtt the occupancy_timeout can only be set to a fixed value per device and can not be changed with mqtt and without restarting the service. If you can add this feature it would also be very benefitial to restart the timeout timer, if one is already running for specific device. Thanks in advance, Philip

system · September 20, 2023, 8:08am

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.