It seems like every time I start an update it takes 2 tries. The download gets to around 80 to 90 percent then I get a failed message. I start again and it goes ok. This has happened on all 3 of the updates I have done so far. Not really a problem, just wondering why.
Also, it seems after an update I find a couple new apps installed that I didn't do. Or is there something else installing apps automatically? For example, Version 2.0.9.133 just installed. Now I have Maker API app installed, which I didn't have before.
I guess there's a few variables to think about.
Do you have reliable internet access, or is it intermittent?
Mine have knock on wood never failed from desktop.
I tried it once on mobile and I saw some odd results, I'll never try that again.
The unintentional installation of the Maker API App is something different I'm sure.
Either delete it and watch to make sure it doesn't happen again or reach out to support.
I would say either this is an internet issue as keithcroshaw stated or maybe there is an issue with the on-board flash and the image that is downloaded is getting corrupted. I would defiantly have support take a look at the internal logs in case there is an hardware issue.
I don't see the same, either. I've updated all 4 of my Hubitat Elevations to v2.0.9.133 and none of them have MakerAPI installed, unintentionally or not.
This is NOT to discount your experience, just to adding another voice saying.. yes, unusual, good idea to have support look at it.
Our internet connection has been very reliable. Not the fastest as the only thing available here is DSL. (Living in the boondocks). The update issue has happened 3 different times. It always goes the second try, just kinda wondering what might be going on.
As far as the apps. I can delete them ok. But weird they are installing themselves. I'll keep an eye on it with the next updates, whenever that might be.
EDIT: Just thought of something that maybe has an affect on the update. I didn't realize that the Portal wasn't a local logon to the hub. I had been logging on to the hub thru that always. Maybe that had some affect on the update. I just assumed the portal was local to the hub, kinda like my router which I can use it's name to log on to it or the IP either one which goes to the same place. I just found out to just use the IP when connecting to the hub.
