Thanks for the update! Much appreciated. If you get to per segment brightness/on/off someday, that'll be even better, but the changes you made will definitely help.
I think the per segment brightness adjustment may have been added with the last update as I don't recall seeing it before and I just updated all of my nodeMCUs this week. It may very well be scaling the RGB values together instead of adjusting overall brightness but that would make sense. I wonder if that would affect the "stepping" in brightness I get when my one strip fades on and off because there's not a lot of resolution as I run it at brightness of 8 or does the brightness paramater just scale the RGB values through the step automatically anyway?
You're right, looks like 0.10.0 introduced some settings at the segment level. Should be able to turn on/off individual segments now. I haven't thoroughly tested it. Let me know if you run into problems with the latest commit.
I have a second one I am working to get running correct wleds is installed and working but something is wrong the led strip never turns on. Frustratingly it's a clone of the one I have working (Dig-UNO by Quindor). The blue light on the one that isn't working is NOT on but I don't know what if anything that means....
I'm having a problem aswell, can turn my strip on but not off, also it dosn't seem to update the status if i turn it on via the app. Running the latest driver and version 0.10.0 of wled.
Thanks for your work on this code. I was able to get the integration working on one WLED on a D1Mini. It works well and I have it in a rule that works well.
Now, when I try to add a second one, it doesn't work. When I try to turn the light off or on, it doesn't work. The error in the logs is
something went wrong: org.apache.http.client.ClientProtocolException
I'm mostly using the MQTT driver but I have this one installed on one WLED instance.
This one is far easier to set up, no need for an MQTT server. Just remember to put http:// in front of your ip address. It responds instantly. Picking effects is a bit cumbersome as it expects numbers to be entered.
hi all. can't figure out how to change the intensity / speed via webcore commands. Is this possible?
This is all I can see. So at the minute I think I need to set some options through wled itself, then as long as nothing changes, I can control the simple stuff from webcore.
Was hoping there might be a way of controlling more from webcore without needing to log onto the web interface / or click on device options... to automate as much as poss.
Am I not quite grasping something? Any help much appreciated =)
This might be foolish, but is there a way to deconflict this and Prismatik? I'm using WLED and Prismatik for reactive bias lights, and have this set up as well, but I think as long as Prismatik is running commands from this will effectively be overridden. The real goal is just to be able to have real on/off control either from a button or by voice.
Sorry, don't use WebCORE so couldn't really help with this one. The setEffect command takes multilple arguments which include speed and intensity. It's a custom command though, so it might not be supported by WebCORE?
for them to work.
