Did you install with HPM. Please open HPM then scroll down click on the option to "View Apps and Drivers". Thst will display a list of what is installed via HPM. Scroll down until you find the Govee Integration V2 and look at the list. If you do not see that deiver listed scroll down to the bottom and click on the Main Menu button. Click on the Modify button, and then select "Govee Integration v2" from the drop down. Make sure the "Govee V2 Air Purifier" is selected and then click on Next in the lower right corner. That should install the missing driver.
If it still doesn't work but is selected run a repair from HPM for the integration so it downloads everything again.
I'm just getting around to installing V2 but my API key doesn't return any devices... On the old V1 App page, I see this... Is it the same API key or do I need a new one?
With the number of devices have you can poll as frequently as every 35.3 seconds
You have 9488 of your 10k Daily APIv1 Calls left.
You have null of your 100 Daily APIv2 Calls left.
EDIT:
I applied for and got a new API key... I then deleted V1 and installed V2 with the new API key.
I now get this error with the V2 app... Its not showing any devices...
java.lang.NullPointerException: Cannot invoke method apiKeyUpdate() on null object on line 572 (method updated)
You should be able to use the same API Key. I also suggest running the V1 and V2 integration together for a time when migrating. The V2 version was written to allow it to run side by side with the older versiob so you could take your time with the migration and ensure everything works.
Those lines were remove from the Govee V2 integration app because the new APi currently isn't returning the data. If you are seeing those line you are still using V1 Code and need to update.
I looked at the code and that error shouldn't cause a problem at this moment. It is just saying it can't call the method used to reset thr API Key on the child devices when you change it in the app.
First please make sure you are running v2 from HPM. Maybe even go into the Apps and drivers page and make sure it is V2 that is loaded. If the devices are not listed please click on the device refresh button underneath the drop down to see if that will kick it. If nothing shows up you could turn on debug logging and then try again. The send me the loggs so i can see what happened when you went into the app
I couldn't get V2 to work at all. Not sure if something was down on the Govee side last night? In any event, I did a full repair from Package Manager, deleted V1 and cleanly installed V2. I even did a reboot to make sure.. V2 would not return a list of devices at all.
I removed V2 and re-installed V1. V1 found my devices and I was able to add them back... Very weird, but V2 just wouldn't work...
I wanted to upgrade to V2 as I assume at some point you or Govee will abandon the V1 api... But I'm back on it for the time being...
I might try it again alongside V1, but not sure I should mess with it for a bit... I did see a random post by someone else last night talking about Govee devices not working... Maybe the api was having issues?
If you look back in your logs did you get any errors.
The v1 and V2 install's are completely independent. You should be able to run them side by side.
I would suggest you restore from a local backup to get all your devices and automations in a good state since those could of gotten hosed when you uninstalled v1. You will need to update your API to get that working since you got a new one. Then install v2, put in your API Key. and click done. Then go in and turn on Debug Logging and click done again. Then go to the menu for the "Standard Device Add". Once you click on that it should retrieve the Device details. Go look at your live logging and send me the details. It doesn't make sense that it wouldn't work. I uninstall and reinstall it constantly on my dev hub.
I am already not making any changes to V1. At this point it is static and just there incase someone needs it. V2 is pretty well hashed out now as well as of the last few changes unless we find bugs that i introduced on accident . Well or if Govee adds new functionality like they have been.
Quick question: Is there a reason why some scenes are missing in my Hubitat device? For example, I have Lightning – A, Lightning – B, and Lightning – C in the Govee app, but in the Hubitat device, I only see Lightning – C.
If you have the device setup with LAN Enable turned on and Local Lan Scene Control turned on. You are using scenes that have been currated by me or others that have contributed.
The app has scends added occasionally as well so there may be some in the app that haven't been added.
You can add it though if you want by extracting it using the Smartapp and then adding it into the file for that device type.
After a deeper look i see scene number 400 so that is from the cloud. I can't answer that as it pulls that from Govee. You may want to ensure it is enabled for that device in the Govee Home App and then click on the sean load button in hubitat.
@mavrrick58 Trying to upgrade to v2 and can’t get any drivers to install. I installed the standalone app just fine but when trying to add drivers, I get the same error shown in photo. I’ve tried for each individual driver and all at once. Can you advise
When I was first getting the errors, I uninstalled and reinstalled with no drivers selected, got the up running with my api key and couldn’t add my lights (no driver). So I went and tried to install just the color light drivers. They failed with the same error shown above. I then read that you recommend installing all drivers, so I tried that. The pic I sent is the error I got then because that driver is the first it tries to install
Can you try the install again and capture the error from Live Logging from HPM. I am not sure why you are having this issue. I just installed this on one of my hubs and it worked fine. I will try a few more things to see if i can get it to fail.
I tend to recommend installing all drivers just to prevent you from having to go back and add them later. Some folks don't want all the drivers though, so it is perfectly reasonable to not do that if you don't want to.
Lets first try unmatching the Govee Integration and then matching it backup. If that doesn't work can you try removing HPM and then installing it again.
Open HPM. Click on "Package MANAGER Settings" at the bottom. Click on "Removed a matched Package" at the bottom. Select the "Govee Integration V2" and click on Next, and then next again and it should unmatch it.
. Well or if Govee adds new functionality like they have been.
