Yesterday, I tried to add the MeteoAlarm sensor to my config after looking at the site and knowing there would be warning in Europe.
In the afternoon I was able to browe the site, but in the evening the new sensor couldn’t be added to HA. After that I wasn’t able to open the site over both Wifi and 3G. It looks like the site is down or that DNS cannot be resolved.
Can anyone confirm similar issues?
It’s not working for me either.
thx. luckily it’s not just me. or sadly…
Down for me also, I was wondering why the component was giving errors
DNS can’t be resolved. I tried to look at their WHOIS and the domain was registered 7June 2006. I guess they didn’t renew in time.
Same for me. Any alternative? Working on a special meteo-alarm card right now but without data it has no sense. 
I think we should be patient. It is only down for a day or so and it is Pentacost. It will probably/hopefully be fixed in a few days.
The site is up again
site is up, but the alert in progress is not shown in home assistant. Strange.
I’m also getting meteoalarm errors in my log:
2019-06-13 17:30:24 ERROR (MainThread) [homeassistant.components.binary_sensor] meteoalarm: Error on device update!
Traceback (most recent call last):
File "/usr/local/lib/python3.7/urllib/request.py", line 1317, in do_open
encode_chunked=req.has_header('Transfer-encoding'))
File "/usr/local/lib/python3.7/http/client.py", line 1229, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1275, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1224, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1016, in _send_output
self.send(msg)
File "/usr/local/lib/python3.7/http/client.py", line 956, in send
self.connect()
File "/usr/local/lib/python3.7/http/client.py", line 928, in connect
(self.host,self.port), self.timeout, self.source_address)
File "/usr/local/lib/python3.7/socket.py", line 727, in create_connection
raise err
File "/usr/local/lib/python3.7/socket.py", line 716, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Operation timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/meteoalertapi/meteoalertapi.py", line 35, in get_alert
file = urlopen('http://meteoalarm.eu/ATOM/'+ country +'.xml')
File "/usr/local/lib/python3.7/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
File "/usr/local/lib/python3.7/urllib/request.py", line 525, in open
response = self._open(req, data)
File "/usr/local/lib/python3.7/urllib/request.py", line 543, in _open
'_open', req)
File "/usr/local/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
File "/usr/local/lib/python3.7/urllib/request.py", line 1345, in http_open
return self.do_open(http.client.HTTPConnection, req)
File "/usr/local/lib/python3.7/urllib/request.py", line 1319, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [Errno 110] Operation timed out>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 261, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 377, in async_device_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/meteoalarm/binary_sensor.py", line 93, in update
alert = self._api.get_alert()
File "/usr/local/lib/python3.7/site-packages/meteoalertapi/meteoalertapi.py", line 39, in get_alert
raise(WrongCountry())
meteoalertapi.meteoalertapi.WrongCountry
2019-06-13 17:45:30 ERROR (MainThread) [aiohttp.server] Unhandled exception
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 447, in start
await resp.prepare(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py", line 353, in prepare
return await self._start(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py", line 667, in _start
return await super()._start(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py", line 410, in _start
await writer.write_headers(status_line, headers)
File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 112, in write_headers
self._write(buf)
File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 67, in _write
raise ConnectionResetError('Cannot write to closing transport')
ConnectionResetError: Cannot write to closing transport
Does anyone else have a working MeteoAlarm sensor?
Could the HA component have been blocked by MeteoAlarm?
For days I have the meteoalarm sensor at “off” state regardless that we had several yellow and orange alerts at their webpage.
Perhaps someone knows how to ping the developer?
The component, python library or website is flaky. The last time my sensor was updated is 24 hours ago.
{{states.binary_sensor.meteoalarm.last_updated}}
Lots of different timeouts and errors in the logs.
I’ve removed it now, it’s a nice idea for a component but if it’s not reliable then it’s not worth using IMO.
yes, not wanting to cross-post, please accept this link to another thread on the subject: Love the new Meteoalarm - how do I put the alert in a card?
Have to cancel the integration for now, hope to be of help when the dev takes it on to improve.
The component logging says that it times out because it takes too long to update:
Updating meteoalarm binary_sensor took longer than the scheduled update interval 0:30:00
15:30 helpers/entity_platform.py (WARNING) - message first occured at 12:00 and shows up 8 times
The xml is quick to load though:
https://www.meteoalarm.eu/ATOM/NL.xml
I’m not at home currently but when I am I will enable debug logging for the component and see what is happening behind the scenes.
hi, if you get to that, please have a look if this is explainable too:
Its safe so should show the mdi:shield-check icon… nothing really important, but it shows the integration isn’t functioning correctly.
I already know why that is the case. The component HAD set a fixed icon, instead of relying on the device class. This has already been fixed and will probably be released soon (tagged with 0.95.0b0).
The component will probably (hopefully 
) be updated in the next release.
The api update is also tagged with the same release.
Ok, thanks for the update, missed that, sorry.
Hope they also fix the attributes, or better said, the absence of attributes in the ‘Off’ state.