#Follow up

1 messages · Page 1 of 1 (latest)

deep kiln
#

@urban mantle Apologies on the delay It slipped my mind i said i would take a look at this for you. Its probably too late now.

#

As im not entirley sure what you wanted to do with the value one you got it I made two examples for you. The first shows you how to take in the incoming message and simply change the overall payload to the "description" i.e. "Hue dimmer switch" or whatever the value is using a Change Node. The second sets a global variable to the Description value using a Function Node assuming another flow may need access to it for example.

#

If you simly Import the flow.json file and interact with the Inject node (Used to inject the data you supplied) and the Debug panel in Node Red you will see this working. If you have an alternative case just let me know some more information and ill try to assist again sorry for the delay.

#

I hope this helps if ive misunderstood just let me know 🙂

urban mantle
#

hi @deep kiln , no need to apologize! We're all here in our spare time (or during work lol) so I completely understand.

#

The solution was very simple in the end, I just needed to put the payload through a json node first, then it became 'readable' allowing me to use the payload.data.definition.description and push the value through. I tried that before, but it didn't work then. I probably botched it then by using a change node first.

#

and thank you for your help, because that Global variabel was exactly what I was looking for in my next step! (delete last paired device incase something went wrong)

#

background info: I'm building a front-end solution to pair/rename devices through zigbee2mqtt

#

I got it working for 99%, just wanted to push through the vendor + description, so users can see what was actually added

#

all the rest I already had working

deep kiln
#

👍 Great stuff! Happy you got there in the end 🙂

soft vortex
#

(what's wrong with the GUI for Zigbee2MQTT?)

urban mantle
# soft vortex (what's wrong with the GUI for Zigbee2MQTT?)

nothing wrong with the Z2M GUI, but not everyone feels comfortable using it. Also I'm experimenting creating a Lovelace dashboard where 90% is built using auto-entities. The next step was creating a way to pair a device through Lovelace, make sure it get's the correct naming scheme so it's in the UI automatically.

soft vortex
#

Looks cool!

urban mantle
#

currently have this working now. When a device pair fails, the text will become red and Node-RED will automatically remove the device, so the user can try again.

soft vortex
#

Very very impressive

urban mantle
#

Only thing left is for a user to remove last paired device if needed for some reason (which I almost have done, now that I have saved the IEEE address as global state)

soft vortex
#

Do not hesitate to share when you are done 😎