zigbee2mqtt topic issues

I have called it Hue Bulb, but it probably doesnt need to be. It looks like zigbee2mqtt handles the bulbs the same and has the same commands for them all, so it could just be bulb.

Or maybe RGBbulb and ColourTempBulb or Color

For all these zigbee devices I am following naming convention of zigbee2mqtt/{deviceType}/{uniqueName}

For all these zigbee devices I am following naming convention of zigbee2mqtt/{deviceType}/{uniqueName}

I assume that can be done in Node-Red but I just get an error if I try zigbee2mqtt/plug/Salus_SP600/, it has to be zigbee2mqtt/Salus_SP600/

Code: Select all

Jan 14 16:10:44 raspberrypi npm[688]: Zigbee2MQTT:info  2021-01-14 16:10:44: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"plug/Salus_SP600"},"type":"entity_not_found"}'
Jan 14 16:10:44 raspberrypi npm[688]: Zigbee2MQTT:error 2021-01-14 16:10:44: Entity 'plug/Salus_SP600' is unknown
Jan 14 16:10:44 raspberrypi npm[688]: Zigbee2MQTT:info  2021-01-14 16:10:44: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"plug/Salus_SP600"},"type":"entity_not_found"}'
Jan 14 16:10:44 raspberrypi npm[688]: Zigbee2MQTT:error 2021-01-14 16:10:44: Entity 'plug/Salus_SP600' is unknown
Jan 14 16:10:44 raspberrypi npm[688]: Zigbee2MQTT:error 2021-01-14 16:10:44: Invalid JSON '', skipping...



You mean in the node-red UI for z2mqtt. Yes. That’s where I do it.
Maybe try without the under score?

Tried it without the underscore and same error in the logs and 2 devices in MQTT Explorer.

Screenshot 2021-01-14 at 22.47.29.png (53.81 KiB) Viewed 2074 times

I assume that can be done in Node-Red but I just get an error if I try zigbee2mqtt/plug/Salus_SP600/, it has to be zigbee2mqtt/Salus_SP600/

Salus_SP600 IS the device type that he was referring to. It's not the unique name. I think.

Thats strange. Was the top one from before you changed the name? What if you restart explorer? Although I guess if you get errors it wont publish. Was the 2nd entry from Indigo?

Out of interest where do you see the error log?

Thats strange. Was the top one from before you changed the name? What if you restart explorer? Although I guess if you get errors it wont publish. Was the 2nd entry from Indigo?

Out of interest where do you see the error log?

Ok, I have changed the friendly name in configuration.yaml from

'0x001e5e09021621b7':
friendly_name: SalusSP600
to
'0x001e5e09021621b7':
friendly_name: plug/SalusSP600

and now get

Code: Select all

Jan 15 11:35:38 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:38: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/update-state', payload 'idle'
Jan 15 11:35:38 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:38: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/update_available', payload 'false'
Jan 15 11:35:38 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:38: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/state', payload 'OFF'
Jan 15 11:35:38 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:38: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/power', payload '0'
Jan 15 11:35:38 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:38: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/energy', payload '12.33'
Jan 15 11:35:38 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:38: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/linkquality', payload '78'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600', payload '{"energy":12.33,"linkquality":76,"power":0,"state":"ON","update":{"state":"idle"},"update_available":false}'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/update-state', payload 'idle'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/update_available', payload 'false'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/state', payload 'ON'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/power', payload '0'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/energy', payload '12.33'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600/linkquality', payload '76'
Jan 15 11:35:41 raspberrypi npm[1586]: Zigbee2MQTT:info  2021-01-15 11:35:41: MQTT publish: topic 'zigbee2mqtt/plug/SalusSP600', payload '{"energy":12.33,"linkquality":73,"power":0,"state":"ON","update":{"state":"idle"},"update_available":false}'


but in reality it is no different to '0x001e5e09021621b7':
friendly_name: plug-SalusSP600 or plug*SalusSP600

What was you reason for adding the /plug/ in the name?

The error log is from a Terminal window in Pi running the Z2M

Code: Select all

pi@raspberrypi:~ $ sudo journalctl -u zigbee2mqtt.service -f

Ok, that looks good now.

The advantage to this method is you only need one trigger for plug, and then use it for all your plugs, ie plug/SalusSP600 and plug/bedroom, plug/living room etc... Otherwise you would need to create triggers for all.

and thanks, but I run z2m on my mac and journalctl doesnt work on Macs.