Rest sensor ignores the availability line in the yaml

1mfaasj · July 25, 2024, 9:32am

Hi
I dont get it, the log is full of the following errors while I have defined an availability in the rest sensor?
what am I missing?

the rest sensor must try to pull data ONLY when the inverter is online. it looks like it’s now ignoring the availability line, so when the binary_sensor is not ON, the inverter is offline, so HA needs to skip the pulling…

2024-07-24 01:00:09.471 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:00:09.471 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:01:09.950 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:01:09.950 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:02:09.917 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:02:09.917 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:03:08.477 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:03:08.477 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:04:09.917 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:04:09.918 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:05:09.949 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:05:09.949 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:06:09.917 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:06:09.917 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:07:09.438 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:07:09.438 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:08:09.917 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:08:09.918 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:09:09.950 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:09:09.951 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:10:08.445 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:10:08.446 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:11:09.949 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:11:09.949 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data
2024-07-24 01:12:09.981 ERROR (MainThread) [homeassistant.components.rest.data] Error fetching data: http://192.168.2.35/ failed with All connection attempts failed
2024-07-24 01:12:09.981 WARNING (MainThread) [homeassistant.components.rest.util] Empty reply found when expecting JSON data

the yaml:

sensor:
- platform: rest
  scan_interval: 60
  resource: !secret solax_local_ip
  payload: !secret solax_local_realtime_payload
  method: POST
  headers: 
    X-Forwarded-For: 5.8.8.8
  name: "solax_rest_local"
  json_attributes:
    - SN
    - ver
    - type
    - Data
    - Information
  value_template: 'Active' 
  availability: >-
    {{ states('binary_sensor.192_168_2_35') == 'on' }}
  timeout: 30

Sir_Goodenough · July 25, 2024, 9:58am

Hi Bowa,

My first thought would be to put that into developer - templates and see if this is true or false, on or off, On or Off, whatever exactly. If that’s not changing from on as per your template it will not change the availability of the sensor.

Aster thst make sure the rest of the things are correct, url, passwords, etc are correct because the error (to me) seems like you are not getting connection to the api, not that availability is messing you up but I cannot tell exactly.

tom_l · July 25, 2024, 10:06am

It’s a binary sensor. The states will only be on or off.

I’d use this though:

{{ is_state('binary_sensor.192_168_2_35','on') }}

1mfaasj · July 25, 2024, 10:59am

@tom_l thanks let’s see if that changes anything. I will respond to this tomorrow because the inverter needs to go offline first. But your solution looks the same as mine?

@Sir_Goodenough the sensor works, the only thing is that HA tries to pull data when the inverter is offline (so during nights), and that’s not possible obviously. that’s why I was looking into the availability thing in the sensor.

koying · July 25, 2024, 11:01am

There is an open (ignored) issue regarding this

github.com/home-assistant/core

Rest sensor not updating (non-numeric value: 'None')

opened 04:21PM - 08 Sep 23 UTC

flo-wer

integration: rest

### The problem The rest sensor is still raising the `non-numeric value: 'Non…e' (<class 'str'>)` error despite using the `availability` config to filter any non-numeric values (see the `is_number` condition). I included example API responses for both cases. In the not available case, the `availability` condition evaluates to false and the value_template equals `null`/`None`. This produces the below exception. ### What version of Home Assistant Core has the issue? core-2023.9.0 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Core ### Integration causing the issue rest ### Link to integration documentation on our website https://www.home-assistant.io/integrations/sensor.rest/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml rest: - resource: http://192.168.1.110:3001/api/status-page/heartbeat/default scan_interval: 30 sensor: - unique_id: rest_uptime_ping1 name: uptime_ping1 value_template: '{% set v = value_json.heartbeatList["1"][-1] %}{{ v.ping }}' availability: '{% set v = value_json.heartbeatList["1"][-1] %}{{ v.status == 1 and is_number(v.ping) }}' unit_of_measurement: 'ms' state_class: measurement ``` ### Anything in the logs that might be useful for us? ```txt 2023-09-08 18:27:10.124 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/components/sensor/__init__.py", line 591, in state numerical_value = float(value) # type:ignore[arg-type] ^^^^^^^^^^^^ ValueError: could not convert string to float: 'None' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/update_coordinator.py", line 235, in _handle_refresh_interval await self._async_refresh(log_failures=True, scheduled=True) File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/update_coordinator.py", line 392, in _async_refresh self.async_update_listeners() File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/update_coordinator.py", line 173, in async_update_listeners update_callback() File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/components/rest/entity.py", line 51, in _handle_coordinator_update self._update_from_rest_data() File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/components/rest/sensor.py", line 180, in _update_from_rest_data self._process_manual_data(raw_value) File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/trigger_template_entity.py", line 242, in _process_manual_data self.async_write_ha_state() File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/entity.py", line 730, in async_write_ha_state self._async_write_ha_state() File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/entity.py", line 830, in _async_write_ha_state state, attr = self._async_generate_attributes() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/entity.py", line 771, in _async_generate_attributes state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/helpers/entity.py", line 736, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/components/sensor/__init__.py", line 593, in state raise ValueError( ValueError: Sensor sensor.uptime_ping1 has device class 'None', state class 'measurement' unit 'ms' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'None' (<class 'str'>) ``` ### Additional information REST API response available: ``` { "heartbeatList": { "1": [ { "status": 1, "ping": 21.4 } ] } } ``` not available: ``` { "heartbeatList": { "1": [ { "status": 0, "ping": null } ] } } ```

Sir_Goodenough · July 25, 2024, 2:10pm

My point is test the sensor you have on the IP address is that completely functioning. I would expect if the availability binary sensor were indeed changing to off, it should not be available and should not poll. You have the right idea, just see exactly what the binary sensor is giving you. You are looking fo on, and it seems that is there. Make sure it is flipping when you think it is. I didn’t know about the

issue, so if the availability is changing to none that might be a problem.
I have an availability template as a custom template in one of by blue message footer links you are welcome to use or learn from it it helps. \/ below \/

1mfaasj · July 26, 2024, 5:39am

The errors stays unfortunately.
I guess we need to wait until the github issue has been resolved…

Sir_Goodenough · July 28, 2024, 7:53pm

Or use my availavility-template which is OK with none… (Handles it correctly)