I had this happen on my C-3 a couple of updates ago; I rebooted the hub, retried the package repair and the update then succeeded. The current update went through on the first try.
No warnings at all. Just asking if this would be a good way of putting to not increase the overhead. I have read the page you sent out but in there I dont see anything related to groupas of conditions nested in groups of conditions and processing overhead.
Might want to let the hub settle a bit after rebooting; I usually wait an hour or so before doing anything that would make it busier before stressing it with an app update (at least a sizeable one).
In the end, you piston 'wakes up' for any event it is subscribed to.
So wakeups depend on # of events that occur.
The piston could do something or nothing when it wakes up...
I would suggest just get things working as you want for automation. Then there can be a discussion/review if you think there are too many events. In general it should not be a big issue.
I have followed the instructions in note 2 and used the commands from @Tony (thank you!). Cleared all cache registries and security tokens and now I am not getting an error but also not seeing my pistons. Also, anytime I click on any of the links in the UI (dashboard, fuel streams, backup pistons, etc.) it redirects me back to the register browser prompt. I have logged out and back in a dozen times. I've rebooted the RPi twice and cleared all data and cache from my browser. Any other ideas?
I just noticed the same thing (blank window when selecting dashboard) when I have 'Use custom endpoints' set.
I normally don't use this setting; I do not set custom endpoints but just open a browser and enter the IP of my RPi when I want to use the local dash and that still works as expected (though I needed to log out of the local dash and log in with a new registration code from the WebCoRE app).
@nh.schottfam
I have just upgraded to the latest release of WC.
All my motion pistons are dead, not sure what else. The events are in the device logs but the pistons never fire. I can set my thermostat fine.
I have edited and saved a piston and it seems to re-subscribe,
Cleared the cache, did a HPM repair.
Can you post URL's for the previous code to downgrade?
EDIT Found a backup from 3 days ago so I'm back in business on 3.113 2022.0105
Subscribing to devices...
+258ms ║Device missing from piston. Loading all from parent (228ms)
+261ms ║Using Attribute motion subscription
+268ms ║Using Attribute motion subscription
+275ms ║Subscribing to Office Motion.motion...
I get an active event in the logs but the logic always fails on testing "motion changes" Condition 3 should be true, illuminance is = 0
+3ms
╔Received event [Office Motion].motion = inactive with a delay of 25ms, canQueue: true, calledMyself: false
@nh.schottfam Just starting in migrating 100+ pistons from ST to HE. Are there any plans to change the format of webCoRE global variables or the way how HE hub variables will be displayed within HE webCoRE (@@HE_hub_variable).
Just asking to get an idea what's the best way to revise my pistons regarding my global variables.