upgrade creates new hub

[Vinisz]

Hi,

just upgraded to 1.0.1 and now, all my devices do not respond.
When investigating, I saw that a new hub /bridge is created (on my Iphone) to which now all of the devices are bound.
How do I get back my devices and old bridge ? I have 138 devices, reconfiguring them all is no option.

[crxporter]

Release notes for version 1.0.1 state that it breaks backwards compatibility with a link to this notice explaining that hubs will need to be deleted and re-added in the home app.

Unfortunately I don’t know of any way to go back unless you made a full backup of your environment before upgrading to 1.0.1.

One more comment- are you running all 138 devices on one bridge? Homekit guidelines aren’t to keep 100 or fewer with most users noticing the best speed with about 50 as the upper limit per bridge.

[Vinisz]

Ah ok, could not find release notes, thanks for pointing them out to me. I see it is stated there that there is no upgrade path, ok, that is clear. Can you tell me if that is “one time only” or that an upgrade is never possible, also not in future versions ? I do run all 138 on one bridge yes, I have no issues at all, I think those guidelines are coming from the fact if you really use homekit native, which this is of course not, It is just a link to my z-wave environment. I have a full backup yes, but if the reconfiguration I have to do is a one-time-only, then I think I will do it.. (might just be worth it) , If I have to do that every upgrade then I think an upgrade path should be there, please let me know. Greetings, Vinisz Van: crxporter <[email protected]> Verzonden: zaterdag 29 februari 2020 17:27 Aan: NRCHKB/node-red-contrib-homekit-bridged <[email protected]> CC: Vinisz <[email protected]>; Author <[email protected]> Onderwerp: Re: [NRCHKB/node-red-contrib-homekit-bridged] upgrade creates new hub (#215) Release notes <https://github.com/NRCHKB/node-red-contrib-homekit-bridged/releases/tag/v1.0.1> for version 1.0.1 state that it breaks backwards compatibility with a link to this notice <#163 (comment)> explaining that hubs will need to be deleted and re-added in the home app. Unfortunately I don’t know of any way to go back unless you made a full backup of your environment before upgrading to 1.0.1. One more comment- are you running all 138 devices on one bridge? Homekit guidelines aren’t to keep 100 or fewer with most users noticing the best speed with about 50 as the upper limit per bridge. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#215?email_source=notifications&email_token=AL2YLJBJNWPPFW7UW32PR7DRFE3NJA5CNFSM4K62DMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL6HWA#issuecomment-592962520> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL2YLJHXAHK3NFCOFMKDJKLRFE3NJANCNFSM4K62DMZQ> . <https://github.com/notifications/beacon/AL2YLJFVUAZVVSAWAZXH2T3RFE3NJA5CNFSM4K62DMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL6HWA.gif>

[crxporter]

Can you tell me if that is “one time only” or that an upgrade is never possible, also not in future versions ?

I don't remember what the "official" name for it is but we use a major-minor-bugfix version number system say X.Y.Z

A change in the X likely means a breaking change for a major update. A change in Y means a minor update with new features. A change in Z means a bug fix. Expect Z updates to have little or no effect on your setup. A Y update may add features but should be backwards compatible.

I'm impressed you have all 138 running in one bridge. Cool. Also yes this is a one-time breaking change, you shouldn't have to go through it again until a 2.0.0 version! If you watch the updates and github issues you'll be better prepared for knowing about breaking changes. I also just put in a pull request to add a prominent warning in the readme so others will see that 1.0.1 is a breaking change. Sorry you had to be the guinea pig.

Finally: while I have your attention, I'm getting ready to dump all of my insteon hardware (about 40 switches/dimmers) for zwave. If you don't mind, what hardware/software are you using for zwave?

[Vinisz]

Thanks for the fast response, like it.. No problem I went though it, I should have read the release notes better/searched better. Meanwhile I already restored my backup, all up and running again. I understand the version numbering, thanks for that. I you go for z-wave, go for quality.. or you will regret it. I have talked to lots of guys buying cheap stuff and complaining that they have problems. I use Fibaro modules and Qubino , go for z-wave plus if you can, lots of advantages. You pay a bit more but it works… (also a lot depends on the controller of course) Van: crxporter <[email protected]> Verzonden: zaterdag 29 februari 2020 18:21 Aan: NRCHKB/node-red-contrib-homekit-bridged <[email protected]> CC: Vinisz <[email protected]>; Author <[email protected]> Onderwerp: Re: [NRCHKB/node-red-contrib-homekit-bridged] upgrade creates new hub (#215) Can you tell me if that is “one time only” or that an upgrade is never possible, also not in future versions ? I don't remember what the "official" name for it is but we use a major-minor-bugfix version number system say X.Y.Z A change in the X likely means a breaking change for a major update. A change in Y means a minor update with new features. A change in Z means a bug fix. Expect Z updates to have little or no effect on your setup. A Y update may add features but should be backwards compatible. I'm impressed you have all 138 running in one bridge. Cool. Also yes this is a one-time breaking change, you shouldn't have to go through it again until a 2.0.0 version! If you watch the updates and github issues you'll be better prepared for knowing about breaking changes. I also just put in a pull request to add a prominent warning in the readme so others will see that 1.0.1 is a breaking change. Sorry you had to be the guinea pig. Finally: while I have your attention, I'm getting ready to dump all of my insteon hardware (about 40 switches/dimmers) for zwave. If you don't mind, what hardware/software are you using for zwave? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#215?email_source=notifications&email_token=AL2YLJDKFK3W5KRB7F4HSXLRFFBXVA5CNFSM4K62DMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL7VDQ#issuecomment-592968334> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL2YLJEOI7OKZTPSI6CXKDLRFFBXVANCNFSM4K62DMZQ> . <https://github.com/notifications/beacon/AL2YLJAEULQDUJG6MNOWOP3RFFBXVA5CNFSM4K62DMZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL7VDQ.gif>

[crxporter]

@Vinisz I believe we’re done here? Please come back if you have more questions.

@Shaquu we should be fine to close.

[Vinisz]

Yep, all done, thanks for the help 👍

…

Op 2 mrt. 2020 om 05:43 heeft crxporter ***@***.***> het volgende geschreven:  @Vinisz I believe we’re done here? Please come back if you have more questions. @Shaquu we should be fine to close. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.