search

cpyarger / Home-Assistant-Addons

A hass.io addon for a software defined radio tuned to listen for Utility Meter RF transmissions and republish the data via Home Assistant's API
MIT License
9 stars 4 forks source link

Only first ID number is identified, and incorrectly given the gas units #31

Open Siress opened 11 months ago

Siress commented 11 months ago

Describe the bug Only the first ID is identified, and it's incorrectly identified as gas type.

To Reproduce Steps to reproduce the behavior:

  1. First time install
  2. Add three space-delineated 8-digit meter ID numbers in the "IDs" field.
  3. Input units m3 , kWh , gal
  4. Input multipliers: 0.01, 0.01, 748.1

Expected behavior Space-delineated IDs to each be used separately, and somehow identified as being either gas, electric, or water automatically. Each one to be configurable in the Energy Dashboard.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context If there are instructions regarding delineation of the IDs I have not found it... And if there's a specific order they should be given, that too is has not been communicated.

Siress commented 11 months ago

Found in the Log for this addon while trying to debug: "filterid=: display only messages matching an id in a comma-separated list of ids."

So it IS supposed to be CSV. That should be made clear through the Config GUI. I'm not sure it worked if there were spaces between the IDs and the commas.

Now that each meter is being read, a new issue arises: All three meters are being treated as a gas meter.

Per HA Settings > Devices... > Entities, these sensors do not have unique IDs. That seems like it could be due to the debug required for ID deliminator issue above. They also show as read-only. This means I cannot change the sensor settings.

And I just recognized another issue: This add-on is 150MB. That's a lot... that's 600% larger than the rest of my HA. This doesn't seem like a big deal except that it will consume that for every single backup - so that's another 1-2 GB of backed up data that really aren't needed.