I haven't been able to update Webcore for a couple of months now. Current version 1.0.87 HPM downloads version 1.0.93 but fails on the install producing this message.
SHOULD REBOOT HUB, wait few mins, then update webCoRE. HPM has had problems hanging on new HE firmware releases...may need to update files manually
If you update manually, update starting with piston file, fuel stream, any devices, and finish with the webcore main app.
1.0.94 - update for cloud gzip responses, updates to json logging, IDE improvement for timers, optimizations
1.0.93 - another time handling fix, and optimization, bug fixes
1.0.92 - update time handling for compler issue
1.0.91 - update time handling with sunrise/sunset
1.0.90 - update IDE operations during edit with variables
1.0.89 - Fix for hsmAlert events, cleanup azimuth and altitude sun calculations
1.0.88 - Fix for graph current value, fix for graph setting for http vs https, new location events lowMemory and cloudBackup, fixed marking of global variables in use, added altitude and azimuth to weather data, UI modules updates
1.0.83 - add asin, sin, cos function, update to allow piston setting custom timezone for sunrise/sunset
You may have to update manually.
I have been in discussions with @gopher.ny . The compile of the files happens pretty quickly. It appears there is post processing done to apply the updated files to the running applications, and that is what seems to take a long time. Victor has said he will look into it
I feel like a traitor since I moved to the HE embedded version; I miss the instant updates and testing of the fixes I ask for from @ipaterson and @nh.schottfam , great guys.
I don't seem to see a correlation between the HE version and the user app version.
How can I tell how far behind HE is?
I do use staging.webcore so at least the UI is current albeit in test.
Have you noticed any difference? I haven't installed the embedded version yet, even though I can apparently access my old pistons through it. Do I need to "transfer" them over in any way? I kinda like accessing them through the browser. Still not sure whether to change over or not.
The difference in versions is typically only a month or two max.
You do not need to convert either to built in, or to user install in general. The built in version is typically is updated quickly. I usually request this a couple weeks after user install is updated.
Do you know is there anything that HE people are trying to do for the update issue? I think it's weird that issue like this has not been solved and in the last 6 or more months none of the updates goes through.
The issue is primarily the code size combined with the way that the platform “compiles” the code when it is saved. Neither of these is a simple change, and technically the ability to utilize HPM to help manage the community’s code installs is non-standard (the manual code import is the supported standard).
Given these factors I wouldn’t be looking for a quick fix in the near future. Your best bet, if you don’t want to manually update, is to migrate your pistons to the built-in edition.
Just updated to the latest version here. I use tasker for communication between our phones and webcore. After updating I'm getting errors when I send a message from tasker to any of my pistons locally.
java.io.ioexception:gzip finished without exhausting source.
Can't say I have any clue what this means. Seems like the piston is still executing correctly it's just tasker that's throwing up an error. I can ignore the error in tasker so no big deal but wanted to check if this error is normal or if tasker is unable to handle the new gzip replies.