Indigo and Zigbee

Hi Simon,
Thanks for the info and link.

I will order one once he is back in early January.

Looks like it could be quite good.

He is back, just ordered mine this afternoon, hopefully here later this week.
Just need to get my head around it all as shims still confuses me.

I need to finalise a couple of issues with Joe when I get time then in theory we can have templates setup in the plugin that do it all for you and you just enter the device name.
There are some there but the colour bulb I think needs some correction.

In the meantime shout if you have any questions.

A few interesting observations on my now large zigbee mesh vs zwave.

I have a zwave module controlling a pendant light in my bedroom, and 2 zigbee bulbs, one INNR, one Hue. Consitently the zigbee bulbs respond to commands faster than the zwave one.

Not all zigbee mains devices act as repeaters for all zigbee devices! For instance an INNR bulb and Smartthings socket will repeat signal for my Aqara temperature sensors, but Hue Bulbs and Lidl sockets dont so I am having to make some views on where to put devices based on this.
However seeing the details of the zigbee mesh is easier than the zwave one.

Finally, at the moment, my zigbee devices dont always report correct state in Indigo, but that might just be issues with my setup of the MQTT Shims plugin. Or my setup of zigbee2mqtt as there are more options in zigbee for how long messages are persisted across the network.

I am currently experimenting using a Hubitat Elevation (HE) as a Zigbee Controller at the moment. I have two Zigbee networks running: My cc2531 (Zigbee2MQTT) and HE.

The experience I had when the CC2531 went pear-shaped over Christmas and a level of complexity involved with setting up Zigbee2MQTT is what made me interested in Hubitat as it seems easier (even if more expensive).

As mentioned, the setup in HE seems easier but you do have to install some 3rd party specific Zigbee Device drivers. I have got MQTT to work and the HE devices are reflected in Indigo via Joe’s MQTT Shims plugin.

Out of interest, @Busta999 has discovered that Hue Motion Detectors will still output temperature updates if they are put inside a fridge or freezer. My fridge is currently registering 4.74C and the freezer is registering -18.2C. It will be interesting to see how long the batteries last.

More work to do on HE but it looks promising.

Finally, at the moment, my zigbee devices dont always report correct state in Indigo, but that might just be issues with my setup of the MQTT Shims plugin. Or my setup of zigbee2mqtt as there are more options in zigbee for how long messages are persisted across the network.

I have that problem with a Salus SP600 UK plug, I can turn it On/Off from Indigo but the State always shows Off. It also refuses to be a repeater for my Aqara devices which was one reason to buy it in the first place.
Hopefully the postman will deliver my Electrolama zig-a-zig-ah! tomorrow to increase the range.

I had been using 433Mhz sensors - the TFA 30.3163 are great at this, as long as you offset the temp read by 40C

Tried some Sonoff Temp/Humidity Sensors - nope

Now have the Fridge and Freezers with HUE Motion Sensors in them and they appear to be holding well.

Just started graphing them but it looks promising to use the Motion and Luminance sensors to detect if the door is opened AND if it is still open and create an alarm.

Siclark,

I have noticed that I had problems with a Tradfri that was far away from my Hue hub and that my Hue lamps didn’t repeat my signals, it works when I place it closer to the hub.

I have both Hue, Tradfri and Innr lamps and a Lildl plug.

It should be interesting to know what repeats signal to what.

Is it any difference if you use a Hue hub or one of the dedicated zigbee sticks?


Skickat från min iPad med Tapatalk

Finally, at the moment, my zigbee devices dont always report correct state in Indigo, but that might just be issues with my setup of the MQTT Shims plugin. Or my setup of zigbee2mqtt as there are more options in zigbee for how long messages are persisted across the network.

I have that problem with a Salus SP600 UK plug, I can turn it On/Off from Indigo but the State always shows Off. It also refuses to be a repeater for my Aqara devices which was one reason to buy it in the first place.
Hopefully the postman will deliver my Electrolama zig-a-zig-ah! tomorrow to increase the range.

What do you see if you monitor the device over mqtt in an app, not in indigo. Ie does the device report On, it’s just indigo doesn’t respond?

If I click the SP600 in Indigo I get the following log, the physical plug turns on and off, MQTT Explorer gives {"state": "OFF"} and {"state": "ON"}, it just does not update the GUI State from OFF

Code: Select all

pi@raspberrypi:~ $ sudo journalctl -u zigbee2mqtt.service -f
-- Logs begin at Thu 2019-02-14 10:11:59 GMT. --
Jan 12 18:36:45 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:45: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":89,"power":0.2,"state":"OFF","update":{"state":"idle"},"update_available":false}'
Jan 12 18:36:45 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:45: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":86,"power":0.2,"state":"OFF","update":{"state":"idle"},"update_available":false}'
Jan 12 18:36:46 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:46: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":89,"power":0.2,"state":"OFF","update":{"state":"idle"},"update_available":false}'
Jan 12 18:36:47 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:47: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":86,"power":0.2,"state":"ON","update":{"state":"idle"},"update_available":false}'
Jan 12 18:36:47 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:47: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":86,"power":0.2,"state":"ON","update":{"state":"idle"},"update_available":false}'
Jan 12 18:36:48 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:48: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":86,"power":0.2,"state":"ON","update":{"state":"idle"},"update_available":false}'
Jan 12 18:36:50 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:50: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":89,"power":0.2,"state":"OFF","update":{"state":"idle"},"update_available":false}'
Jan 12 18:36:50 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:36:50: MQTT publish: topic 'zigbee2mqtt/Salus_SP600', payload '{"energy":12.33,"linkquality":86,"power":0.2,"state":"OFF","update":{"state":"idle"},"update_available":false}'
Jan 12 18:37:07 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:37:07: MQTT publish: topic 'zigbee2mqtt/Aqara_Movement_Sensor', payload '{"battery":100,"illuminance":34,"illuminance_lux":34,"linkquality":0,"occupancy":true,"voltage":3015}'
Jan 12 18:37:07 raspberrypi npm[497]: Zigbee2MQTT:info  2021-01-12 18:37:07: MQTT publish: topic 'zigbee2mqtt/Aqara_Movement_Sensor', payload '{"battery":100,"illuminance":34,"illuminance_lux":34,"linkquality":0,"occupancy":true,"voltage":3015}'




Now we need to see your Shim device configuration.

Ok, I have seen the same in indigo too. I would raise this to Joe, open a new post in the MQTT thread.

I am currently experimenting using a Hubitat Elevation (HE) as a Zigbee Controller at the moment. I have two Zigbee networks running: My cc2531 (Zigbee2MQTT) and HE.

The experience I had when the CC2531 went pear-shaped over Christmas and a level of complexity involved with setting up Zigbee2MQTT is what made me interested in Hubitat as it seems easier (even if more expensive).

As mentioned, the setup in HE seems easier but you do have to install some 3rd party specific Zigbee Device drivers. I have got MQTT to work and the HE devices are reflected in Indigo via Joe’s MQTT Shims plugin.

More work to do on HE but it looks promising.

£135 for the HE is a lot for what we need as a controller USB. We would be buying a home automation system to operate as a controller for zigbee? I would be more tempted to use the zig-a-zig-ah in Home Assitant and use the plugin for that than pay for HE.
I dont see the point in HE if we still need Shims. With the new zigbee stick it should be a one time setup and then using the node red interface for zigbee2mqtt it takes 30 seconds to rename a new device.
Ideally we would have indigo auto create the device, but once we have the proper Shims templates setup, it would be no longer to create the indigo device than for a zwave device.

Now we need to see your Shim device configuration.

Code: Select all

message_type: '##SP600##'
props:
    SupportsOnState: true
    SupportsStatusRequest: true
    action_template: zigbee2mqtt/{{uniqueID}}/set
    off_action_payload: '{"state": "OFF"}'
    on_action_payload: '{"state": "ON"}'
    shimSensorSubtype: Power
    state_location: payload
    state_location_payload_key: state
    state_location_payload_type: raw
    state_location_topic_field: '2'
    state_on_value: 'ON'
    status_action_payload: '{ "state": ""}'
    status_action_template: zigbee2mqtt/{{uniqueID}}/get
    uid_location: topic
    uid_location_topic_field: '1'
trigger:
    match_list: '["Match: zigbee2mqtt", "Match: Salus_SP600", "Any: ", "End: "]'
    queueMessage: true
type: shimRelay



You've got payload type set to raw, but that's a JSON payload. Please continue this in the MQTT forum.