Badnest breaks.

[Jaguaza]

Home Assistant Core 2025.1.0 breaks badnest integration.

[Jaguaza]

Here I think they set out the solution:

badguy99/badnest#12

I understand little, if I could check.

[stanwebber]

hmm, i did not know about the extensive activity on the oegemeister/badnest repository. in any case, i bit the bullet and finally converted to a google account last year and paid the $5 developer fee to use the official ha integration. at the time, this original code from reddragon was still working for my original nest account and token refreshes were on the order of 1 per every other year. the reason i abandoned this code was because i had 2 thermostats on my account and google changed something slightly that caused my secondary thermostat to stop working--primary thermostat continued to function without issue.

no doubt ha 2025.1 has some breaking changes considering everything that's been deprecated over the past year. i use another abandoned custom integration for a wyzesense bridge that is running into the same problem. if anyone cares to apply fixes and author a pull request for badnest i can accept it, but there's no way for me to test it anymore.

[nemethloci]

To me it seems, that, the badguy99 version of this integration has more recent changes (Not that either would have any changes in the past almost 3 years, but at least my hot water control related changes are there in the other repo) and as such we plan to proceed merging in the proposed changes there, which will hopefully make that version to function with hass 2025.1.0
Does anybody know why we have so many independent forks of this integration?

[Jaguaza]

To me it seems, that, the badguy99 version of this integration has more recent changes (Not that either would have any changes in the past almost 3 years, but at least my hot water control related changes are there in the other repo) and as such we plan to proceed merging in the proposed changes there, which will hopefully make that version to function with hass 2025.1.0 Does anybody know why we have so many independent forks of this integration?

I don't understand programming. The only thing is that in the other repository the author is not available and does not accept the changes.

In this one the author as you indicated says that he can no longer test the changes but he would approve them.

I don't know why there are so many branches of this project but the truth is that so far it has been working correctly for me.

That's why I proposed this repository in the other thread, as the author is willing to help us by approving the changes and it is appreciated.

[nemethloci]

Ok, so i see two options:

• fastest: @badguy99 would approve the already existing PR in the other repo
• someone (me?) creates a PR of any diffs between the two repos + the PR from the other repo. This will likely take longer considering we have no idea how many merge conflicts there might be

I'll wait a day or two for badguy99 and then I'll see what I can do

[Jaguaza]

Ok, so i see two options:

• fastest: @badguy99 would approve the already existing PR in the other repo
• someone (me?) creates a PR of any diffs between the two repos + the PR from the other repo. This will likely take longer considering we have no idea how many merge conflicts there might be

I'll wait a day or two for badguy99 and then I'll see what I can do

Thanks!!!!!!!.

[stanwebber]

reddragon wrote the original code for badnest. all subsequent forks/repositories on github are derivatives of his work. my repository is a clone of reddragon's work before he decided he no longer wanted to support the project (which is his prerogative). the reason it exists is because, instead of archiving his repository and allowing everyone who forked it to still have historical read-only access, reddragon deleted all traces of his work like a child throwing a tantrum and taking all his toys home with him so nobody else can play.

his original code works well if you still have an original nest account and login. if you converted to a google account you should not be using it and move on to one of the other badnest forks hosted on github

[Jaguaza]

Well, that seems to be the end of it. No one has yet been able to do an update on this.