Well if you think the updates from HPM is causing an issue there is a simple fix, delete HPM.
You are going to need to focus on a specific device and give more details about the device for anyone to have any ideas. Just saying random devices randomly don't work does not give us anything to go on.
i shut off error reporting for some devices because
tonight the sengled light was not working because of a govee app update.
Seriously, that is not possible...
Not surprised you have issues with all those errors.
Easiest solution would be delete HPM, delete the Alexa app.
Disable the Alexa skill on your amazon account.
Set the Alexa skill/app back up again from scratch.
See if errors continue.
Do not add HPM back until this is sorted out.
how does hpm have anything to do with the hubitats updates? when a new version is aval it seems to stop working for some devices but works for others untill i do the update, rebooting without updating does nothing. i have also uninstalled the alexa app and reinstalled even left the alexa app off for a few days just to see well that has done nothing same problem. i will delete hpm and see what happens. i doubt it will do anything.
Depending on the app/driver updating it can be cpu and memory intensive temporarily.
If you are talking about the hubitat platform, this is not likely the cause of your issues. Hub updates being available DO NOT affect your hub. Hell, there are people here still run 2.3.5 just because they don't feel like updating. It's one of the wonderful things about hubitat. They don't force you to upgrade and if you don't like an upgrade, it's incredibly easy to roll back.
Did you delete everything from the alexa side so it stops trying to reach out to your hub? (removing the alexa app alone from hubitat will not do this)
Honestly based on a lot of your complaints, and the fact you say it's happening to multiple hubs makes me thing there is something more fundamental going on. For diagnostics I would recommend the KISS principal.
All hubs on a flat network hard wired.
Switch wifi to 6 and below and zigbee to 20 and above ( make sure both hubs are on different zigbee channels. One of 20 and the other 25)
Make sure that jumbo frames are not enabled on any switch or router.
eliminate unnecessary switches
Make sure both hubs are set to AUTO in their networking section.
Now.... Once that is done.
If you are still having zigbee/z-wave devices issues...
Check for any z-wave ghosts. Eliminate if there are any.
Look closely at the logs (device, and event) for any anomalous behavior. This can give you clues to a rogue device causing mesh issues.
Install @thebearmay's Hub information driver as well as webcore graphs and monitor CPU and Memory activity. This could also give you clues to where issues are at.
Again, it seems something more is at work here that no one is seeing due to lack of some information.
The Alexa app can throw occasional connection errors but it should be minimal, maybe 1-2 times a day at most is what I would consider normal.
If they are constant then it looks like you have a networking issue.
What is your internet connection? Is it reliable?
i have deleted all from alexa at least a few times . it is time consuming. i have changed the power and channel settings. i wonder if my daughters VR is doing something she has the whole set up with sensors for movement.
That I certainly cant contribute any advice to. I've never worked with any vr stuff.
Which VR system is she using? You mention "with sensors for movement", so it sounds like an HTC Vive or Valve Index system, correct? If so, those "sensors" and actually nothing more than very specialized Infrared Emitters, that the VR headset and hand controllers receive the IR signal from. Both the Vive and Index use a hard-wired connection for data and video back to the PC. So, no RF signal interference should be coming from any of that. Now, the controllers do communicate to the headset via 2.4GHz Bluetooth, IIRC. So there is a slight chance of interference from those. Do the issues only manifest themselves when she is using the VR headset?
Now, if she is using an early Oculus Rift VR system, the wired 'sensors' for that system are actually infrared USB cameras. Again, they will not interfere with the Hubitat hub. The controllers still use 2.4GHz Blutetooth, IIRC...
I have used HTC Vive, Oculus Rift, Samsung Odyssey+, and Meta Quest 2 VR headsets in my house. None of them have ever caused any issues whatsoever with my Hubitat Hub or any home automation wireless communications.
It will remove that error, so that's something 
But I agree, HPM is not contributing to your problems.
HPM does not run by itself EXCEPT to check for updated packages at midnight:13 seconds, OR whatever hour/minute you set in HPM's configuration. None of the "Unable to get app ID of the package manager" errors are on second #13, then we can conclude it's not the once daily automatic run and that HPM is being run manually. Although removing HPM will eliminate the error, just not running it will too. 
HPM has a very limited task: Get Code from the an Internet repository and put it into the hub's Apps Code, Driver Code, Libraries Code or Bundles location. It then checks for updates daily and if found, puts a green message in it's title. A few developers mark their Apps Packages to be run on install by using the "primary" keyword in the manifest. But HPM isn't running it, it just "clicks" the installed package, causing the Platform to run it.
"Unable to get app ID of the package manager" errors are usually caused by forgetting that HPM has been told to be the maintainer of the Package. Users manually manipulating the code typically causes a disconnect between the package and HPM. An UnMatch, followed by a MatchUp usually recovers from those manual events. HPM itself can have the same problem, and the message is explicitly saying so. The fix is one step simpler: UnMatch HPM. No MatchUp is needed for HPM only.
I think you're OK to delete HPM, just to get that error message off the list.
Changing Zigbee channels is a lengthy project. I know, I just had to do it. I'm still fighting ONE device that insists on dropping.
its the new Oculus with some crowdfunded wireless sensors.
There is no “new” Oculus. Meta bought Oculus years ago and has since produced the Quest 2, Quest Pro, and Quest 3. None of those systems use external camera for tracking. They are all “inside out” systems, relying on cameras built into the headset for both room and hand tracking.
quest 3 with 5 naretracker slime vr trackers. they are wireless trackers that hook directly to the rougher/wifi
Very interesting. Thank you for the details. Since those simply use an ESP8266 for 2.4GHz WiFi connectivity to your home network, they should not cause any issues with your hub's normal operation... Unless they are somehow flooding your home network with broadcast traffic, which could, in theory, bog any device on your home network down, including the Hubitat hub... 
So again, the question remains - Do the issues you have with Hubitat only manifest when the VR system is in use? Since those Slime VR full body trackers are battery powered, they should be turned off when the system is not in use, correct? How often does the VR system get used?
Also, have you properly separated your 2.4GHz WiFi channel from your Hub's 2.4GHz Zigbee channel? Make sure to only use 2.4GHz WiFi channel 1, 6, or 11 - with a 20MHz channel width. With that sorted, be sure to use Zigbee channel 15, 20, or 25. This will prevent WiFi and Zigbee inteference.
I'm with this guy even though it doesn't make sense. Lately I know there must be an update when my motion sensor nightlight stops working.
Are you using "Basic Rules" for these automations? If so, yes there was a bug introduced in a recent release. That bug will be addressed in an upcoming release.
"Correlation does not equal causation." In other words, just because every time your hub acts up, and you look outside and see that the grass is green - Does that mean green grass causes the hub to have problems? People will often only look at their hub when something is not behaving correctly. If it has been a long time since they last looked at their hub, chances are very good that a Hub Platform Update is waiting.
If you'd like assistance with troubleshooting your particular issue, I'd recommend starting a new thread where you provides the details of your setup. The community is a great resource in finding the actual root cause.
I do use basic rules. would that be why the devices stop working within the hubs app and threw alexa? is their another app that works how basic rules work that does not cause issues when updates are available. ps i rolled back the updates to 2.3.9.135 and dismissed the updates notification in habitats dashboard and it seems to be working correctly now. i wonder if a update will be released that does not have bugs isnt the point to update to get rid of the bugs ?
I’ll say again, this just isn’t a plausible explanation for why you’re having issues with your hub. I’m sure something explains the issues, just not the pending update notification in the hub’s admin UI.
Honestly it only happens when a update is pending/available. I tried so many different things from uninstalling device etc to rebooting the hubs to taking out batteries from devices rebooting my routers even throwing the main beaker on my house. the only thing that works is updating it when a new update is avail. maybe now that i have dismissed the update notification it wont happen but only time will tell. this is also not a new issue to me it has been happening for 2 or so years. i thought maybe a c8pro would fix it, it has not
Download the Hubitat app
