You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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:
The text was updated successfully, but these errors were encountered: