All RFXMeters are gone after upgrade
Posted: Saturday 15 February 2025 19:25
After upgrading from Version 16344 to 16461 I read an error in the log:
No idea what to do about it...
After some search I found out it is related to MQTT-traffic from my EPS-devices. Which are running ESPeasy-software. These devices monitor my kWh-meters..
And when ik look better in the GUI-database I cannot find the RFXmeter devices!! So the virtual meters are gone!
This is an example of a device with RFXMeter as Type in build 16344
This is an example of a device with RFXMeter as Type in build 16461
I am running Domoticz in Docker container so I can easily revert from old to new and back to old as the database is outside of the virtual machine on the host. After reverting to the old build the devices are back. So database is not corrupt.
What has changed in the software? Is this a bug or is this type of device outdated? And what is the replacement for it? How do I solve this problem?
Thanks for your help or advise.
Code: Select all
2025-02-15 14:35:00.380 Error: Invalid Number sValue: '%' for device idx: '%'
2025-02-15 14:35:00.381 Error: Invalid Number sValue: '%' for device idx: '%'
2025-02-15 14:35:03.720 Error: Invalid Number sValue: '%' for device idx: '%'
2025-02-15 14:35:03.721 Error: Invalid Number sValue: '%' for device idx: '%'
2025-02-15 14:35:04.447 Error: Invalid Number sValue: '%' for device idx: '%'
2025-02-15 14:35:04.759 Error: Invalid Number sValue: '%' for device idx: '%'
2025-02-15 14:35:08.449 Error: Invalid Number sValue: '%' for device idx: '%'After some search I found out it is related to MQTT-traffic from my EPS-devices. Which are running ESPeasy-software. These devices monitor my kWh-meters..
And when ik look better in the GUI-database I cannot find the RFXmeter devices!! So the virtual meters are gone!
This is an example of a device with RFXMeter as Type in build 16344
This is an example of a device with RFXMeter as Type in build 16461
I am running Domoticz in Docker container so I can easily revert from old to new and back to old as the database is outside of the virtual machine on the host. After reverting to the old build the devices are back. So database is not corrupt.
What has changed in the software? Is this a bug or is this type of device outdated? And what is the replacement for it? How do I solve this problem?
Thanks for your help or advise.