Adrian Sampson

Cool! I'll give this a try, do a thorough code review, and run some tests. I think the only visible change is the one @mineo mentioned above: the cause field...

Personally, I see no problems with breaking the API when going from 0.x to 1.x, or 1.x to 2.x if that's preferable. No need for a new Python module name....

Sadly, I believe `read` can raise errors (I'm about 75% confident about that). See also #123. :smiley:

I like the idea of returning an iterable from these functions. That would be a great way to provide pagination to clients of the library -- I imagine it working...

Hi there! Thanks for getting this started! I'm catching up on the PRs here, and although I know this is still WIP, I wanted to make a couple of notes:...

We'd love any help we can get!! Carefully figuring out what remains to be done based on the thread would be a great way to start…

That's actually the big question: nobody seems to be 100% sure whether we need both v1 and v2 support, or whether we can transition entirely to v2 without dropping support...

Home Assistant is telling you that you need to install the `wideq` module in a location where it can find it.

Something like that! But the details are really up to your system and Home Assistant itself. This is the kind of procedure that I used, but vagaries of the specific...

Thanks! That would indeed be #73. @cynicer, any chance you could take a look? It seems like some models may use a different/incompatible representation for swing mode…