General help

[allangood]

Please, use this thread for general support questions.

Thank you!

[markwoodward86]

Hi there!

I just updated to the latest 1.5.4 but lost my sensors in MQTT. The meters are still being read in rtlamr according to the logs and still being sent to MQTT but the entities show 'unavailable'. Tried uninstalling MQTT and resetting everything up but now entities show up at all (with both auto discovery and manually).

Any ideas?

log output in attachment
rtlamr error.log

[allangood]

it is a bug introduced by the device_class feature. I am working on it to fix ASAP.
Thank you for reporting.

[allangood]

I just pushed #70 and the correction will be available shortly

[markwoodward86]

Thank you very much for your quick turnaround on this! Installed and working.

Much appreciated.

[allangood]

Thank you for reporting the problem!
I am still working in a better way to test everything before going to production.

[eCyclops]

I have set up using the addon and it seems to work correctly.

meters:
  - id: <obfuscated>
    protocol: scm
    name: house_electric_meter
    format: "#####.##"
    unit_of_measurement: kWh
    icon: mdi:gauge
    device_class: energy
    state_class: total_increasing
    native_unit_of_measurement: kWh
    native_value: decimal.Decimal

However, although I can see the correct meter reading as "state" of my meter ID using MQTT Explorer, I can't seem to get Home Assistant to notice it.

I believe the meter config is working to some degree, as I was able to change the state (from the "Consumption" field in the scm) format from three digits to the right of the decimal to two.

I don't see any errors, just nothing showing up in Energy. The energy dashboard suggests this page: https://www.home-assistant.io/more-info/statistics/

[eCyclops]

Then again, it might have something to do with : After setting up a new device, it can take up to 2 hours for new data to arrive in your energy dashboard. (from the Energy dashboard).

[eCyclops]

Well, after running for a week, it's still running, but there doesn't seem to be anything popping up in the Energy dashboard. Is this because there's no sensor? Rank beginner at HA here.

[eCyclops]

Okay, I dug into the instructions a bit more. I'm not sure I have all the yaml in the right places, but I do have a sensor now. I'll see if I start to get statistics and so on.

[eCyclops]

I believe I have the answer to my problems. Although I installed the addon, and have auto-discovery enabled, I needed to define the utility_meter in my main configuration.yaml (I understand that I could have put it in a separate one and loaded that). I also had to define the sensor in the configuration.yaml.

Once I had done both of those things, it works like a champ. My next adventure will be to add the power meter for my outbuildings, but I suspect that will go smoothly now.

Thanks so much for packaging this as an addon. I was having a lot of trouble manually adding it to HA using the half-dozen how-tos out there on the Internet.

[dwwkelly]

I have the SDR component set up and working OK but when the SDR detects a packet and tries to send to MQTT I get this error:

[2022-11-10 23:11:26] Sending message to MQTT:
[2022-11-10 23:11:26]  > topic => rtlamr/1808657/attributes
[2022-11-10 23:11:26]  > payload => {"Message Type": "SCM", "ID": 1808657, "Type": 12, "TamperPhy": 3, "TamperEnc": 0, "Consumption": 159378, "ChecksumVal": 5679}
[2022-11-10 23:11:26]  > retain => True
[2022-11-10 23:11:26] Unknown exception connecting to MQTT broker: [Errno 111] Connection refused
[2022-11-10 23:11:26] Sending message to MQTT:
[2022-11-10 23:11:26]  > topic => rtlamr/1808657/state
[2022-11-10 23:11:26]  > payload => 0159.378
[2022-11-10 23:11:26]  > retain => True
[2022-11-10 23:11:26] Unknown exception connecting to MQTT broker: [Errno 111] Connection refused
[2022-11-10 23:11:26] Sleep_for defined, time to sleep!
[2022-11-10 23:11:26] Terminating all subprocess...
[2022-11-10 23:11:26] Kill process called.
[2022-11-10 23:11:26] Killing RTL_TCP...
[2022-11-10 23:11:31] Killed.
[2022-11-10 23:11:31] Killing RTLAMR...
[2022-11-10 23:11:31] Killed in the first attempt.
[2022-11-10 23:11:31] Sleeping for 60 seconds, see you later...```

I can access mosquitto from outside my RPi that HA is running on using mosquitto_pub and mosquitto_sub.  I have a username and PW setup which are both in my config file.  Looking at the code it doesn't seem like it's doing anything odd when reading the username and PW.  I can also publish and subscribe using the MQTT integration.

Any ideas?

[allangood]

Without more info, no. But the error is very clear Connection refused
Double check your MQTT host, username and password.

[JAudi23]

Hi All,

Hoping someone can help me with the initial setup. I've installed rtlamr2mqtt on a RPi i have here for various tools and utilities, and it has my SDR receiver plugged in. I'm not clear on what I need to do to confirm that it's working on my RPi before I even attempt to send the data over to my HA Yellow where the MQTT is running.

On my RPi, for some reason this path is a folder, not a YAML file like I assumed it should be.

/opt/rtlamr2mqtt/rtlamr2mqtt.yaml

Error opening file /opt/rtlamr2mqtt/rtlamr2mqtt.yaml: is a directory

Is this rtlamr2mqtt.yaml file simply a copy of the file in this repositories folder here > "rtlamr2mqtt-addon/app/rtlamr2mqtt.yaml"

My HA Yellow already has a separate SDR receiver plugged in where I am running rtl_433 for my weather station and other stuff. HA add-on for thsi, it stops my rtl_433 add-op from running, hence me running it from my RPi instead.

If anyone can provide some pointers to get me started I'd appreciate it.