Emoncms Integration - Null value causes error

[borpin]

The problem

A user reported seeing this error on the OEM Forum.

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

sensor:
  platform: emoncms
  api_key: API_KEY
  url: 192.168.1.10
  id: 1

Traceback/Error logs

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

core/homeassistant/components/emoncms/sensor.py

Lines 159 to 160 in 6ea5c8a

	else:
	self._state = round(float(elem["value"]), DECIMALS)

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.

[probot-home-assistant]

emoncms documentation
emoncms source
_{^{(message by IssueLinks)}}

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[borpin]

Could I get a small amount of help with this please?

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[borpin]

I still need some help to fix this error please. Just needs a check added that the value exists/is valid.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[borpin]

I still need some help to fix this error please. Just needs a check added that the value exists/is valid.