node-red-indigo

[am I missing something or is there no home for discussion related to the Indigo node-red contrib: https://flows.nodered.org/node/node-red-contrib-indigo?] Not sure if they are actively maintained?

I've been experimenting with using these nodes (as an alternative/complement to MQTT). They work very well testing on the local Indigo machine but the Indigo connection node is hanging node-red when used on a remote machine that in all other respects runs node-red perfectly (an RPi running ChirpstackOS).

[jay (support)]

That's a 3rd party plugin. It's been several years since that Indigo user has posted on the forums, so my guess is that he's moved on. It seems unlikely that it's going to work with the next release and beyond.

I use Node Red for some applications that I can't do in Indigo, The Indigo Node doesn't work so I use the mqtt nodes and then I use the shims plugin to make devises.


Sent from my iPad with Tapatalk

damn!

That's a 3rd party plugin. It's been several years since that Indigo user has posted on the forums, so my guess is that he's moved on. It seems unlikely that it's going to work with the next release and beyond.

As Jay foreshadowed, I can confirm that the most recent (i.e., nearly 5-year-old) release of the node-red-indigo-contrib palette is not compatible with Indigo 2022.2.0.

Looks like I will need to rework most of my node-red flows to go through an MQTT broker instead of controlling Indigo directly via node-red-indigo-contrib. <sigh>

You will still have to do a change but you can use the new HTTP API | WebSocket API to control Indigo from Node REd. That is what I am now doing. You don't have to use MQTT.

Thanks Jon. I will check that out.

You will still have to do a change but you can use the new HTTP API | WebSocket API to control Indigo from Node REd. That is what I am now doing. You don't have to use MQTT.

Would you mind sharing an export of one of your node-red flows where you have this working?

ditto would like to switch to websockets but I cant seem to get it to work. I can read the all devices definitions feed, and can appear to push a json to ask for a specific device, but not join the 2, unless its not possible with standard node-red websocket nodes.

Got it.. realised that the array values for onOff State of [0] amd [1] flip between true and false, with [1] representing current state.

So you need a
"websocket in" node using this url from docs "wss://your-reflector.indigodomo.net/v2/api/ws/device-feed?api-key=YOUR-API-KEY"
json parse node
switch node based on property msg.payload.objectId. and == your device id
switch node based on the specific value you want to filter on, for my I wanted different actions on true and false, so I used Property msg.payload.patch[6][2][1]. having looked at the json object, and copied the path for the value I wanted.

Hope this gets you moving in the right way. and not down the same rabbit hole I went triyng to get javascript running in nodered!

Simon

Thanks. I couldn't figure out how to get websockets working, so I ended up converting all my node-red-contrib-indigo dependencies to MQTT subscriptions via FlyingDiver's MQTT Connector/Shims plugins.

Not sure what I would do without FlyingDiver (Joe). Half my house runs on his Indigo plugins. Thanks Joe. You're awesome!