You have a trigger for the active statement and a condition for the inactive statement.
Try changing it to changes to.
IF you look in the left column you will see the lighting bolt.
At this point something is broken @nh.schottfam. This simple setup is not working under any of these recommended methods. Both Ifs are triggers and this is as basic as it can get.
It's because of the modified webcore.
Thanks for that effort @bobbles. I think this is a duplicate of yours and still no lights off.
Yeah. Looks the same.
What version are using?
I downloaded this about a week ago I think.
Unfortunately there is no version statements to tell you when it was last updated.
Is there anything in the logs.
Could it be that it is telling the light to turn off but the light is ignoring it.
Just trying to explore all the avenues.
BTW. When you have the piston open does the trace go green for the active and then change to green in the inactive statement with a countdown timer counting down against the wait statement?
Not exactly Netflix quality but this video shows that piston in action.
On my phone I cannot see what the logs say but I can see that the 'inactive' section goes green and the timer counts down and matures. Not sure why the light doesn't turn off.
Can you try this on a different type of light. A non-ikea one.
When you look at the logs or the events for the IKEA light do you see the turn on and turn off events?
Looking at the logs it looks like the 5 second timer starts. When it matures it starts execution but there is no statement to say an off command has been sent.
I'll look at mine and get back to you.
1 Like
Yes.
In my logs I see the command
'Executed Xxxxxxx.off' between the Execution stage started and Execution stage completed statements.
Looks like a bug then.
You can see what I mean below when you compare my logs to yours. (ON my mobile so difficult to highlight).
I see multiple others having issues with this new slimmed down build of WC and Wait.
Look down through those new posts related to WC.
@bobbles what's the github link where you got your most recent WC code from?
I was heavily into webCoRE on ST from the very beginning and did a lot of testing with Adrian.
I don't use it on HE as I have managed to do everything I need with RM so I haven't been following the forum much anymore.
I updated from post 768, 8 days ago just to have quick play as I was trying to do something that I could not do with RM.
Didn't need it in the end but didn't remove it.
@nh.schottfam, Love the fact that this has some life again. Reading through the latest issues, I have a thought. Since you 'correctly' forked this version of webcore without intending to merge it back (Again I believe that is the correct approach), we probably need a few specific things.
- A new name for the app - on that shows up in the apps section in HE. HECoRE or WebCoRE4HE or something.
- Any maybe, just maybe a different color scheme for the piston screen shots - so we all know we are really actually and indeed using WebCoRE4HE and the user is not making a silly mistake. For example, make the text that webcore auto generates and comments out - to be red instead of green.
2a) Or maybe something in the 'UI statement' in this screen shot. In effect change the version to v.HE.0.1
Just some ideas. I fear version management will bite you (us) in the long run if not.
2 Likes
