webCoRE for Hubitat Updates

The March 5th 2023 update was the first update in 2.5 months. And it was made after I wrote my post about this thread losing its purpose.

One update in 2.5 months can’t be considered “regular” particularly when there’s been releases every week or two this year.

As for:

“The more recent posts are mostly others speaking up when they have a problem with a certain Webcore related function, or something is not operating the way they are expecting it to within Webcore.

Do you really believe it is the best solution for a multitude of support problems to be mixed into a disorganised mega-thread whose topic was intended for update announcements? There is an entire category in the Hubitat forums dedicated to Webcore. In forums like this different issues are usually addressed in individual topics of their own. That’s just how things are usually done. Disorganised Mega-threads like this aren’t helpful.

Just some constructive feedback. That’s not really the issue I care about anyway.

But I do care about release notes being available. I’m a software engineer myself. Releases should not happen without release notes. It’s the duty of the software engineer to provide these. People need to be able to make an informed choice about whether or not to take the update.

I always take the “if it ain’t broken don’t fix it” route so I always look for release notes before I make a decision. Personally I think dedicated read-only threads work best such as the approach taken by the Hubitat engineering team:

1 Like

New update posted today, see note 1 for details.

Should be in next HE firmware release.

4 Likes

@nh.schottfam
can you please explain a little bit more about the " * updates for DST calculations on every schedules"? What does that mean?

Currently I have pistons to stop and resume every single pistone twice a year to fix the DST issue in time. Is this still necessary?

Thanks for some explaining words.

Someone pointed out an example of an every statement that had not calculated DST changes right, that is what was fixed.

If you upgraded and are concerned, you can pause/resume pistons that do this after the upgrade.

There is nothing wrong with what you may be doing now, (I understand why this was needed), I have been trying to stamp out any last issues.

2 Likes

New release is pushed out. Note 1 has details.

It is also available in latest HE firmware for built in.

2 Likes

Seems to be stuck on this...

Edit
Took ages, but worked

Hello,

The update from 1.0.76 to 1.0.77 keeps getting stuck on Updating Piston and shows Fatal Error and rolling back. HPM then finishes with an error. I'll post a screen shots as I'm trying again.

What am I doing wrong or what do I need to get this to Update?


All,

I deleted some Local Back-Ups (I assume these use memory on my hub). Then used the HPM Repair Feature for WebCore and it seems to have loaded fine.

Any thoughts?

Thanks,

John

I would be sure you hub firmware is up to date.

You can reboot before running the HPM update and let the hub settle.

Without seeing some logs, hard to guess what is going on.

I am up to date on the platform updates. I tried updating webCoRE with HPM twice. The first time it failed while updating 'piston'. I did nothing between the first and second update attempts. The second pass was completed without error.

Edit: Adding Log entries related to the above (app 417 is HPM):

I'm having the same issue upgrading with HPM from version 1.0.75 to 1.0.77. (C8 Hub on firmware version 2.3.5.130. The error occured on the previous version of the firmware as well).

HPM ends with the following error:
Error Occurred During Installation
An error occurred while installing the package: Failed to upgrade app https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/smartapps/ady624/webcore-piston.src/webcore-piston.groovy. Be sure the package is not in use with devices.

And in the logs:
app:702023-04-27 16:36:59.124infoFatal error occurred, rolling back
app:702023-04-27 16:36:59.117errorError upgrading app: java.net.SocketTimeoutException: Read timed out
app:702023-04-27 16:31:58.711infoUpgrading webCoRE Piston
app:702023-04-27 16:29:33.519infoUpgrading webCoRE
app:702023-04-27 16:29:32.901infoDownloading webCoRE Storage
app:702023-04-27 16:29:32.319infoDownloading webCoRE Piston
app:702023-04-27 16:29:31.803infoDownloading webCoRE
app:702023-04-27 16:29:31.366infoDownloading https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/resources/files/WeatherTile2.css
app:702023-04-27 16:29:30.934infoDownloading https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/resources/files/WeatherTile2.js
app:702023-04-27 16:29:30.470infoDownloading https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/resources/files/WeatherTile.js
app:702023-04-27 16:29:30.016infoDownloading https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/resources/files/HubiGraph.js
app:702023-04-27 16:29:29.432debugPerforming update
app:702023-04-27 16:29:27.279debugprefPkgVerifyUpdates

I've even tried to soft reset the hub - still experiencing the same issue after the restore when trying to update webCoRE.

Thank you.

you can try to save the file(s) individually.

The log shown above suggests HPM had a problem downloading from git (ie sounds like a network error)

In short I have not seen this issue and sounds like a networking problem that HPM is having

Thanks for the response. I don't know how to save the files individually, but I'm sure I'll be able to figure it out. (In case it might be essential to know - I've tried upgrading over a period of 3 days, getting the same error. In between, I did the soft reset of the hub.)

Just FYI: I tried to repair the webCoRE installation with HPM and received this error after about 20 minutes:
Error Occurred During Installation
An error occurred while installing the package: Failed to upgrade app https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/smartapps/ady624/webcore-piston.src/webcore-piston.groovy. Please notify the package developer..

Be sure the package is not in use with devices.

@nh.schottfam I'm currently not able to access "Register a browser" on PC and mobile on the local network, it's saying something about a certificate error?

Edit, managed to fix it on PC by deleting site data, still cant access on Firefox mobile..

There is a new version of webCoRE today with various fixes:

  • fuel stream NP fixes and cleanups

  • timegraph improvements (thx @tj4293)

  • http arguments fix

  • fixes for 'was' handling

  • Improved attribute options for device variables and allow choosing attributes available to a subset of devices (thx @ipaterson ! )

  • fix for user of statement restrictions on every statements

  • cleanups and optimizations

Should get into firmware in upcoming release for built-in users

6 Likes

I just wanted to define a device variable in one piston but no "Physical Device menu" is shown in the dedicated pop up menu (see shot below). Workaround for me was to play around a little bit until the menu shows up again.

Behavior was different in the past.

Did someone notice this too?
Running webCoRE local on a Raspberry Pi and using webCoRE version via HPM. Latest version from HPM. Need I update Raspberry Pi again?

Thanks

are you sure you pi files are up to date?

I just tried this with staging, and it seems to work for me....

@ipaterson - note the "Physical device(s)" twice...

will check the pi files and will let you know.

Updated my pi files today to the latest but still same issue, no Physical devices to define Device Variable :frowning: