I just tried moments ago with a manual update and got this:
Any suggestions?
What version of FW are you on?
Something quite old (but still specifically unknown), according to another topic they started for the same problem. 
I am having an issue with local variables inside pistons. Maybe I'm losing my mind but I remember if a local variable was set, the variable contents would remain in tack when saving a piston. Now any local variable gets erased after the save.
Another oddity is when opening up a piston the local variable use to populate almost immediately. Now variable take upwards 5-10 seconds to show the contents.
there was a bug, ensure you are up to date in webcore
If user install do a repair
I’m not sure if it’s the same/similar issue. I’ve noticed recently, that after a hub reboot, I suspect variables don’t retain their previous value.
Yes, that is what is happening to me too. I checked and it looks like I'm on the July 6th update. I can't using Package Manager anymore because it times out so I have to manually update. The webCoRE Piston module takes a very long time to update.
The August 8th update fixes the variable problems.
It's the same problem. Update to Aug 8th update.
Package Manager no longer handle webCoRE because it times out.
Manually updating webCoRE Piston took over 9 minutes so maybe webCoRE is getting to big to handle.
Just a little update. After I update webCoRE every single Piston I have fired making for an interesting experience. Lots of things happened that should have but, all is running stable now.
For those of you who run a local WebCoRE dashboard, I wanted to share a fork of the existing dashboard where I made some quality-of-life improvements.
tl;dr works better on mobile (iOS Safari), reverse proxy https support, no cloud dependencies except backup (e.g., can login without cloud auth), lots of minor bug fixes and improvements.
There are no changes needed to the Hubitat Apps. I did end up modifying some of the libraries used by the dashboard to fix some underlying upstream bugs.
Not all of these changes make sense in the cloud version since I removed some functionality (Fuel Streams, Dashboards, Google Maps), but if I get some free time, I'll open some PRs to backport some of the improvements.
Here is a change summary:
- Fix: Mobile experience is improved (drag and drop, right click works).
- Fix: keep linebreaks when displaying comments.
- Fix: Ordering is retained when drag/drop of long lists.
- Fix: Expression outputs now wrap so you can see everything and can also copy the output.
- Fix: Device filter is retained after selecting a device in the device picker.
- Fix: Expression editor no longer overflows and expands properly.
- Fix: No scrollbar on left nav menu unless needed.
- Feature: Variables can be duplicated.
- Feature: Login without using the webcore code by directly providing the link, so there are zero external cloud dependencies.
- Feature: Switch between local and cloud endpoints.
- Feature: Show cloud and local execution URIs for each piston.
- Feature: Set a default category and select the category you want the piston in during creation.
- Feature: Supports arbitrary hubitat endpoints (e.g., use a reverse proxy). HTTP/HTTPS must match with signed certs.
- Feature: All dependencies are local (except piston backup).
- Feature: Docker build minifies all assets and runs on Alpine
- Feature: Added debug view in settings to see all local state.
- Feature: Enabled Variables, drag/drop and advanced statements by default.
- Removed Google Ads, Google Maps, Dashboards, Fuel Streams and device list in piston editor.
- Minor UX color improvements for consistency (still some work to do here)
- Debug output of all local client storage
Repo is here: jake9190/webcore-docker. Just clone and run docker compose up -d --build
It's been a while since I manually updated webcore in my C7. Can anyone provide instructions and links as I've forgotten the order of updating and where to get the updates from.
Thanks
Determine first if you installed the built-in app, or if you used the community source. You could have copy-pasted in the code directly, pulled it from a git repository, or used Package Manager, if it is the community version.
If you have Package Manager and it shows installed there, update from Package Manager. If you have the built-in, you should be on the latest version if you are on the latest platform release.
In post #1 you will find the instructions and links for a manual refresh.
Open each link Github for WebCore, Piston, select RAW and copy/paste onto the matching code on Devices code. Make sure you have the Dev switch (Show advanced/developer options) on in Settings so you can see this tab. Then just Save and it will recompile the new code.
If you have a C7 and the HPM install I believe and update will timeout.
I have a situation that has been going on for at least a year where devices, such as lamps lose commands such as on/off. Below is an example. I have three bulbs I wan to turn on. When the piston executes it will turn on the first two but fail to turn on the third device as the end of the list.
I have using full logs tracking what the piston is doing and from the log's standpoint there are no errors. Looking at the event of the lamp that didn't turn on, I see a command-on being issued by WebCoRE but alas, no light.
This would seem to me the issue is not with WebCoRE but a failure of the hub to follow through but, if I edit the piston and then save it, the piston will turn on all three lamps as it's supposed too.
I have done a soft reset thinking I have database contamination but that doesn't correct the issue.
I'm running the stand alone version and on the latest version however the situation I'm laying out here has been at least a year, probably more.
Has anyone ever run across this problem? It happens so rarely maybe it gets missed? Anyway, just putting it out there to see if i'm the only one.
Something to try as experiments: command execution delay. (1/2 way down this article)
You can see in devices view of console the commands issued also.
Yes. It looks like WebCoRE is doing everything correctly. The only reason I question WebCoRE is the problem resolves if I do a edit/save. It acts like some type of data contamination that gets corrected when the piston gets saved. Does webCoRE have it's own database, or is it part of the hub itself? I was thinking if I backup all my pistons, then delete and do a restore whether that would flush things out.
ensure you are on the latest webCoRE. I'm not aware of issues in the latest.
I am. This isn't a new thing. Every once in awhile I find this kind of issue and I edit/save and move on. I may try and covert over to the internal webCoRE but I just haven't found the courage to do so.... yet.
One thing I do when things like this happen is turn off the pistons smart state option and force it to do the on/off all the time.
I had one bulb last week that refused to work in the piston but was fine in the devices tab.
Turned off Command Optimization and Voila, the synced up and now works again.
I am on: