Wifi socket disconnecting [solved]


I’ve got my spark2 working fine with the hyperios based docker and over USB. Using that, I’ve upgraded my firmware, restarted the spark and flicked the config across to using wifi. However, when I restart the docker without any device statement and a local config.cfg, I get connected apparently, but then get a socket disconnected error shown below which I’d be grateful for any thoughts on. The device itself is in maintenance mode showing the right IP address and a sensor value for temperature.

Aug 15 2017 15:51:58 Notification: Script started for beer 'My First BrewPi Run’
Aug 15 2017 15:51:58 Connecting to controller…
Aug 15 2017 15:51:58 Opening serial port
Aug 15 2017 15:51:58 Checking software version on controller…
Aug 15 2017 15:51:58 Found BrewPi v0.5.2 build 0.5.2-0-g72e633171, running on a Particle Photon with a V2 shield on port socket://

Aug 15 2017 15:51:58 Serial Error: socket disconnected)
Exception in thread Thread-1:
Traceback (most recent call last):
File “/usr/lib/python2.7/threading.py”, line 810, in __bootstrap_inner
File “/usr/lib/python2.7/threading.py”, line 763, in run
self.__target(*self.__args, **self.__kwargs)
File “/home/brewpi/backgroundserial.py”, line 110, in __listen_thread
if self.writeln("") > 0:
File “/home/brewpi/backgroundserial.py”, line 56, in writeln
return self.write(data + “\n”)
File “/home/brewpi/backgroundserial.py”, line 59, in write
File “/home/brewpi/backgroundserial.py”, line 75, in exit_on_fatal_error
File “/home/brewpi/backgroundserial.py”, line 38, in stop
self.thread.join() # wait for background thread to terminate
File “/usr/lib/python2.7/threading.py”, line 940, in join
raise RuntimeError(“cannot join current thread”)
RuntimeError: cannot join current thread

Aug 15 2017 15:51:59 Lost serial connection. Cannot write to serial
Terminating due to fatal serial error


Replying to my own problem is probably not the done thing, but while walking the dog I realise I had left another docker instance running on another test box pointing to the same device. Hurumpf. Once I had stopped that running, all was well. I guess a different error message to the above would be handy, but I’m happy it all works ::slight_smile: