Closed scargill closed 2 years ago
Are you actually triggering the node? Just having it configured won't result in anything, it needs an input to actually cause the node to activate. If you are testing things out try connecting a timestamp node at the front, deploy, then click the timestamp node to trigger.
Configuring the number of LEDs should be done in the WLED web UI.
Wheeee... thanks. Didn't think of that. Sorted.
Glad it worked!
Is it not working for you @scargill ?
Yes, sorry I left a comment but had an Internet failure today so the comment got lost. All is working but I did want to ask if there was any way your node could accept effect names rather than numbers - I found RAINBOW just by checking through the effects - {"effect":65} - but if it was possible to put in {"effect":"rainbow"} that would future proof against changes in WLED... or am I missing something...
If you are passing JSON directly to the node you are better off bypassing my node entirely and just sending it as an HTTP request to your WLED device directly, my node adds nothing of value in that situation.
A number is what WLED expects so that's what I take and send.
I'm suer its just me but I have a working WLED board,,, I indtslled WLED2 in Node-Red - and passed the Ip of the board, it SAYS it is connected, but in Node-Red if I select, say, ON and effect RAINBOW, nothing happens - am I missing the point? I'm quite familiar with both Node-Red and wLED but maybe I'm just as bit slow on this ocasion as I can't see why my LEDS which will happily select an effect in the WLED webui, do nothing in Node-Red. Put me out of my misery please?
Alsoi am I mising the bit that sets the number of LEDS?