[hydrawise][WIP] Fixes #7261

[digitaldan]

Fixes a NPE due to a change in the Hydrawise API, adds additional controller statuses as a channels, improves documentation.

Signed-off-by: digitaldan [email protected]

[TravisBuddy]

Travis tests were successful

Hey @digitaldan,
we found no major flaws with your code. Still you might want to look at this logfile, as we usually suggest some optional improvements.

[TravisBuddy]

Travis tests were successful

Hey @digitaldan,
we found no major flaws with your code. Still you might want to look at this logfile, as we usually suggest some optional improvements.

[digitaldan]

Thanks @cpmeister for the review!

[digitaldan]

Hold off on this one, i am looking through the API responses more carefully and realized there are more changes than just the controller online status.

[DenDeXTeR51]

1. They changed API(last year's API was better…) As i understand some information now is only available via GraphQL & OAuth2.0 and limited data via REST.

URL for new api - https://support.hydrawise.com/hc/en-us/articles/360008965753-Hydrawise-API-Information

2. Also they implement "refresh windows", now you cannot just update every 30 second. There is parameter in json (time for next request)

"Rate Limiting
Access to this API is rate limited. The statusschedule.php request has a field called nextpoll that indicates when the next API query should be made. Queries over this rate may be rejected with an HTTP 429 status code."

[digitaldan]

Thanks @DenDeXTeR51 , I'm aware of the new version of the API. Unfortunately they removed a lot of the functionality i was using . I have a GraphQL version of the binding in development now, which is what they use for their own clients and new integrations. It will allow the binding to retain its current functionally as well as get some new features. I'll post back here when i have a version ready for testing.

[digitaldan]

Closing this in favor of a new PR based on their GraphQL APi