New release available!!!

[allangood]

After a long time without working on this project, I am back and with a new release!
Please, refer to #193 for more information

[miniminne]

Not sure if its my computer, or a bug but when trying to run the addon I get this error:

[2025-05-30 00:34:37,570] INFO:Publishing to rtlamr/status: online [2025-05-30 00:34:37,630] DEBUG:Reseting USB device: 001:004 Traceback (most recent call last): File "/opt/venv/app/rtlamr2mqtt.py", line 394, in <module> main() ~~~~^^ File "/opt/venv/app/rtlamr2mqtt.py", line 300, in main rtltcp = start_rtltcp(config) File "/opt/venv/app/rtlamr2mqtt.py", line 121, in start_rtltcp usbutil.reset_usb_device(usb_id) ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^ File "/opt/venv/app/helpers/usb_utils.py", line 45, in reset_usb_device filename = f"/dev/bus/usb/{busnum:03d}/{devnum:03d}" ^^^^^^^^^^^^ ValueError: Unknown format code 'd' for object of type 'str'

[allangood]

Your configuration has the usb_device set for something other than 0, right?

[GaussianWaffles]

I just installed the 2025.6.1 dev build to test out and am also seeing the same error. Release version 2.3.4 is working on the same hardware. I don't know enough to dig into the python code, but let me know if there's anything I can test out.

[2025-05-30 07:11:18,283] INFO:Publishing to rtlamr/status: online
[2025-05-30 07:11:18,366] DEBUG:Reseting USB device: 001:002
Traceback (most recent call last):
  File "/opt/venv/app/rtlamr2mqtt.py", line 394, in <module>
    main()
    ~~~~^^
  File "/opt/venv/app/rtlamr2mqtt.py", line 300, in main
    rtltcp = start_rtltcp(config)
  File "/opt/venv/app/rtlamr2mqtt.py", line 121, in start_rtltcp
    usbutil.reset_usb_device(usb_id)
    ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
  File "/opt/venv/app/helpers/usb_utils.py", line 45, in reset_usb_device
    filename = f"/dev/bus/usb/{busnum:03d}/{devnum:03d}"
                              ^^^^^^^^^^^^
ValueError: Unknown format code 'd' for object of type 'str'

[allangood]

Thank you for the feedback!
I know exactly were the problem is. I will send a fix i a few hours.

[allangood]

Just merged #267 and this shouldn't be a problem anymore!

[talormanda]

I see on the main page it says "This new version does not have the LISTEN MODE!!!"

Can you remind me what listen mode did? I want to test this, but I just want a refresher on what this did before I upgrade and lose it.

[sharoon65]

IIRC, listen mode could listen in on all the meters and would display all of it in the logs, and that way you could try to figure out which one was your meter and get its meter id.

[talormanda]

IIRC, listen mode could listen in on all the meters and would display all of it in the logs, and that way you could try to figure out which one was your meter and get its meter id.

So why bother updating if we can no longer listen to figure out what devices are out there? That's silly.

[sharoon65]

The new release had too many issues for me (I use it as a HAOS addon) and I went back to the previous version. If it's not broken , dont mess with it, I guess. I also didnt find any benefit that would make me want to upgrade

[finishthepint]

Just curious, how come the previous version didn't require mqtt user name and password but the new one does?

[willymena]

Hmm... 2.3.4 required me to use username and password. This latest version changed slightly. Now I need to use "user" instead of "username"

[finishthepint]

I went back to the old version since the new release isn't working for me and can confirm it indeed works without any mqtt credentials. Here's my mqtt config:
ha_autodiscovery: true
ha_autodiscovery_topic: homeassistant
base_topic: rtlamr
tls_enabled: false

And in the logs, there's this interesting piece:
[2025-06-04 12:55:53] Fetching default MQTT configuration from http://supervisor/services/mqtt
[2025-06-04 12:55:53] Configured MQTT sender:
[2025-06-04 12:55:53] > hostname => core-mosquitto
[2025-06-04 12:55:53] > port => 1883
[2025-06-04 12:55:53] > username => addons
[2025-06-04 12:55:53] > client_id => rtlamr2mqtt
[2025-06-04 12:55:53] > base_topic => rtlamr
[2025-06-04 12:55:53] > availability_topic => rtlamr/status
[2025-06-04 12:55:53] > tls => None

[allangood]

The previous version uses the Supervisor API to get those values.

[willymena]

Agree. I was using credentials in the previous version. I did have to back-rev for now and noticed that It would work without it... so you're right.

[allangood]

I finally found and fixed the problem.

A new release is available.

The new release also was shipped with the "transparent mqtt configuration". No mqtt user/password is needed.

Cheers

[allangood]

Finally we have a working release! Thanks to @nrdufour

Sorry for the troubles!

[talormanda]

Finally we have a working release! Thanks to @nrdufour

Sorry for the troubles!

Still no listen mode right?

[allangood]

No, not for now.

But you can run the command inside the container