Indigo Domotics

siclark wrote:

Also I have changed to do zigbee2mqtt/aqaratemp/room_name. I then have aqaravibration and aqarabutton etc.

Therefore only need one trigger per aqara type.

siclark wrote:

Also I have changed to do zigbee2mqtt/aqaratemp/room_name. I then have aqaravibration and aqarabutton etc.

Therefore only need one trigger per aqara type.

autolog wrote:

Looking at the documentation here: MQTT topics and message structure, I see it is possible to get a graphical display of the Zigbee network. Search for this heading: zigbee2mqtt/bridge/networkmap

You need to publish a message with the topic: zigbee2mqtt/bridge/networkmap/routes and payload of graphviz [Note no {} around the payload].

This can take a few minutes and you will get a network map data published as a message topic: zigbee2mqtt/bridge/networkmap/[graphviz. I didn't use this, I just copied the content of the message out of the zigbee2mqtt log.

You can then paste the message starting with digraph G { and ending in } into the panel at WebGraphViz to get a graphical display of your network.

Using this I have confirmed that my INNR plugs work as routers. Having relocated one of the INNR plugs, I reset one of my temperature sensors that was in close proximity and I can now see that the sensor is routing back to the controller via the plug.

Code: Select all

ag@automation ~ % sudo curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
Password:

## Installing the NodeSource Node.js 12.x repo...


## Populating apt-get cache...

+ apt-get update
bash: apt-get: command not found
Error executing command, exiting

agame wrote:

oh I should probably have read the error. I need to install apt-get presumably

siclark wrote:

Just try installing node.js for mac

Code: Select all

ag@automation ~ % sudo chown -R pi:pi /opt/zigbee2mqtt
chown: pi: illegal group name