Closed jscribbles closed 2 years ago
Govee plugin is behaving like the hoobs instance doesn’t have internet access…
Edit: Local network access yes but internet access no
I do restrict internet access to some of my devices through Homekit (using a Eero for my network), but I haven't changed anything in weeks, and the HOOBS Bridge in Homekit is set to "Automatic," not to "Restrict to Home".
Anywhere else I should be looking to test this?
Your box needs internet access. It uses the internet to connect to the APIs that are controlling your devices. The device may be local, but the security and command structure is not.
Restricting internet to a bridge device like this is not a good idea.
Description I've been attempting to fix what is apparently a common problem right now with an unresponsive box that can't use plugins or update to the latest version. That involves running the following command:
curl -sk https://dl.hoobs.org/fix | sudo bash -
Unfortunately, instead of fixing things for me, it's lead me to another issue. It's returning the following error:
sudo: unable to resolve host hoobs: Temporary failure in name resolution
I've tried my darnedest to solve based on other people having issues like that outside of the HOOBS world, but no such luck. I'm trying hard not to have to do a full reset on my box so I don't lose my existing plugins.
Version If I get the about info, it says 4.1.17, however my dashboard says 4.1.15 and notes that an update is available. (Hence the original issue I was trying to solve.)
Did you upgrade Please let us know if you upgraded from a previous version.
Maybe? I attempted to run the update but it always failed.
Pervious version If you upgraded, please let us know your previous version.
Did you orginally upgrade to HOOBS 3 from HOOBS 2.1.1? Did you perform an upgrade from HOOBS 2.1.1? Some things are different.
What device are you using? Please let us know the device you are running HOOBS on.
List your plugins Govee
Post your config
Post your log You can get the log from the interface. This is in the Log section.
Additional context That log is just from today. There's a whole lot of plugin site unavailables that I was getting previously if I'd tried to install new ones as well.