jdeath / rtlamr2mqqt Goto Github PK

View Code? Open in Web Editor NEW

36.0 36.0 8.0 46 KB

License: MIT License

Dockerfile 51.54% Shell 48.46%

rtlamr2mqqt's People

Contributors

Stargazers

Watchers

Forkers

fcfort kyle2222 mccroden anthonypluth aguedob pringlechip par-texx sacofpotatoes

rtlamr2mqqt's Issues

Error on start - s6-overlay-suexec: fatal: can only run as pid 1

Hi,

Thanks again for the great add-on that worked flawlessly. I was able to receive my gas and water meter readings. Unfortunately, I recently upgrade my home assistant instance. Now I receive a "s6-overlay-suexec: fatal: can only run as pid 1" error In the logs and the add-on won't start.

I have removed and reinstalled, unplugged and plugged back in the dongle, restarted HA and I still encountered the Issue. Do you have any thoughts?

Home Assistant Core 2022.5.5
Home Assistant Supervisor 2022.05.3
Home Assistant OS 8.1
Kernel version 5.15.41
Agent version 1.2.1

i/o timeout

Sorry, another question as I am trying to learn the ins and outs of this: The add-on will be running great for hours or days but sometimes it will randomly show this in the logs:

read tcp 127.0.0.1:45698->127.0.0.1:1234: i/o timeout
io.ReadFull

Any clue what this means? I have tried Googling around but nothing overly helpful in relation to SDRs. I'm on a Proxmox VM with HAOS with plenty of resources. Restarting the AddOn doesn't do anything, the error just comes back, but restarting the whole VM usually fixes it. Not sure if it's losing connection to the dongle maybe?

Make repo available for use from Home Assistant Add-Ons UI

While you can add this repo to the Home Assistant, you can't actually use the add-on because this repo isn't structured the way Home Assistant expects.

What do you think about adding a repository.json file to the root of this repo and moving the rest of the files into a sub-directory as per https://developers.home-assistant.io/docs/add-ons/repository?

Failed to install add-on error - returned a non-zero code: 1

Hi, your software was working great until I upgraded home assistant. I upgraded to latest version and when I attempt to install the add-on I receive the error below.
I would in be interested in your thoughts.

System Information
Home Assistant Core 2022.6.7
Home Assistant Supervisor 2022.05.3
Home Assistant OS 8.2

Error message attempting to install
"Failed to install add-on
The command '/bin/ash -o pipefail -c go get github.com/bemasher/rtlamr' returned a non-zero code: 1"

Feature Request

Thanks for the great addon!

I was wondering if it was possible to implement this library (https://github.com/merbanan/rtl_433) as the James Fry addon did. I had it working quite well with my efergy power monitor but that addon no longer plays nice with the Supervisor.

I'm happy to help out in anyway I can.

Cheers

Start-up issue after recent Home Assistant upgrade

Had been working great, recently upgraded Home Assistant -- now receiving errors, thanks

core-2021.2.2
supervisor-2021.02.6

Getting following errors in log, add-on crashes after startup.

WARNING (MainThread) [supervisor.addons.validate] Add-on config 'startup' with 'before' is deprecated. Please report this to the maintainer of RTLAMR to MQTT Bridge

WARNING (MainThread) [supervisor.addons.validate] Add-on config 'devices' use a deprecated format, the new format uses a list of paths only. Please report this to the maintainer of RTLAMR to MQTT Bridge

Following error for the add-on:

07:24:52.917561 main.go:85: Error connecting to spectrum server: dial tcp 127.0.0.1:1234: connect: connection refused
rcvr.Connect
main.(*Receiver).NewReceiver
/go/src/github.com/bemasher/rtlamr/main.go:85
main.main
/go/src/github.com/bemasher/rtlamr/main.go:325
runtime.main
/usr/lib/go/src/runtime/proc.go:204
runtime.goexit
/usr/lib/go/src/runtime/asm_amd64.s:1374

rtl_tcp dies, doesn't get restarted

My rtl_tcp has a bad habit of dying on a daily basis. It doesn't get restarted when this happens and rtlamr has nothing to connect to. Would it be possible to have an rtl_tcp watchdog?

08:11:45.658190 decode.go:59: Protocols: scm
08:11:45.658209 decode.go:60: Preambles: 111110010101001100000
08:11:45.658230 main.go:124: GainCount: 29
08:11:50.662190 main.go:343: Receiver context cancelled.
08:11:50.662793 main.go:320: read tcp 127.0.0.1:52638->127.0.0.1:1234: i/o timeout
io.ReadFull
main.(*Receiver).Run.func2
	/go/pkg/mod/github.com/bemasher/[email protected]/main.go:181
runtime.goexit
	/usr/lib/go/src/runtime/asm_amd64.s:1371
08:12:50.676234 decode.go:45: CenterFreq: 912600155
08:12:50.676603 decode.go:46: SampleRate: 2359296
08:12:50.676624 decode.go:47: DataRate: 32768
08:12:50.676636 decode.go:48: ChipLength: 72
08:12:50.676646 decode.go:49: PreambleSymbols: 21
08:12:50.676656 decode.go:50: PreambleLength: 3024
08:12:50.676667 decode.go:51: PacketSymbols: 96
08:12:50.676678 decode.go:52: PacketLength: 13824
08:12:50.676691 decode.go:59: Protocols: scm
08:12:50.676704 decode.go:60: Preambles: 111110010101001100000
08:12:50.676716 main.go:124: GainCount: 29
08:12:55.679475 main.go:343: Receiver context cancelled.
08:12:55.679904 main.go:320: read tcp 127.0.0.1:53012->127.0.0.1:1234: read: connection reset by peer
io.ReadFull
main.(*Receiver).Run.func2
	/go/pkg/mod/github.com/bemasher/[email protected]/main.go:181
runtime.goexit
	/usr/lib/go/src/runtime/asm_amd64.s:1371
08:13:55.692265 decode.go:45: CenterFreq: 912600155
08:13:55.692353 decode.go:46: SampleRate: 2359296
08:13:55.692359 decode.go:47: DataRate: 32768
08:13:55.692362 decode.go:48: ChipLength: 72
08:13:55.692364 decode.go:49: PreambleSymbols: 21
08:13:55.692374 decode.go:50: PreambleLength: 3024
08:13:55.692377 decode.go:51: PacketSymbols: 96
08:13:55.692380 decode.go:52: PacketLength: 13824
08:13:55.692384 decode.go:59: Protocols: scm
08:13:55.692387 decode.go:60: Preambles: 111110010101001100000
08:13:55.692390 main.go:124: GainCount: 29
08:14:00.696871 main.go:343: Receiver context cancelled.
08:14:00.697428 main.go:320: read tcp 127.0.0.1:53400->127.0.0.1:1234: i/o timeout
io.ReadFull
main.(*Receiver).Run.func2
	/go/pkg/mod/github.com/bemasher/[email protected]/main.go:181
runtime.goexit
	/usr/lib/go/src/runtime/asm_amd64.s:1371
08:15:00.708316 decode.go:45: CenterFreq: 912600155
08:15:00.708688 decode.go:46: SampleRate: 2359296
08:15:00.708714 decode.go:47: DataRate: 32768
08:15:00.708728 decode.go:48: ChipLength: 72
08:15:00.708740 decode.go:49: PreambleSymbols: 21
08:15:00.708753 decode.go:50: PreambleLength: 3024
08:15:00.708766 decode.go:51: PacketSymbols: 96
08:15:00.708779 decode.go:52: PacketLength: 13824
08:15:00.708797 decode.go:59: Protocols: scm
08:15:00.708814 decode.go:60: Preambles: 111110010101001100000
08:15:00.708830 main.go:124: GainCount: 29
08:15:05.710015 main.go:343: Receiver context cancelled.
08:15:05.710131 main.go:320: read tcp 127.0.0.1:53860->127.0.0.1:1234: i/o timeout
io.ReadFull
main.(*Receiver).Run.func2
	/go/pkg/mod/github.com/bemasher/[email protected]/main.go:181
runtime.goexit
	/usr/lib/go/src/runtime/asm_amd64.s:1371
08:16:05.718234 decode.go:45: CenterFreq: 912600155
08:16:05.718561 decode.go:46: SampleRate: 2359296
08:16:05.718586 decode.go:47: DataRate: 32768
08:16:05.718600 decode.go:48: ChipLength: 72
08:16:05.718614 decode.go:49: PreambleSymbols: 21
08:16:05.718628 decode.go:50: PreambleLength: 3024
08:16:05.718641 decode.go:51: PacketSymbols: 96
08:16:05.718656 decode.go:52: PacketLength: 13824
08:16:05.718675 decode.go:59: Protocols: scm
08:16:05.718694 decode.go:60: Preambles: 111110010101001100000
08:16:05.718711 main.go:124: GainCount: 29
08:16:10.723719 main.go:343: Receiver context cancelled.
08:16:10.724229 main.go:320: read tcp 127.0.0.1:54304->127.0.0.1:1234: i/o timeout
io.ReadFull
main.(*Receiver).Run.func2
	/go/pkg/mod/github.com/bemasher/[email protected]/main.go:181
runtime.goexit
	/usr/lib/go/src/runtime/asm_amd64.s:1371
08:17:10.729891 decode.go:45: CenterFreq: 912600155
08:17:10.729946 decode.go:46: SampleRate: 2359296
08:17:10.729949 decode.go:47: DataRate: 32768
08:17:10.729951 decode.go:48: ChipLength: 72
08:17:10.729953 decode.go:49: PreambleSymbols: 21
08:17:10.729954 decode.go:50: PreambleLength: 3024
08:17:10.729956 decode.go:51: PacketSymbols: 96
08:17:10.729957 decode.go:52: PacketLength: 13824
08:17:10.729960 decode.go:59: Protocols: scm
08:17:10.729962 decode.go:60: Preambles: 111110010101001100000
08:17:10.729964 main.go:124: GainCount: 29
08:17:15.733466 main.go:343: Receiver context cancelled.
08:17:15.733657 main.go:320: read tcp 127.0.0.1:54664->127.0.0.1:1234: i/o timeout
io.ReadFull
main.(*Receiver).Run.func2
	/go/pkg/mod/github.com/bemasher/[email protected]/main.go:181
runtime.goexit
	/usr/lib/go/src/runtime/asm_amd64.s:1371

Startup issue w/ Add-on

Hi -- I have a RTL-SDR Blog V3 R820T2 RTL2832U 1PPM TCXO HF Bias Tee SMA Software Defined Radio with Dipole Antenna Kit (Link)

Running Hassio 0.107.4 on an Intel NUC w/ Ubuntu. I have previously installed rtl_tcp using apt-get.. looks like it is detecting my device.

I installed your add-on, however I am getting the following error after it starts. Any thoughts much appreciated.

main.go:85: Error connecting to spectrum server: dial tcp 127.0.0.1:1234: connect: connection refused rcvr.Connect main.(*Receiver).NewReceiver /go/src/github.com/bemasher/rtlamr/main.go:85 main.main /go/src/github.com/bemasher/rtlamr/main.go:325 runtime.main /usr/lib/go/src/runtime/proc.go:203 runtime.goexit /usr/lib/go/src/runtime/asm_amd64.s:1357

High Values with Mosquito Broker Update

I think this might be an issue more with Mosquito Broker as whenever it updates all of my utility meter readings go sky high for one reading then go back to normal right after the update and the add-on starts. I wanted to check here if this happens to anyone else and is there a way to prevent this?

Compliments to the great addon

I absolutely love this addon, but I tend to have issues with MQTT not being stable for me.

So I went and forked and rebuilt the addon to use the Home Assistant API Directly

I would love if you could check it out and offer any suggestions you may have!

Regards,

Chris

scm+ gas meter not being stored in mqtt with proper id

I'm trying to get my gas meter readings into HA and I know that rtlamr can see them, as I've run it elsewhere to verify. 21892877 is my electric meter and 95229911 is my gas.

# rtlamr -msgtype=scm,scm+ -filterid=21892877,95229911
07:35:36.812021 decode.go:45: CenterFreq: 912600155
07:35:36.812126 decode.go:46: SampleRate: 2359296
07:35:36.812132 decode.go:47: DataRate: 32768
07:35:36.812136 decode.go:48: ChipLength: 72
07:35:36.812140 decode.go:49: PreambleSymbols: 21
07:35:36.812144 decode.go:50: PreambleLength: 3024
07:35:36.812147 decode.go:51: PacketSymbols: 128
07:35:36.812151 decode.go:52: PacketLength: 18432
07:35:36.812156 decode.go:59: Protocols: scm,scm+
07:35:36.812160 decode.go:60: Preambles: 0001011010100011,111110010101001100000
07:35:36.812164 main.go:126: GainCount: 29
{Time:2021-11-30T07:35:50.434 SCM:{ID:21892877 Type: 7 Tamper:{Phy:00 Enc:00} Consumption:  256606 CRC:0xD32D}}
{Time:2021-11-30T07:35:54.378 SCM+:{ProtocolID:0x1E EndpointType:0x9C EndpointID:  95229911 Consumption:    480066 Tamper:0x0808 PacketCRC:0xA74A}}
{Time:2021-11-30T07:36:09.379 SCM+:{ProtocolID:0x1E EndpointType:0x9C EndpointID:  95229911 Consumption:    480066 Tamper:0x0808 PacketCRC:0xA74A}}
{Time:2021-11-30T07:36:39.380 SCM+:{ProtocolID:0x1E EndpointType:0x9C EndpointID:  95229911 Consumption:    480066 Tamper:0x0808 PacketCRC:0xA74A}}
{Time:2021-11-30T07:36:55.379 SCM+:{ProtocolID:0x1E EndpointType:0x9C EndpointID:  95229911 Consumption:    480066 Tamper:0x0808 PacketCRC:0xA74A}}
{Time:2021-11-30T07:37:24.379 SCM+:{ProtocolID:0x1E EndpointType:0x9C EndpointID:  95229911 Consumption:    480066 Tamper:0x0808 PacketCRC:0xA74A}}
{Time:2021-11-30T07:37:53.382 SCM:{ID:21892877 Type: 7 Tamper:{Phy:00 Enc:00} Consumption:  256615 CRC:0x132A}}
{Time:2021-11-30T07:38:09.878 SCM+:{ProtocolID:0x1E EndpointType:0x9C EndpointID:  95229911 Consumption:    480066 Tamper:0x0808 PacketCRC:0xA74A}}
{Time:2021-11-30T07:38:39.378 SCM+:{ProtocolID:0x1E EndpointType:0x9C EndpointID:  95229911 Consumption:    480066 Tamper:0x0808 PacketCRC:0xA74A}}
{Time:2021-11-30T07:38:54.655 SCM:{ID:21892877 Type: 7 Tamper:{Phy:00 Enc:00} Consumption:  256633 CRC:0x1F4E}}

Here is the rtlamr2mqtt output:

MQTT Device IDs = 21892877,95229911
20:39:13.987567 decode.go:45: CenterFreq: 912600155
20:39:13.987650 decode.go:46: SampleRate: 2359296
20:39:13.987654 decode.go:47: DataRate: 32768
20:39:13.987656 decode.go:48: ChipLength: 72
20:39:13.987658 decode.go:49: PreambleSymbols: 21
20:39:13.987659 decode.go:50: PreambleLength: 3024
20:39:13.987661 decode.go:51: PacketSymbols: 128
20:39:13.987662 decode.go:52: PacketLength: 18432
20:39:13.987669 decode.go:59: Protocols: scm,scm+
20:39:13.987671 decode.go:60: Preambles: 111110010101001100000,0001011010100011
20:39:13.987673 main.go:124: GainCount: 29

Apparently, it is getting the gas meter, but it is putting it into MQTT as 'null':

Error connecting to spectrum server: dial tcp 127.0.0.1:1234: connect: connection refused with latest Home Assistant versions

After the latest updates of home assistant (as of 1/7/24 ~9am ET) I've started seeing the following error messages and I have not been receiving gas meter updates (they had been working fine for over a year before then.) Any idea what's going on here?

23:11:26.526880 main.go:90: Error connecting to spectrum server: dial tcp 127.0.0.1:1234: connect: connection refused
rcvr.Connect
main.(*Receiver).NewReceiver
/go/pkg/mod/github.com/bemasher/[email protected]/main.go:90
main.main
/go/pkg/mod/github.com/bemasher/[email protected]/main.go:313
runtime.main
/usr/lib/go/src/runtime/proc.go:250
runtime.goexit
/usr/lib/go/src/runtime/asm_amd64.s:1598

No MQTT Message Crossing

I had this setup and running smooth but woke up this morning to no updated data overnight. I have been checking everything but configuration is right; nothing was changed. I manually checked the SDR and I am receiving signals/messages; it just seems like they aren't crossing from the add-on to the MQTT broker. Looking at MQTT Fx, I am not seeing any message cross. Credentials in the add-on are correct, logs all look good. The only thing I see off is: "Socket error on client , disconnecting." in the Mosquitto Broker logs. I can't seem to figure it out and it's driving me crazy. Any insight?

Addon is unable to find the

Hi,

Thanks for making this available for all.

Not sure if it is a bug in the addon or my OS, but I am in the process of migrating to HassOS and tried your add-on. I am running the 64 bit version of HassOS. After installing the addon and placing the file in the proper location /config/rtlamr2mqtt/rtl2mqtt.sh with the added line for the 64 bit version, the program still cannot find the rtl2mqtt.sh file. Any ideas?

Here is the log info:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. /bin/ash: /rtl2mqtt.sh: not found [cmd] /bin/ash exited 127 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal.

Any help is appreciated.