Is it really necessary to have the conditions be so drastic? You want them off at sunrise, right? Why only turn them off IF they are ON and IF they are at 20%? Why not just turn them off? The problem is the bulb says its switch is “turningOn”, not “on”, which is not according to standards. So the problem is with the hue bulb, the switch attribute never became “on”.
has something been changed in the last update to do with the “changed in the last” condition?
I have pistons set to use the “changed in the last” condition and they have worked exactly as expected up until last night after I updated to the current version v0.2.0bd. now whenever i check the TRACE it shows that the most recent trigger doesn’t update the Changed in the last count but the second trigger of the same piston does?
Is there an option anywhere to use something like “changed to ON in the last” or “Changed to OFF in the last”
So I’m not going to say whether this solution is better or worse than yours, but it’s a different way of getting a similar result with an AC unit that doesn’t have discrete power on/off commands, just a power toggle. The structure would be largely the same for you, just replace my http calls with your Outlet 5 instructions.
I created a Simulated Switch in My Devices named CJ AC 2 (Switch 15 in the screenshot) and in the piston itself have a variable that can be “on” or “off”.
If the CJ AC 2 turns on the variable get’s set to “on” and the http call fires. Same for off. If something sends CJ AC 2 the on command and it’s already “on”, then the piston does nothing.
I like this solution because it allows other applications/routines to interact with the AC unit without having to edit anything in WebCore.
I originally assumed you were getting in a weird loop (and maybe you are) because that piston can effectively trigger itself, but when I tried to replicate I got things like this in the logs: Skipped execution of physical command [Play Room Lamp].on() because it would make no change to the device
So if WebCore is short circuiting like that then I would think you’d be ok. Try turning on parallel execution for the piston in piston settings.
ok, need some help. I have a piston that works my fan for auto on and auto off based on temp. Here is the issue, the auto part works fine, but I Have zero manual control. If I try to turn the fan off it turns right back on and if I try to turn it on it goes back off. How can I control it for auto and manual in Webcore? I have added the TEP, but that did not fix the issue.
hi all, this has probably been answered to death but because of the size of this thread… what’s the current best practice to actually pause a piston for x amount of time. can pause piston + wait + resume piston work if it’s doing it to itself? or what’s the correct way to do a variable comparison to $now - only run if you have not for 120 seconds, thanks