HPM will not update Govee integration v2. I get "An error occurred logging into the hub. Please verify your Hub Security username and password." I have my username and password on the settings page. I get a notification that update failed on my phone every day.
I will look into this shortly. What device driver is it failing on. On second thought, I don't think that error is related to the Govee Integration at all, but hub security using HPM. Do you have hub security enabled?
Yes I have security enabled. Other apps have been updated before the Govee v2 without any trouble.
You have any logging to indicate what the hub is doing when it fails?
I got this on HPM app:602026-03-02 01:47:09.707 PM Govee v2 device manager
Error logging in: java.io.IOException: Stream closed
error
Error logging in: java.io.IOException: Stream closed
What is dev 345? That isn't related to HPM.
Can you click on the "warn" button and see what device loads from it.
Can you please provide more log info around that error. those two errors in that last screen shot are from a device, so that would be nothing to do with HPM.
It looks like it is the Govee Driver trying to isntall somewhere and the driver is missing.
All my Govee devices are working and running automations.
Well that doesn't have anything to do with HPM. Those errors would be created by the Govee Device Manager trying to install a device. Goos thing is in most cases though it failed it doesn't impact anything.
Lets get back to HPM since that is what this thread seems to be about. What is happening with HPM.
What were you doing when that error was generated. That isn't related to the Govee Integration V2
You need to provide more information about what you are doing and what you are experiencing. That error alone doesn't really tell anyone much.
This is most likely pointing to the issue.
- Have you tried clearing your credentials from the HPM settings and then adding them back again to be sure they are correct?
- Have you tried turning off hub security and clearing the credentials to see if that works (as a test)?
1 Like
That was it previously I had tried clearing and adding back then I turned off the security without clearing first. What is the problem with leaving the security off I live in a rural area unless someone is in my driveway they aren't getting anything? I think the problem is from the govee app it spits out info 18 times a minute, Thanks for your help gentlemen I appreciate your patients and advice.
With the login security disabled, your only risk is people already on your LAN. Anyone on the LAN could access the Hubitat UI freely. So if your LAN is secure from outsiders, which it should be, it would be to keep out snoopers like kids, guests or a spouse.
External access is still secured with access tokens or by logging into the remote admin portal (if you have remote admin). This is assuming you do not have your hub directly exposed to the internet via port forwards or something else silly.
If you have an issue with the logs from the Govee app itself, you should post the logs on the thread for that integration.
2 Likes
If you are having a issue with the Govee Integration i can focus on that. I just need all the details about what is happening.
The driver failed error message is about the device trying to install a new child device. There are only a few things that would trigger that.
If you feel you are getting excessive logging can you show me all of the logging that is a concerning to you. I can probably make a few changes to reduce the logging you are concerned about. It is likely all informative instead of a problem. The more devices you have the busyer it will be as well which is important to keep in mind.
Can you check to see if you have "Debug Logging" turned on for the Govee Device Manager. If that was enabled, that would generate allof the the logging you showed above. Most of that is the Device scan that the Govee Device manager does on a scheduled basis. Simply put it hits a multicast port with a requet for all Govee devices to respond with their details. Then each device responds and the Govee Device Manager parses that response for each device. What you show above is largely the hub parsing those responses. You can also adjust the frequency of the Device scan action to reduce this type of processing being done by the hub.
Ok thanks.
