Open source hardware tend to get a much longer lifespan, and better quality overall. It would be so nice if Inovelli was innovative enough to make firmware for its devices opensource, so community could help with development and coming up with crazy new features.
Also, we really need to get OpenZwave OTA Firmware Update feature implemented, but this is something that community should do.
Hi all, I just wanted to add a little incentive and use case here. I need a solution to control my soon-to-be multicolor LED pool light. Communication to most of these lights (Jandy, Hayward, and Pentair) is done by pulsing the AC power to them on and off a certain number of times with certain timing. It seems that the timing is sensitive to around 1 second, which does not seem easily achievable from the SmartThings side. I would really appreciate being able to modify the firmware to manage this color change protocol from within the Inovelli switch.
Jandy actually makes different models of their pool LED fixture that adhere to other manufacturer’s control protocol (series-h for Hayward emulation, series-p for Pentair,…) so you can see all of the manufacturer’s color modes/inputs from within this one document:
I appreciate the work that is being done at Inovelli.
Does SmartThings not let you use delay/wait commands to space out your commands to do this through automation?
I could see conceivably doing this through NodeRed tied back to it and inserting delay commands between on/off…but I think that would end up pretty slow depending on how many colors you’re going through?
@chack and @Bry, exactly. You can add delays, but it doesn’t seem like I can make a device change on/off state faster than at a 1 second interval, which means it could take about 28 sec to complete some color change actions. Also, it seems as though the task is randomly descheduled during runtime, which can add multiple seconds of timing uncertainty. Do note, I am still an ST and webCoRE noob.
Not totally following the logic in the piston, but I’d try it this way.
Start by testing if you can get webCore to turn the switch on and off a number of times within short intervals. Disregard the variables for now. For simplicity, I’d stack the on, off, on, etc without a wait just to see if it works changing the color. Then if need be, add a wait in between each.
If that works, then figure out how to set a variable to get to the proper color by setting a specific set of on offs.
I’m suggesting this because manipulating the variable may take longer than simply turning the switch on and off.
Then again, it just may not work fast enough, but the instructions you posted state you get up to 3 second intervals.
EDIT: I just tested a piston with a 2 second on/off delay and it worked.