-
Notifications
You must be signed in to change notification settings - Fork 26
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
Suddenly Stopped Working #15
Comments
Was this ever resolved? This just happened to me, I was working on an unrelated project and it just stopped working. OSError: No communication with the instrument (no answer) |
Hi folks - I've not encountered this one before. The Raspberry Pi I had installed in my "original" solar shed trailer just expired -- so I might try to do a "fresh setup" to a) document it and b) see if I encounter anything like this one. If I find anything helpful, I'll report back |
I am all but certain that this is not an issue with Solar Shed. That being said, I had a perfectly working system running on a Raspberry Pi, everything was being stored in Prometheus, charted with Grafana. Then today, I reconnected my Renogy Bluetooth module just to see what the Renogy DC Home app could offer, just out of curiosity. Since I've done that, when I reconnect the Raspberry Pi Solar Shed server (and more specifically the MinimalModbus) library is reporting errors to the effect of:
Nov 03 13:22:19 raspberrypi python[445]: File "/home/pi/.local/lib/python2.7/site-packages/minimalmodbus.py", line 930, in _communicate
Nov 03 13:22:19 raspberrypi python[445]: raise IOError('No communication with the instrument (no answer)')
Nov 03 13:22:19 raspberrypi python[445]: IOError: No communication with the instrument (no answer)
The software version on the charge controller is reporting device version V3.0.1 (I'm seeing this through the Renogy BT app on my phone). I'm starting to think that running the Renogy DC Home app might have updated the firmware on the device so that it somehow blocks requests over the serial port from unknown sources. Also just curious what the software version on your charge controller indicates?
The text was updated successfully, but these errors were encountered: