Closed craigmate closed 5 months ago
Have also started seeing this today
Also on me. Hope fix will come soon
I logged a similar error (Error #26) back in June 2021, and the owner asked me to use dig blitzortung.ha.sed.pl I did run this when I first saw the error an it wasn't resolving However, I ran it again and it appears to be resolving the DNS See the screenshot below
The integration appears to be working again now. So not sure if it was an issue with DNS or the MQTT server which it connects to
I will leave it open for any others, but if it is resolved. Feel free to close it.
Managed to check on DNS. You have right! It was resolving 0.0.0.0
adblocker thought it is ads
i whitelisted it and it appears again. thx for the tip
Looks like it's sorted itself, I use AdGuard but without whitelisting the DNS name it's started working again so maybe it found it's way onto a filter list and subsequently got removed
Hi..
I have been getting the following error for the last few hours
This error originated from a custom integration.
Logger: custom_components.blitzortung.mqtt Source: custom_components/blitzortung/mqtt.py:233 Integration: Blitzortung (documentation, issues) First occurred: 11:00:07 (102 occurrences) Last logged: 14:02:41
Unable to connect to the MQTT broker: Connection Refused: not authorised.