wrybread

Very strange, this now happens on both my computers. Once it starts happening it doesn't go away apparently. A cookie maybe? Willing to perform troubleshooting if anyone has any tips....

Aha, looking through the source I found the "logout" option, which fixed the issue for me: instalooter logout Maybe that should be added to the usage page? http://instalooter.readthedocs.io/en/latest/usage.html

`os.environ["SDL_HINT_JOYSTICK_ALLOW_BACKGROUND_EVENTS"] = "1"` Thanks for that! And does it really require a numerical string, or is this more correct? `os.environ["SDL_HINT_JOYSTICK_ALLOW_BACKGROUND_EVENTS"] = True` And unfrotunately I won't be back at that...

One year later and I'm trying to do the same, server still down...

At the moment my controller won't respond to connection attempts again. It ran all night in a test script, responding for about 11.5 hours (4253 responses, one every 9.7 seconds)....

Ugh, after running smoothly for a week, the charge controller just stopped responding again, and now it won't respond. Am I the only one having this problem? Can someone confirm...

Just a quick note, I solved the issue. I needed to ground my Pi to the charge controller. I did that by connecting the ground pin from the modbus cable...

Could you post the code you're using? I'm using the same basic code as Matt (I think), which is: > from pymodbus.client.sync import ModbusSerialClient as ModbusClient > > client =...

Aha! I think I figured out what's causing the slowness. You need to add a timeout value to your client: client = ModbusClient(method = 'rtu', port = '/dev/ttyUSB0', baudrate =...

I had some flaky behavior before grounding the charge controller to my Pi, as described here: https://github.com/kasbert/epsolar-tracer/issues/14