From the original screenshot, could you scroll down to the bottom where it should show master true and another value for websocketopen and take that screenshot?
I'm just getting started with this app and it looks like I'm also getting the web socket closing error. Any thoughts/suggestions?
Posting logs
Hub
Valve
Settings
Hub
Valve
I'll take a look in a little bit. As a note the websocket stuff isn't a "bug" so much as their websocket doesn't like us connecting 24/7. So when they disconnect, I just reconnect. I'm working on ways to make it a bit more stable, but remember, their app is really designed to be one you open and use for 2 minutes and then close. I'll take a closer look at your logs though, something is definitely not right there.
1 Like
Thanks!
FYI - If I open the valve via their app it updates HE, but HE has no control over the valve.
Ok. Could you scroll all the way\ down on the valve device page? There is a section at the bottom where it should say master true. If you could show me that at the same time as the state variables that would be great. There is something I'm doing wrong with the websocket that is frustrating the hell out of me and I may need to seek a little bit of expert help on it because I'm at the point of pulling my hair out! I have the webSocketOpen in both a state variable and a data value and they should ALWAYS be equal. I'd like to see if they are for you. Let me know if that dopesn't make sense!
Edit; I just added debug logging for some of the other errors you're seeing if you could grab the new app version
Let me add to your frustration 
I'm connecting and getting updated when I make changes in BHyve app but can't open/close with HE. If a valve opens/closes as part of a program, HE indicates that change.
However, I have never had websocketOpen say anything but false and retryCount and nextRetry are always 0. I have both a 6-station controller and the bridge and that is the same for both. Devices were created for all six stations, the bridge, and the screw-on hose valve.
I have latest version according to HPM.
I'd reinstall the app. The fact that nextRetry is 0 says it NEVER connected. The only time that value is ever 0 is when you first install the app
I have NO clue how I wasn't getting those errors but I just fixed it. Can you try the new app? I actually suspect this bug caused some bad things in the app state. Can you uninstall the app and reinstall? Also please wait about 10 minutes. I think that because of this bug I think their server is throttling you so give it 10 mins so it stops auto disconnecting you every time you connect.
1 Like
Definitely better. Two questions, what kind of devices do you have (hose timer or the multi-zone?). Curious too, are you currently watering? That line 388 error... I don't see how that would occur unless the valve is open.
Do you see log messages where it says it's reconnecting?
That was when I opened the valve via their app. No water it is on my desk clicking.
EDIT:
Only this once for the controller app, not the device or hub
I get this if I hit initialize in HE
but it does nothing.
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...
1 Like
still says 41 minutes, ago commit?
Thanks so much for trying all this. I'm sure you'll get it going.
Try now, I closed my laptop cover too quickly and it didn't upload
1 Like
