Update: The developer of the integration is located in Kiew, Ukraine and did not respond to any request since summer 2023. Perhaps he is serving in the army…
First of all. I hope all is fine with Alex!
I can confirm. I have no more sensors since the 2014 update. Perhaps someone else has a clue where to look for?
Thomas
I went through the changes on the 2024 versions and the only thing which could be related ist the following change:
Changes to EntityDescription data classes | Home Assistant Developer Docs (home-assistant.io)
Switched to this integration (via HACS):
At the moment is working fine…
Well, this is fetching data from the cloud, not really the same as this integration. I have template sensors doing that for me meanwhile!
I have tried the other integration but can’t see any entities.
JUPPPO, did I get you rigth that you are using template sensors instead any integration to get the data from the mobielalerts sensors? If yes, how does it work?
would you please make your template sensors configuration public?
Sure, but it pulls the data via REST from the MA Servers, not locally:
# Mobile Alerts
- platform: rest
name: aterm2
unique_id: MobileAlertsCloud
json_attributes:
- devices
resource: https://www.data199.com/api/pv1/device/lastmeasurement
method: POST
headers:
Content-Type: application/json
payload: '{"deviceids": "XXX,XXX,XXX,XXX,XXX"}'
value_template: "{{ value_json.success }}"
scan_interval: 120
- platform: template
sensors:
aterm2f:
friendly_name: "Luftfeuchte vorm Haus"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[0]['measurement']['h'] }}"
unit_of_measurement: "%"
aterm2t:
friendly_name: "Temperatur vorm Haus"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[0]['measurement']['t1'] }}"
unit_of_measurement: "°C"
aterm2t2:
friendly_name: "Temperatur Teich"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[0]['measurement']['t2'] }}"
unit_of_measurement: "°C"
aterm1f:
friendly_name: "Luftfeuchte hinterm Haus"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[1]['measurement']['h'] }}"
unit_of_measurement: "%"
aterm1t:
friendly_name: "Temperatur hinterm Haus"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[1]['measurement']['t1'] }}"
unit_of_measurement: "°C"
aterm3r:
friendly_name: "Temperatur Dach"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[2]['measurement']['t1'] }}"
unit_of_measurement: "°C"
aterm3rm:
friendly_name: "Regenmenge Gesamt"
value_template: "{{ state_attr('sensor.aterm2' , 'devices')[2]['measurement']['r'] }}"
unit_of_measurement: "mm"
aterm4w:
friendly_name: "Windgeschwindigkeit"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[3]['measurement']['ws'] }}"
unit_of_measurement: "m/s"
aterm4wb:
friendly_name: "Boen"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[3]['measurement']['wg'] }}"
unit_of_measurement: "m/s"
aterm4wr:
friendly_name: "Windrichtung"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[3]['measurement']['wd'] }}"
unit_of_measurement: "Richtung"
aterm5ld:
friendly_name: "Luftdruck"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[4]['measurement']['ap'] }}"
unit_of_measurement: "hPa"
aterm5t:
friendly_name: "Temperatur Speicher"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[4]['measurement']['t1'] }}"
unit_of_measurement: "°C"
aterm5f:
friendly_name: "Luftfeuchte Speicher"
value_template: "{{ state_attr('sensor.aterm2', 'devices')[4]['measurement']['h'] }}"
unit_of_measurement: "%"
1 Like
As a workaround without the MA Cloud:
There is a stand-alone proxy for MA Gateways with pushed the data to an MQTT Server.
MMMMobileAlerts/maserver at master · sarnau/MMMMobileAlerts (github.com)
- : Works without the MobileAlerts TFA Servers
- : You need to run it on by your self on a linux instance.