Hmmm…. So you have a newer firmware and I don’t have a firmware update available so that’s weird
That is strange. How did you check for the firmware.
I went to the device itself, no option there to update. Then I went to my profile and went to the firmware update section and nothing shows in there either.
In the lower right corner click on the little icon for your profile screen. The icon kind of resembles a person. From that spot there should be a option for firmware update. Click on it and it should scan and look for devices to update.
Yes, I did that, the only firmware update it shows is for one of my floor lamps, nothing for the extender 
Never noticed that before (the FW update option on that screen). Nice to know... 
@mavrrick58
I just noticed that I cannot set the color of the extender night light in Hubitat, these are the logs:
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_Mavrrick_Govee_v2_Life_Child_Light_Device_832.setColor() is applicable for argument types: (groovy.json.internal.LazyValueMap) values: [[hue:92, level:100, saturation:93]]
dev:5142025-12-28 01:44:58.001 PM
info
Smart Outlet Extender_Nightlight Level was set to 100
dev:5142025-12-28 01:44:50.777 PM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_Mavrrick_Govee_v2_Life_Child_Light_Device_832.setSaturation() is applicable for argument types: (java.math.BigDecimal) values: [50] (method setSaturation)
dev:5142025-12-28 01:44:44.368 PM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_Mavrrick_Govee_v2_Life_Child_Light_Device_832.setHue() is applicable for argument types: (java.math.BigDecimal) values: [20]
dev:5142025-12-28 01:44:38.927 PM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_Mavrrick_Govee_v2_Life_Child_Light_Device_832.setHue() is applicable for argument types: (java.math.BigDecimal) values: [50]
I just posted a code update to the beta to fix this. Please turn on the beta release and check for a update with HPM
@mavrrick58
I’m not sure what you mean “turn on the beta release”
Thank you very much, never saw that
@mavrrick58
Someone showed me the beta toggle and I updated Govee. Is it normal for the update to still show available in HPM after I performed the update. It will let me do it over and over and still shows an update to the Govee integration.
That is strange. I just performed the update on my dev hub and it only let me do it once.
@mavrrick58
Yes it is strange, the update must have worked because I can now control the color of the extender night light but every time I go back into HPM, the update still shows available. If I turn off the beta toggle the update goes away from HPM but as long as that beta toggle is on HPM shows an update for Govee integration
When testing on my prod hub i was able to reproduce it. Eventually i got it to stop though. Could you try a repair to see if it that fixes it.
I ran a repair on the Govee integration and then went in, the update was available, so I updated again. It went through all of the motions like a normal update. After the update was complete I went back into updates and the Govee integration was showing an update available again
I will keep looking at it. I don't think that should be happening. Both of my hubs finally got it updated. It would be interesting to see the "View Apps and Drivers Page". The beta parts should show beta next to the driver/app if it is updated to beta.
Hello all i just rolled out v2.2 with the Retry logic. This brings Beta and Stable back in together.
v2.2 inclues the following changes.
- Includes retry logic for LAN API devices.
- Adjustments to the UI for Scene retrieval.
- Adjusted default value for Lan Scne file to use device model instead of Device Type.
- Removed Curranted Lan Scenes files from default download.
- Adjust light Device drivers to default to Cloud API scenes under all circumstances were LAN API and Lan Scenes are not expicitly set.
- Added Logging to indicate Cloud API Processing repsonse time.
- Added Timeout value of 60 Seconds for Cloud API to prevent hub failures.
- Fixed EffectNum and EffectName Values populating properly after fixing SetEffect command
- Fixed Child Light Device to use proper commands for Cloud Light devices
This change has also standardized all of the code to version 2.2.0 for better tracking going forward.
Installed and all is fine. Ran a few quick tests with no errors. Awesome work as always @mavrrick58
