-
Hi,
you already send the config data in a proprietary format (SolvisSmartHomeServer//
It would be great, if you would (additionally) send the config data in the official Homeassistant format, which …
-
Add autodiscovery capabilities.
Tools:
- https://github.com/curesec/tools/tree/master/nsdtool
-
Hey, thanks for the great work. I miss a few things for be able to properly use kuma-ingress-watcher
It is already possible to customize the port through `uptime-kuma.autodiscovery.probe.port`, I w…
-
Hey @CarlosDerSeher , just letting you know that I found this bug and seems to fix it already.
When autodiscovery found my snapserver on the network, the first discovered address was ipv6, however …
-
## 🐞 Bug report
### Describe the bug
Deployed auto-discovery service with custom zap config and added volumes, but in ScheduledScan volume is emptyDir, but must be configMap.
### Steps To Repro…
-
### Is your feature request related to a problem? Please describe.
Those two newly introduced values are available via MQTT, but not auto discovered by HomeAssistant.
Refering to those commits menti…
-
I installed kodi-fcast-receiver to Kodi/Windows but couldn't discover it from any of my clients. Same with the provided `test.py` script. Wireshark shows no traffic to port 46899 and no relevant traff…
-
Hi Danito,
I just tried running your script in a LXC in Proxmox.
It seems to be working fine and it's connecting to my MQTT broker, but my sensors don't seem to get autodiscovered in HA ...
Thi…
-
We are using AlloyDB, which has a database like the auto-excluded `cloudsqladmin`, but called `alloydbadmin` (there's also an `alloydbmetadata` DB).
We have this config:
```yaml
collect_bloat_metric…
-
It would be nice to autodiscover the appliances. I see a few way:
* Some (all?) appliance regularly broadcast an UDP packet.
* I think you can do something with the existing dhcp discovery mecha…