New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emoncms Integration - Null value causes error #38016
Comments
emoncms documentation |
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. |
Could I get a small amount of help with this please? |
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. |
I still need some help to fix this error please. Just needs a check added that the value exists/is valid. |
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. |
I still need some help to fix this error please. Just needs a check added that the value exists/is valid. |
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. |
This is still a problem so should not be closed. |
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. |
bump. help needed |
Agreed. This issue was a headache to solve. If one feed reports 'null' every other sensor stops updating. |
Fixed by #76074 |
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
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
core/homeassistant/components/emoncms/sensor.py
Lines 159 to 160 in 6ea5c8a
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.
The text was updated successfully, but these errors were encountered: