Skip to content

Unable to start SDRMR addon successfully #20

@N3rdP1um23

Description

@N3rdP1um23

Describe the bug
Have tried to follow the instructions as best as possible and have attempted to use different ID's for the water/gas/electric components, though I'm unable to get it working. It also seems that it starts, doesn't find any devices, then crashes as it's unable to connect to the spectrum server.

To Reproduce
Steps to reproduce the behavior:

  1. Install the addon following the steps in the readme
  2. Configure the addon
  3. Start the addon
  4. View addon logs

Expected behavior
Start the addon, find the sensors, log the data in Home Assistant.

Screenshots
N/A

Desktop

  • Home Assistant is running on Home Assistant OS
    • Home Assistant 2022.12.7
    • Supervisor 2022.11.2
    • Operating System 9.4

Additional context

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Starting RTLAMR with parameters:
AMR Message Type = all
AMR Device IDs =
Time Between Readings = 30
Duration =  15
Electric Unit of measurement =  kWh
Gas Unit of measurement =  m³
Water Unit of measurement =  l
Water measurements provided in tenths =  true
SCM PLUS GAS DIVISOR =  1
Debug is  true
No supported devices found.
13:52:54.704732 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/rtlamr@v0.9.3/main.go:90
main.main
	/go/pkg/mod/github.com/bemasher/rtlamr@v0.9.3/main.go:313
runtime.main
	/usr/lib/go/src/runtime/proc.go:250
runtime.goexit
	/usr/lib/go/src/runtime/asm_amd64.s:1571
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Is there possibly a way to continually listen to scans and view the data to determine which ids are the correct ones? Or even if it's setup/working to pickup data?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions