2022.2: Let's start streamlining!

Hi,

I understand you are frustrated and happy to chat with you more this, but see Legacy Nest - #7 by allenporter for the rationale behind the decision.

I’m pretty surprised at the reaction I have to admit. I set what I thought was a pretty reasonable time frame to give someone a chance to spin up a custom component. Do you think this won’t happen and nobody will volunteer to do this very straightforward task? I would do it (since it is pretty simple) but don’t want to give you the wrong expectation that I can maintain it given I don’t have a works with nest account. I am pretty surprised this qualifies at not putting thought into this given I’ve been maintaining this integration for the last year and a half without even having a works with nest account… It would be pretty a interesting sign to me if nobody found it worth the minimal effort to take over the existing code!

For example, someone is already working on a nest protect custom component prior to this.

2 Likes