plusplus-ua / ha_mobilealerts Goto Github PK

Noticed something interesting when we had a power blackout in our area for about 30 minutes: When the HA server came back online the Wind Sensor (identified as MA10660) recorded pretty high spikes for the wind values while in reality there was no change in weather during that time.

The official app does not show a spike like that, so there must be some difference in the way this integration and the MA servers interpret the received data? Does the integration ”deposit” the change in data, what I guess is a number of sensor revolutions, for the single moment of time when the latest value is received, instead of dividing it by the amount of time since the last value received?

For what it’s worth, my HA server is behind an UPS while the gateway is not, so in my case HA remained powered for some 15 min longer than the gateway did. Maybe this progression of time in HA might affect how derivatives like speeds are calculated?

Hi,
after Update to HA Core 2024.1.0 no more mobile alerts enties are available.
I´m running HA OS 11.2 in a Virual Machine on a Synology DS920+

I´m using TFA30.3060.01 & MA10120.

Maybe anyone could help to solve the issue?

Many Thanks

hi,
i am very new with HA, how do i need to install this?
kind regards

Hello,

I can't connect to my mobile Alerts. It is in a other Netwok (the Gateway) and this is connected via VPN to my Home. And HA is in my Home network.

Is there a way to get the Mobile Alerts integration to work anyway?

When setting up the integration, only the error message appears:
Mobile-Alerts
No devices found on the network

Great integration !! Has worked on the spot.
A little fine-tuning kindly requested for MA 10251 (or MA 10250), though.
Humidity is 10-bit (not 9-bit). So instead of 98.7 % we get 47.5% (98.7-47.5=51.2)
This difference is always 51.2 (or 512 in integer representation).
Other Humidity sensors I have (e.g. MA 10200) are XY.0 precision, so 8-bit precision is enough to cover 0=100% range.
This sensor MA 10251 entity is represented by name:
sensor.professional_thermo_hygro_sensor_0e44a09a67f9_humidity
A sensor MA 10200 is represented by:
sensor.temperature_humidity_03009426e837_humidity
Any ideas ?

Would it be possible to add support for the AC Power Sensor? It monitors the electricity supply (on/off) and the current temperature.

You can see some information about it here:
https://www.batterylogic.co.uk/technoline-mobile-alerts-ma10870-ac-mains-sensor.asp

I'm happy to provide the first few digits of the ID if required.

the wind sensor (MA10660) is detected but the information stay at 0 ( Gust 0,0 m/s Time span 352 s Wind direction 0,0 ° Wind speed 0,0 m/s).
https://www.lacrossetechnology.fr/P-25-A1-MA10660.html

I have an MA10320 sensor which is being detected as MA10120, so it thinks the External Temperature Probe is at 71C while the Humidity is Unknown. In fact it is the other way around, the Humidity is 71% but the external temperature is unknown as the probe is not connected.

Sensor Type MA10120 is only temperature, so if Humidity is present it must be MA10320 type sensor.

Hi,
Great integration when I finally got it working. Complete HA noob myself so I was struggling to get it work as I am using HA docker. I had to create macvlan network to be able to turn network discovery on ( I guess) and after that all external sensors was starting to get data. But the sensor on main display is not getting any readings. Could that be implemented in your integration? Don't know whether that panel has separate product code but acc. to @sarnau device list it is this TFA30.3060.01.

Slava Ukraini!

First thanks very much for the integration, saved me loads of time trying to work it out myself.

My sensors all work but I get some very strange default names for the sensors discovered on my MA10430 device e.g.

Temperature/Humidity/Pool sensor (061C7479505D) Humidity
Temperature/Humidity/Pool sensor (061C7479505D) Pool temperature
Temperature/Humidity/Pool sensor (061C7479505D) Battery
Temperature/Humidity/Pool sensor (061C7479505D) Temperature

I presume the names somehow come from TechoLine but they really don't make much sense! The Technoline app correctly identifies them as Humidity, Temperature, Probe Temperature. It may be that the app just renames the above?

Is there anyway of renaming these to something more sensible?

Just a small thing I noticed about the "Proxy" and "Proxy is used" entities: They seem to be showing wrong information when compared to the information my Gateway is showing in its webui. Proxy is indeed in use (.11.202) but the entities in HA show that it is not and the IP is wrong (.1.1). Everything about the proxy still works just fine, it's just the information that is incorrect.

Gateway UI:

HA proxy info:

My MobileAlerts integration started suddenly flooding my log with this error, after upgrading to Home Assistant 2023.5.3 (Supervisor 2023.04.1 - Operating System 10.1). All entities under this integration do not seem to be updating anymore.

These are logged right after system reboot:

Logger: homeassistant.components.sensor
Source: custom_components/mobile_alerts/binary_sensor.py:171 
Integration: Sensori (documentation, issues) 
First occurred: 22.02.39 (2 occurrences) 
Last logged: 22.02.39

Error adding entities for domain sensor with platform mobile_alerts
Error while setting up mobile_alerts platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 455, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 731, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 844, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/config/custom_components/mobile_alerts/base.py", line 193, in async_added_to_hass
    self._handle_coordinator_update()
  File "/config/custom_components/mobile_alerts/base.py", line 220, in _handle_coordinator_update
    entity.update_data_from_sensor()
  File "/config/custom_components/mobile_alerts/binary_sensor.py", line 171, in update_data_from_sensor
    (int(time_span_sensor._attr_native_value) == 0) and
ValueError: invalid literal for int() with base 10: 'unavailable'




Logger: aiohttp.server
Source: custom_components/mobile_alerts/binary_sensor.py:171 
Integration: Mobile-Alerts 
First occurred: 22.03.04 (1 occurrences) 
Last logged: 22.03.04

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/mobilealerts/proxy.py", line 87, in request_handler
    await gateway.handle_update(
  File "/usr/local/lib/python3.10/site-packages/mobilealerts/gateway.py", line 526, in handle_update
    await self.handle_sensors_update(packages)
  File "/usr/local/lib/python3.10/site-packages/mobilealerts/gateway.py", line 510, in handle_sensors_update
    await self.handle_sensor_update(
  File "/usr/local/lib/python3.10/site-packages/mobilealerts/gateway.py", line 496, in handle_sensor_update
    await self._handler.sensor_updated(sensor)
  File "/config/custom_components/mobile_alerts/coordinator.py", line 52, in sensor_updated
    self.async_set_updated_data({})
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 376, in async_set_updated_data
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 146, in async_update_listeners
    update_callback()
  File "/config/custom_components/mobile_alerts/base.py", line 204, in _handle_coordinator_update
    self.update_data_from_sensor()
  File "/config/custom_components/mobile_alerts/binary_sensor.py", line 171, in update_data_from_sensor
    (int(time_span_sensor._attr_native_value) == 0) and
ValueError: invalid literal for int() with base 10: 'unavailable'

Maybe i'm to stupid, to get this configured well, but i get this error and no data is sent to the Mobile-Alerts-Cloud:

Logger: mobilealerts.gateway
Source: runner.py:188
First occurred: 10:44:26 (25 occurrences)
Last logged: 11:02:59

Error resending request to cloud: ClientProxyConnectionError(ConnectionKey(host='192.168.31.70', port=8085, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.31.70', 8085)"))

Any suggestions to get this great integration fully working?

After updating Home Assistant to 2022.12.1 data is no longer sent to the cloud.

The logs say:

Error resending request to cloud: <InvalidURL /gateway/put>

Sensor is not recognised / Unknown device
(AC Voltage on or off and Temp sensor combo)

When the pop() runs from the code below:

sensor.py:
        for measurement_time in self._measurements.keys():
            if measurement_time < (now - self._period):
                _LOGGER.debug(
                    "period_rain update_data_from_sensor removed (%s: %s)",
                    datetime.fromtimestamp(measurement_time).isoformat(),
                    self._measurements[measurement_time]
                )
                self._measurements.pop(measurement_time)
            else:
                total += self._measurements[measurement_time]

you get the exception:
RuntimeError: dictionary changed size during iteration

A possible fix is:
for measurement_time in list(self._measurements.keys()):

Related to the issue #8 we need a way to specify the ip manually if the autodiscover fails.

The rain sensor is not detected.
I'm not totally sure, but it seems to be this one : https://www.lacrossetechnology.fr/P-20-A1-WSTX58IT.html

Just noticed while browsing some of my weather data that the entities created by this integration may not be supporting long-term statistics, as the data stops at my recorder's purge_keep_days -setting of 60 days. Many other entities do have long-term statistics, like for example the forecasted temperature in my case:

Is there any way to force statistics creation for the MobileAlerts' entities, or does something need to be changed in the integration itself to gain support for statistics?

My guess is that the state_class: measurement might be the key here? The template sensor I have for recording the current forecast has this:

template:
  - sensor:
      # Collecting weather forecast:
      - name: forecast_temperature
        state: "{{ state_attr('weather.forecast_myplace','temperature') }}"
        unit_of_measurement: "°C"
        state_class: measurement

First of all, thanks for your work! I was looking for that integration for a long time.

There seems to be an issue with the rain sensor. There are two entries for "last hour rain" but there is no one for "last day rain". I didn't have the chance to check the values - could be a naming issue and the second "last hour rain" has the data for "last day rain".