any updates on this? Is the update working now?
2 Likes
So at some point in one of the hubitat updates or webcore updates a few of my pistons nolonger work. They are all related to HSM. Specifically related to intrusion detection and intrusion-delay detrction. here is my piston that was working, and now nolonger works. Nothing in the piston has changed. my arm and disarm pistons still work.
Its like hubitat has changed the executes command and is nolonger "Intrusion Away" or "Intrustion-Delay"
Any way to find out what is uses now?
Ok I have done more testing, when an intrusion triggered in hubitat, webcore use to be able to detect this with and event alert, but now that nolonger triggers for intrusion or intrusion delay. Hubitat has changed something and not sure what. verified my friends stopped working also. Using latest webcore and hubitat version (c8)
Please don’t cross post Issue with HSM since updated to Current version.
Check your Location Log events. At least for mine, it appears that the event is a combination of intrusion and the mode, i.e. intrusion-night.
I tried tondelete one last night but dont have permissions.
Anyway the log does not show anything other than intursion and intrusion-delay. Or am i looking wrong.
It would be good to see piston logs (medium) for the piston executing thru these events.
I will get the logs when I have time. I did look ant them and could see the arm and disarm, but the intrusion / delay intrusion never triggered it. But I will still get logs after I rerun it again.
Have not had time to get the logs and test, but i did a workaround for now and created 2 virtual switches and used rule machine to turn them on based on intruder and intruser alert.
For now i will use this. Have my daughters wedding saturday so its a bit hetic now. Lol. Will come back here and post logs when i can.
Any news on this? Sorry guys, for bothering you. But currently an update of webCoRE isn't possible. Ends up in a fatal error. Are you still investigating or is it necessary to think about moving to the native integration? I don't know what that means. But I think any indication if there is a solution on it's way is really appreciated.
Please don't get me wrong, I just want to understand what are the next steps with this.
Thanks
This is not true; you can update the code manually. See the post above: webCoRE for Hubitat Updates - #1927 by thebearmay.
For the issue itself: there is a beta of the next platform version in testing, though I don't recall any fixes for this particular issue at the moment. And there is, as usual, also no timeline for actual release date--but I wouldn't expect any changes until whenever that is, at the earliest, given that 2.3.7.x is likely done at this point.
1 Like
Thanks @bertabcd1234 for your reply. As I said before I don't want to blame someone, I just want to understand.
I haven't tried to update manually because of this post: webCoRE for Hubitat Updates - #1928 by maffpt
Sounds like even the manual update is not going through.
I was able to manually update mine with no issues. As to understanding, the developer said he was looking into it and it was not going to be a simple fix. So they don't completely understand how to fix it yet. So either manually update or wait.
I’ve tried unsuccessfully to update manually.
The hub I’ve tried is a C-7. Which one is yours?
I think that, as the app is quite large, the processor can’t process the compilation/syntax check before a timeout occurs. If this is true, I believe that the solution would be split the app on two or more files - file + library maybe?
1 Like
If the manually update works, fine. If not it's nice to know any backup solutions. To decide on my end which is the next best step I would like to know what's the current status. That's the reason why I asked again.
Haven't heard a lot since this started 11 days ago.
Good for you if you were able to fix this through a manually update.
Manual update worked for me. The piston file took a while to save, but I just left it to do its thing and it worked fine.
1 Like
Which hub do you have?
All I did was a repair and all is fine
The C7
1 Like
That definitely seems to be the issue with HPM installations of webCoRE Piston. However, that is not the case for manual installations. I've had to use manual installs for webCoRE for several months (due to the HPM timeout issue) because the HPM installs failed every time. However, manual installations have always been installed properly. So, I don't believe there is a universal timeout issue for manual installations like when using HPM. Something else is likely going on with your particular environment to cause manual installs to fail.
I have Webcore installed on a C7.
Was only letting you know that it is possible, as I had no issues. I will say it took a long time for the Webcore piston code to save. So make sure you wait long enough, walk away and come back.
2 Likes
