-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
main.go:90: Error connecting to spectrum server: dial tcp 127.0.0.1:1234: connect: connection refused #141
Comments
if I restart the host computer, the system seems to time out after 8 min, not sure if this is a new issue or related. [2022-06-09 11:50:54] Using "/data/options.json" config file |
I think you are running with this same problem her: #98 Regards. |
Well, I've been having a similar issue for the last week. I don't have my radio on a powered hub, but it has been working fine for several month now at this point. The message that stood out to me is the "io.ReadFull". Is there a possibility that the new value can't overwrite the old one? My setup always works for the first scan after a restart, but then fails every time after that. I've tried it with the device ID set to "single" or by specifying the hardware ID:
...
Any suggestions? I don't mind getting a powered hub, but I'm surprised that it is only just now an issue. |
After reading a little more of the closed issues, it sounds like this is a powered USB hub issue. There are at least two other closed issues that refer to the io.ReadFull issue. Sorry for the trouble! |
This issue will be close now. |
my powered hub came in today, I am still getting the same issue. [2022-06-14 14:35:46] Using "/data/options.json" config file |
You seems to be running in listen_only mode, try to run in normal mode. |
I am in listen only mode, I don't know the ID of my meters, I can try normal mode just for troubleshooting though. |
I am also still getting the io read full error (listen only mode) [2022-06-14 15:06:06] Using "/data/options.json" config file |
Ok. I am reopening this issue and try to recreate the problem and troubleshoot. Thank you for your feedback! |
I think I've found the problem. RTL_TCP was left open/running after the "kill call". In the output (with problem) no RTL_TCP kill attempt:
This is the (with the fix) output:
|
Any time I have to restart or stop/start the home assistant add-on I get a connection refused error.
Default config other then listen mode set to true
restarting host computer will allow it to come back up
I think it is because there are two PIDs and restart only kills one of them.
[2022-06-09 11:41:25] Using "/data/options.json" config file
[2022-06-09 11:41:25] Fetching default MQTT configuration from http://supervisor/services/mqtt
[2022-06-09 11:41:25] Starting in LISTEN ONLY Mode...
[2022-06-09 11:41:25] Using "/data/options.json" config file
[2022-06-09 11:41:25] Fetching default MQTT configuration from http://supervisor/services/mqtt
[2022-06-09 11:41:25] Configured MQTT sender:
[2022-06-09 11:41:25] > hostname => core-mosquitto
[2022-06-09 11:41:25] > port => 1883
[2022-06-09 11:41:25] > username => addons
[2022-06-09 11:41:25] > client_id => rtlamr2mqtt
[2022-06-09 11:41:25] > base_topic => rtlamr
[2022-06-09 11:41:25] > availability_topic => rtlamr/status
[2022-06-09 11:41:25] > tls => None
[2022-06-09 11:41:25] Starting rtl_tcp with /usr/bin/rtl_tcp
[2022-06-09 11:41:27] Starting rtlamr with ['/usr/bin/rtlamr', '-msgtype=all', '-format=json']
[2022-06-09 11:41:27] You should see all utility meters after this line:
[2022-06-09 11:41:27] 11:41:27.829757 main.go:90: Error connecting to spectrum server: dial tcp 127.0.0.1:1234: connect: connection refused
[2022-06-09 11:41:27] rcvr.Connect
[2022-06-09 11:41:27] main.(*Receiver).NewReceiver
[2022-06-09 11:41:27] /go/pkg/mod/github.com/bemasher/rtlamr@v0.9.3/main.go:90
[2022-06-09 11:41:27] main.main
[2022-06-09 11:41:27] /go/pkg/mod/github.com/bemasher/rtlamr@v0.9.3/main.go:313
[2022-06-09 11:41:27] runtime.main
[2022-06-09 11:41:27] /usr/local/go/src/runtime/proc.go:250
[2022-06-09 11:41:27] runtime.goexit
[2022-06-09 11:41:27] /usr/local/go/src/runtime/asm_amd64.s:1571
The text was updated successfully, but these errors were encountered: