Homeseer is reporting unknown parameters from new SONOFF Zigbee device ZBM5-1C-120

[yecam]

What happened?

The Sonoff switch ZBM5-1C-120 cab be operated through the Homeseer interface but when the switched is operated manually from the front paddle Homeseer is seeing unexpected parameters including the current state (on/off) labelled as state_l1. These property parameters are "update", "state_l1" and "power_on_behavior_l1"

The debug log shows the following: (Note that the familiar name for this switch is "Main vestibule Statue Light"

2/23/2025 4:51:24 PM
ZigbeePlus
Debug
: cannot find published property update
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
Main vestibule Statue Light: cannot find published property state_l1
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
Main vestibule Statue Light: cannot find published property power_on_behavior_l1
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
MQTT Broker: TX (411 bytes) >>> Publish: [Topic=zigbee2mqtt/Main vestibule Statue Light] [PayloadLength=367] [QoSLevel=AtMostOnce] [Dup=False] [Retain=False] [PacketIdentifier=0]
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
MQTT Broker: Client 'mqttjs_a811226c': Queued PUBLISH packet with topic 'zigbee2mqtt/Main vestibule Statue Light'
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
Z2M Client: Received, topic=zigbee2mqtt/Main vestibule Statue Light, payload={"detach_relay_mode":{"detach_relay_outlet1":"DISABLE","detach_relay_outlet2":"DISABLE","detach_relay_outlet3":"DISABLE"},"device_work_mode":"Zigbee end device","linkquality":132,"network_indicator":true,"power_on_behavior":"previous","power_on_behavior_l1":"off","state":"ON","state_l1":"OFF","update":{"installed_version":4099,"latest_version":4099,"state":"idle"}}
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
MQTT Broker: TX (411 bytes) >>> Publish: [Topic=zigbee2mqtt/Main vestibule Statue Light] [PayloadLength=367] [QoSLevel=AtMostOnce] [Dup=False] [Retain=False] [PacketIdentifier=0]
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
MQTT Broker: Client 'mcsMQTT on HS4PiV5-1': Queued PUBLISH packet with topic 'zigbee2mqtt/Main vestibule Statue Light'
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
MQTT Broker: TX (411 bytes) >>> Publish: [Topic=zigbee2mqtt/Main vestibule Statue Light] [PayloadLength=367] [QoSLevel=AtMostOnce] [Dup=False] [Retain=False] [PacketIdentifier=0]
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
MQTT Broker: Client 'Zigbee2MqttNet': Queued PUBLISH packet with topic 'zigbee2mqtt/Main vestibule Statue Light'
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
Z2M Server: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Main vestibule Statue Light', payload '{"detach_relay_mode":{"detach_relay_outlet1":"DISABLE","detach_relay_outlet2":"DISABLE","detach_relay_outlet3":"DISABLE"},"device_work_mode":"Zigbee end device","linkquality":132,"network_indicator":true,"power_on_behavior":"previous","power_on_behavior_l1":"off","state":"ON","state_l1":"OFF","update":{"installed_version":4099,"latest_version":4099,"state":"idle"}}'
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
MQTT Broker: RX (410 bytes) <<< Publish: [Topic=zigbee2mqtt/Main vestibule Statue Light] [PayloadLength=367] [QoSLevel=AtMostOnce] [Dup=False] [Retain=False] [PacketIdentifier=0]
2/23/2025 4:51:24 PM
ZigbeePlus
Debug
Z2M Client: Received, topic=zigbee2mqtt/bridge/logging, payload={"level":"info","message":"z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Main vestibule Statue Light', payload '{"detach_relay_mode":{"detach_relay_outlet1":"DISABLE","detach_relay_outlet2":"DISABLE","detach_relay_outlet3":"DISABLE"},"device_work_mode":"Zigbee end device","linkquality":132,"network_indicator":true,"power_on_behavior":"previous","power_on_behavior_l1":"off","state":"ON","state_l1":"OFF","update":{"installed_version":4099,"latest_version":4099,"state":"idle"}}'"}

In addition, the Zigbee front end state seen by the Homeseer plugib shows

{
"detach_relay_mode": {
"detach_relay_outlet1": "DISABLE",
"detach_relay_outlet2": "DISABLE",
"detach_relay_outlet3": "DISABLE"
},
"device_work_mode": "Zigbee end device",
"linkquality": 132,
"network_indicator": true,
"power_on_behavior": "previous",
"power_on_behavior_l1": "off",
"state": "OFF",
"state_l1": "OFF",
"update": {
"installed_version": 4099,
"latest_version": 4099,
"state": "idle"
}
}

What did you expect to happen?

The Homeseer application should recognize the current state of the switch (on/off) when it is manually operated.

How to reproduce it (minimal and precise)

Change the log setting for the Zigbee plugin to "debug"
Open up the Homeseer log page
Manually toggle the switch and observe the activity as shown above.

Zigbee2MQTT version

2.1.1

Adapter firmware version

7.4.4 [GA]

Adapter

ember

Setup

Homeseer Zigbee Plus plugin version 1.1.1.0 (beta) on Raspberry Pi

Debug log

See log snippet above

[yecam]

Have now updated to Homeseer Zigbee Plus plugin version 1.1.2.0 with no change in the reported behaviour.

This is a listing of the changes over the last few updates.

1.1.2.0 - 2/24/2025

ZBPL-77 Fix parsing of JSON device definitions
1.1.1.0 - 2/18/2025

ZBPL-77 Fix installation of pnpm on both Linux and Windows. Fix initialization of default configuration.yaml file on new installs.
1.1.0.0 - 2/17/2025

ZBPL-77 Update Zigbee2MQTT to version 2.1.1 and adapt plugin to support breaking changes.