-
### Describe The Bug
Upgraded to v2.1.0 and recieved a new 403 error
### To Reproduce
Upgrade to v2.1.0 and restart the plugin
### Expected behavior
No error messages
### Relevant log output
``…
-
Hi,
I was using Bonob a while back and recently came to play some music and found it no longer working.
When i check the logs i can see its configured correctly to register with one of the sonos…
-
During testing #17812 I discovered that thing discovery is not working.
```
2024-11-30 19:02:05.127 [DEBUG] [govee.internal.GoveeDiscoveryService] - starting Scan
2024-11-30 19:02:05.264 [DEBUG] …
-
I have set up the HA Add-on and added a hub with the entities I would like to expose. Scanning the QR code or manually entering the code in either the Alexa app or via the Android native matter setup …
-
Hi,
since pimatic 0.9 devices can be automatically discovered. The current pairing process takes place in Z-Way, therefore, it should be possible to check Z-Way for its devices and show a device li…
-
In case when a user have provided a subnet address , Instead of right away triggering discovery, first the user should be provided with list of sonic devices with system info so that user can select o…
-
Hi, sometimes you don't remember which device is which but if you can look at the Vendor MAC it's easier because usually devices are from different manufacturers. Port Authority has that and here's th…
-
Add discover in discover adapter.
After device discovered automatically.
Sync device info in admin config.
-
I have noted that this plugin treats the connectivity board as the main "device". Being that this platform is highly modular, we need to design the plugin to be module and discover devices as such. I…
-
I've noticed whenever I restart the service on my satellite that I get a new device discovered in Home Assistant. Is there a way to stop this whenever I restart the service?