Home Assistant - Error

julesb · 2020-07-19T17:30:51.858Z

I am trying to get the Emoncms integration working with Home Assistant. Having been through the process of updating to the emonSD-17Oct19 image (which went flawlessly), I still can’t get Home Assistant to recognise Emoncms.

I have been through the logs and found the following, which seems to be the root of the problem. Does anyone know what this means? I am using the basic setup in configuration.yml (Read API Key, Emonpi ip address and id: 1) accessing my local emonpi.

File "/usr/src/homeassistant/homeassistant/components/emoncms/sensor.py", line 160, in __init__
self._state = round(float(elem["value"]), DECIMALS)
TypeError: float() argument must be a string or a number, not 'NoneType'

borpin · 2020-07-20T07:40:29.314Z

Interesting.

Can you post your yaml configuration please.

[edit]
Are any of the feed values in your feed list ‘Null’?

Source code core/sensor.py at dev · home-assistant/core · GitHub

@bwduncan, as the resident Python expert , could you suggest what might be needed as a check to avoid this error?

borpin · 2020-07-20T07:53:55.521Z

Could you also post the result of

http://<your IP>/feed/list.json

julesb · 2020-07-20T14:52:21.827Z

I went through my feeds and found two NULL feeds, which I deleted. I had also not spotted that one of my EmonTHs had a flat battery so this might also have been producing NULLs, but I can’t remember now!

Having re-started Home Assistant, the feeds from EmonCMS are now discovered, so I can start playing with them now.

Thanks!

borpin · 2020-07-20T15:24:11.425Z

No bother, worth knowing and getting fixed.

I have raised an Issue

github.com/home-assistant/core

Emoncms Integration - Null value causes error

opened 03:37PM - 20 Jul 20 UTC

borpin

integration: emoncms by-code-owner

## The problem  A user reported seeing this error on the [OEM Forum](https://community.openenergymonitor.org/t/home-assistant-error/14839?u=borpin). On checking they discovered that one of the Feeds had a Null value. When removed the error stopped. Tested myself to confirm. The code should check for a valid value before converting. ## Environment  - Home Assistant Core release with the issue: 0.112.4 - Last working Home Assistant Core release (if known): - Operating environment (OS/Container/Supervised/Core): Supervised - Integration causing this issue: Emoncms - Link to integration documentation on our website: https://www.home-assistant.io/integrations/emoncms/ ## Problem-relevant `configuration.yaml`  ```yaml sensor: platform: emoncms api_key: API_KEY url: 192.168.1.10 id: 1 ``` ## Traceback/Error logs  ```txt File "/usr/src/homeassistant/homeassistant/components/emoncms/sensor.py", line 160, in __init__ self._state = round(float(elem["value"]), DECIMALS) TypeError: float() argument must be a string or a number, not 'NoneType' ``` ## Additional information https://github.com/home-assistant/core/blob/6ea5c8aed9f113bc1ec58e449491e10112012e85/homeassistant/components/emoncms/sensor.py#L159-L160 A check is needed to ensure the `elem["value"]` is valid and set sensor as unavailable if not. My Python is not good enough to know what should be done to avoid this error being generated.

bwduncan · 2020-07-20T23:59:31.678Z

borpin:

@bwduncan, as the resident Python expert , could you suggest what might be needed as a check to avoid this error?

Sorry, I don’t know what mechanism HA uses to mark a sensor as unavailable, but checking for ValueError and TypeError would probably be the most appropriate exceptions to catch.