[hydrawise] Communication error #16570
Assignees
Labels
bug
An unexpected problem or unintended behavior of an add-on
Comments
Hmm, that's an error coming from the Hydrawise servers, seems like they have a bug, although i'm not sure why its working for me and others and not your account. You want want to try deleting the "account" and "controller" thing and add them back new. |
|
I removed already the Binding and the account thing's. No success, still did not work |
|
I started the DEBUG mode, here is the log entry: |
|
Can you turn on TRACE logging and see what we are sending? I wonder if its choking on a GraphQL variable that maybe is not supported in your region. |
|
Ok, here is the TRACE 👍 |
|
Can you try something for me?
{
me {
email
lastContact
controllers {
id
name
status {
summary
online
lastContact {
timestamp
}
}
location {
coordinates {
latitude
longitude
}
forecast(days: 3) {
time
updateTime
conditions
averageWindSpeed {
value
unit
}
highTemperature {
value
unit
}
lowTemperature {
value
unit
}
probabilityOfPrecipitation
precipitation {
value
unit
}
averageHumidity
}
}
zones {
id
name
status {
suspendedUntil {
timestamp
}
}
icon {
id
fileName
customImage {
id
url
}
}
number {
value
label
}
scheduledRuns {
summary
currentRun{
id
startTime {
timestamp
}
endTime {
timestamp
}
duration
status {
value
label
}
}
nextRun {
id
startTime {
timestamp
}
endTime {
timestamp
}
duration
}
}
}
sensors {
id
name
input {
number
label
}
status {
active
waterFlow {
value
unit
}
}
model {
modeType
active
offLevel
offTimer
delay
}
}
}
}
}
|
|
Ok Dan, here is the result of the query:
|
|
can you post a screen shot ? Does the left panel show any red, like its malformed ? |
|
also make sure these are selected 
|
|
Ok, here is what you want, no red on the left side
|
|
|
|
hmm, so odd, does your system show online when you login to the webportal? 
|
|
Yes both Hydrawise Controller are online and attached to the WLAN |
|
|
|
can you try removing sections in the GraphQL query and run again? I would start by removing forecast first forecast(days: 3) {
...
}then if that still breaks, remove zones, then sensors? I'm trying to isolate this to a specific part of the query thats breaking it for your account, I'm not sure what they don't like in it. |
|
I reduced the forecast up to this
Still errors, only if i take it completly out, then it works |
|
Ahhh, ok , thanks for doing that. i figured the broken promise on their end was trying to hit some 3rd party service. Let me think how i can fix this and still keep weather for the users where it works. |
|
Does the forecast works on your implementation? Where could i find the docu, on the hunter site is only an email address to ask questions? |
|
It does, and it works for others, but the API is not supported by them for 3rd party use, so i would not go asking questions and bringing attention to our binding |
|
out of curiosity, if you go back to the original query and replace the |
|
Dan, it give an error but the rest of the information seems to be ok.
|
|
Gotcha, thanks. If i have to i might make the weather part an option of the controller thing, so it can be disabled, although i think its still odd the query causes their backend to generate an error like that. If this was a public API i would open a bug ticket up, but since its not, will just have to work around it. |
|
May be they do not offer the forecast feature for germany/europe? |
Thats my suspicion too, but a GraphQL service should be returning an empty result when no results are available, not an internal error (looks like nodejs maybe?) which is definitely a bug on their end . I'm going to probably send a test GraphQL request to test if weather is supported and drop it if its not. Hopefully its not too much work. |
|
Thanks for your support i really appreciate your work. |
|
If you need someone fpr testing, don't hesitate to ask, i am interested in your solution and using the software. |
|
Same problem on Account thing - Request failed with HTTP status code: 400 response: {"errors":{"message":"Could not resolve promise"}} |
|
Where do you live? We think that Hydrawise did not offer the "forecast" in all countries, the problem seems to be, that Hydrawise answer this by an error message. |
|
Ukraine, forecast always work for me, so I dont know why its broken now... At HydraWise.com web-ui I see forecast and everything seems ok |
|
@digitaldan Can you add to Binding configuration option "Do not load forecasts" if this solves issue? At least we will have working zone triggers.... |
As i mentioned above, I'm going to detect if weather is supported in the binding, there will not be a need for manual configuration.
My guess is they use multiple weather providers depending on the region, and the code that does this is broken in the graphql endpoint for parts of Europe. It's likely they will fix this at some point, but until then we will just work around it. |
|
Dan, i have seen in the answer message that the forecast ist category "business", so may be this is only available for the commercial version?
|
|
Good find, but i'm not on a commercial system, so i don't think thats it. Also i think this must have broken recently due to a change on their side, so i think this is just a bug we have to work around. |
|
I send message to HydraWise API Support (hunterindustries.com) with link to our github discussion, hope they can help... |
|
Hey @DenDeXTeR51 let me handle this, maybe read the rest of the thread for context. |
|
@digitaldan Ok, Summer Season soon will start so hope new version of binding will be soon... Thanks! |
|
@digitaldan Any news? |
|
I have an updated version you can try, you can quickly update the binding from the OH CLI like this: bundle:update org.openhab.binding.hydrawise https://github.com/digitaldan/openhab-addons/releases/download/hydrawise-weather-fix/org.openhab.binding.hydrawise-4.2.0-SNAPSHOT.jarOr you can uninstall the old binding and drop the following in your addons folder:
I recommend using the first approach. Make sure to have DEBUG or TRACE logging enabled in case this does not work. |
|
Hi Dan, thanks for the new version, is this compatible to version 4.1.2, i am still on the stable version? |
|
Hi @digitaldan . Strange results... I update via karaf and get: After Update from openhab 4.1.1 to 4.1.2 and reboot
|
|
I'll build a 4.1 version and post back here. |
|
Thanks, tell me if you are ready with and i will test it ... |
|
ok new jar is at bundle:update org.openhab.binding.hydrawise https://github.com/digitaldan/openhab-addons/releases/download/hydrawise-weather-fix/org.openhab.binding.hydrawise-4.1.3-SNAPSHOT.jar |
|
Ok, still problems, i loaded it and restarted, it get once the information and then comes back to the old error message: Console output: Status: COMMUNICATION_ERROR Log File |
|
New logs after update jar |
|
@clown-m , well thats interesting, you can see that when i am sending just a request for weather data , and nothing else it actually works and we get weather data for your region. So then my code assumes weather is supported and uses the full GraphQL query with weather, which then of course fails. Sounds like its some kind of race condition in their code. I'll update the jar here today to take this into account. |
|
@digitaldan: Did you make further progress in your evaluations? |
|
I just updated the 4.1 version, its the same link, so bundle:update org.openhab.binding.hydrawise https://github.com/digitaldan/openhab-addons/releases/download/hydrawise-weather-fix/org.openhab.binding.hydrawise-4.1.3-SNAPSHOT.jarI have not had a chance to test yet , so 🤞 |
|
Looks much better, as expected, the forecast is all "NULL". Thanks, will try more test in the next days. It's getting back pretty cool, so no time for sprinkling. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I upgraded to 4.1.2 today while i saw that there is an authorization bugfix in the hydrawise binding done, but still i got this message after the upgrade in the BASIC UI Thing setup:
I am running the Hydrawise Binding on openHAB 4.1.2 stable version on a Debian Buster Machine.
This failure comes up since some days, all other APP's are running as normal.
Any idea?
The text was updated successfully, but these errors were encountered: