Node red admin flow

There is a very interesting flow for node red and Z2M

https://flows.nodered.org/flow/1f1c0dde4ff193e5c14d5b99442a7d00

Take a look at it

1 Like

this is very cool thank you for your share
just wanna say that in this link it doesn’t work.
it says there is few misconfigured node and the list of device is not shown
but the version with subflow that is in you github is really cool and working

I suggest that you to visit the node red flows page were you may find this flow and well some nodes for some xiaomi
Thank you

Hello bob

I rechecked it and it runs perfectly.
The author of this flow mentions that its an upgrade the one you mentioned, and after compare them both I think that this iteration is an improvement.

JLG

it wasn’t for me but that’s ok it’s working now :smile: and i get a much cleaner flow
thanks

Mine works almost perfectly with the exception of the device list, which is empty.

It detects all my 37 devices and I can see them all on target device drop-down list.

The old Zigbee2MQTT flow shows all devices as expected.

Any tips in this case?

strange just happen to e now

I suspect that is due to the fact that the coordinator shows up with different format.

for the time being just comment

        // 'icon': 'https://www.zigbee2mqtt.io/images/devices/' + entry.model.replace(new RegExp('/', 'g'), '-') + '.jpg'

it will shot no so fancy with the icon, buts is workable

hello all

there is a new version

https://flows.nodered.org/flow/1f1c0dde4ff193e5c14d5b99442a7d00

I have a error, this in all devices:
image

This NR flow caused my z2m (hassio addon) to start getting hit by config/log mqtt messages every 5 seconds.
When I disabled the flow and redeployed it stopped.

E.g. (truncated rows)

  zigbee2mqtt:info 5/21/2019, 8:11:45 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:11:45 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{
  zigbee2mqtt:info 5/21/2019, 8:11:50 PM MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":"
  zigbee2mqtt:info 5/21/2019, 8:11:50 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:11:50 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{"
  zigbee2mqtt:info 5/21/2019, 8:11:55 PM MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":
  zigbee2mqtt:info 5/21/2019, 8:11:55 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:11:55 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{
  zigbee2mqtt:info 5/21/2019, 8:12:00 PM MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":
  zigbee2mqtt:info 5/21/2019, 8:12:00 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:12:00 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[
  zigbee2mqtt:info 5/21/2019, 8:12:05 PM MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":
  zigbee2mqtt:info 5/21/2019, 8:12:05 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:12:05 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{
  zigbee2mqtt:info 5/21/2019, 8:12:10 PM MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":"
  zigbee2mqtt:info 5/21/2019, 8:12:10 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:12:10 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{
  zigbee2mqtt:info 5/21/2019, 8:12:11 PM MQTT publish: topic 'zigbee2mqtt/CC2531 Router Kitchen', payload '{"state":false,"linkquality":10}'
  zigbee2mqtt:info 5/21/2019, 8:12:15 PM MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":
  zigbee2mqtt:info 5/21/2019, 8:12:15 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:12:15 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{
  zigbee2mqtt:info 5/21/2019, 8:12:20 PM MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"ieeeAddr":
  zigbee2mqtt:info 5/21/2019, 8:12:20 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"groups","message":{}}'
  zigbee2mqtt:info 5/21/2019, 8:12:20 PM MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":

I had the same problem with the message flood. The flow updates the device list every 5 seconds and the group list every 6 seconds.

I have changed this and added 2 Buttons to do it manually.
You only have to hit the buttons if your devices / groups have changed.

Changed Flow:

1 Like

Thank You xaziwb
That is perfect

dear xaziwb,

great idea for a solution!

do you have any idea what’s going on here?

the devices list of the original z2m admin panel went blank after adding the 10th device and has stayed blank ever since. Everything else works fine, I do get notifications in UI when I add a new device, just the list remains empty.

I tried your mod with the two buttons. The result can be seen in the screenshot. List is still empty. I assume the buttons aren’t to blame because the group button brings up existing groups to a previously blank group list.

Any help greatly appreciated.

the fault appears to be in the output somewhere. A click on the button produces the exact same log entry as when I hit inject “Request Device List” timestamp node The log contains all the details that should be in the device list output.

EDIT:
commenting out the “icon” line in the “Reformat for list” node makes the list reappear, just not as pretty :frowning: