Closed bwp91 closed 1 year ago
Thank you! And thanks for fixing it so quickly.
My hat off to you again Ben. Kudos on seeing this unfold and being on it from the jump. Also being so on top of responses and cranking out updates to solve the issues as they pop up. Just updated my scenes and they all work like a charm again.
Btw, what was the underlying issue that created this entire AWS debacle?
Best get in contact with govee support for an official answer 😆
They seemed to close a method of subscribing to devices via AWS, maybe it was an old method of authentication.
Being careful what I say. But the new method the plugin uses seems to work well and get things back to almost how they were before.
What a week! 😅
Best get in contact with govee support for an official answer 😆
They seemed to close a method of subscribing to devices via AWS, maybe it was an old method of authentication.
Being careful what I say. But the new method the plugin uses seems to work well and get things back to almost how they were before.
What a week! 😅
Gotcha. No worries. I don't need to necessarily know "how the sausage is made." Lol.
As for asking Govee.... yeah, you saw me trying. To date still zip in terms of calling me back and the thread I posted got tier one salesperson boilerplate blow off language.
Again, thank you for all you do.
(And to all those reading this, ya know Ben has a paypal and a patreon. wink wink) ;)
There seems to be an issue with regards to the AWS connection the plugin makes.
Example logs:
Generally and when restarting
When controlling a device
I believe this is a Govee connection issue as this has started with no changes to the plugin. However I am also aware the Govee app is still working. So will monitor this for now.