Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing the non-aws Device code path. #33

Open
rainwoodman opened this issue Dec 14, 2024 · 1 comment
Open

Testing the non-aws Device code path. #33

rainwoodman opened this issue Dec 14, 2024 · 1 comment

Comments

@rainwoodman
Copy link
Contributor

I am not sure yet how, as I have not read the non-aws code path closely. The fundamentals should be quite similar but the IR implementation may be a bit different. So this may open up some ways of consolidating the implementations.

A few questions that may help us to set the prioritization of this work:

  • How frequent do we change the non-aws device code path?
  • How frequent do we add new support to non-aws devices?
  • What is our current coverage ratio?
  • Does blueair still appear to release new products with the non-aws BlueAir API?
@dahlb
Copy link
Owner

dahlb commented Dec 14, 2024

I have a classic 205, but I've added support for a few other models the past two weeks through issues on ha_blueair
currently non coverage for the non-aws device code paths
I thought blueair still sold devices that use the non-aws api, but I just reviewed their current listing and I think all those models that i've heard of use the aws api

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants