Ok, do you gwt any errors in the logs? When you send notifications from other integrations do you usethe notify.notify service as well? When you execute the automation manually, do you get the message?
This is a horribly difficult and unreliable integration. Or, to be more precise, a terribly unreliable service from metro alarm. I use it since its inception and the binary sensor often isnât there when you expect it looking out of the window also, when it is available and you check the website source, a completely different code might be displayed.
Long story short: can you check the template itself in the editor to see if it is alive and what the result is ?
I mean when the binary_sensor changes to on by itself.
How did you test this automation? Did you set the state of the binary_sensor manually to on from Developer Tools â States? If so, this is not going to work, this will only temporarily ovverride the state of the sensor and the attributes also wonât appear.
You need to wait for the sensor to change the state by itself, then youâll also have the attributes and your notification should work.
and this is the issue, the service doesnât deliver a spontaneous change, or even a manual update through the update_entity service. As example, I am still seeing the Flooding alerts while there has been a snow alert for 2 days now. It must have something to do with the âeffectiveâ and âexpiresâ attribute.
Also, we get a âwrong countryâ error, while the conf hasnât changed since original configuration, and the setting is 100% correct @hjalmarr donât you get wrong country errors in the log? Seems you are suffering from something like that
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 358, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 466, in async_device_update
await task
File "/usr/local/lib/python3.8/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 88, in update
alert = self._api.get_alert()
File "/usr/local/lib/python3.8/site-packages/meteoalertapi/meteoalertapi.py", line 26, in get_alert
raise(WrongCountry())
Hi @Mariusthvdb no, I donât get any error in my logs. I fixed it now for myself to use country NL with language NL and province Limburg. If I go to country BE, I only can use the FR language which I donât want
PS: I also tested it, and with the automation the push message will be send correctly. But I hope I can somehow use the ne language?
I wouldnât know sorry, but it seems you really want your info to be geo-locationally correct, first of all and language is of secondary importance.
You should raise an issue on the integration though, maybe it is a core HA thing. If its on the server Meteoalarm side of things, I fear thereâs nothing much that ca be done
If the info you get back is bi-lingual, canât you template the dutch part? Itâs what I do on the Weatherbit icon that is bilingual too:
o nice, hadnât seen that before. Though, I wonder what the advantage over the core integration would be considering the identical issues described in the disclaimer:
If by any reason the server becames unavailable or sends an error status (and this happens a lot with meteoalarm.eu!) the sensor becomes unavailable too , if in the next update the server is ok, it becomes available again .