Gotcha, when I say "watering" I mean that you pressed the button to open the valve. As far as the device would know it's "watering." I fixed that bug if you grab the new version of the app.
What's happening is your hub thinks it is connected to the socket when it isn't. I truly don't see what I'm doing wrong and losing my mind a bit so I asked someone else to take a look at the code and maybe see something I'm messing up. I'm confident it can be fixed, just not sure exactly how yet. I did add a "fail safe" where after 30 mins it will ALWAYS reconnect in case it got into this state, but that shouldn't be necessary.
I'm 99% sure there is a thread race condition, I'm not not entirely sure how to handle it given the methods HE gives me...
