HomeBridge 2.0

[Niklas31]

General idea

Could you please check will this plugin be impacted with new HomeBridge 2.0 and could we have it update it to support it.

[https://github.com/homebridge/homebridge/wiki/Updating-To-Homebridge-v2.0]

Use case

HomeBridge 2.0 is curte tou in beta, but plugins are being asked to show if their plugin works with it, since there are many underlying changes.

Once you have tested your plugin(s) function correctly on Homebridge v2, you can update your package.json's engines.homebridge value to show that your plugin is ready.

  "engines": {
    "homebridge": "^1.6.0 || ^2.0.0-beta.0",
    "node": "^18.20.4 || ^20.15.1"
  },

Users will see a green tick in the readiness check in the UI once they have installed a version of your plugin with this in the engines.

Once Homebridge v2 has been released, you can remove the -beta.0 from the homebridge versions.

Notes

No response

[AlexGustafsson]

Thank you for letting me know! I'll be sure to update what's necessary to ensure the plugin supports v2 going forward. I'll try to release a v7.0.0-beta.0 version. Once Homebridge 2.0 is released, I'll release a v7.0.0 and drop support for older node and homebridge versions as I don't really have the bandwidth to deal with multiple tracks.

[AlexGustafsson]

@Niklas31 v7.0.0-beta.0 is now published. There are no changes (at all) to the actual source code. But it has been configured and tested to work with Homebridge v2. I've decided to do a major bump due to the shift in supported node and Homebridge versions. Thanks again for letting me know about the change.

I'll keep this issue open until Homebridge v2 (and homebridge-wol v7.0.0) is released.

[alissaman]

Thanks @AlexGustafsson, this update did seem to fix an issue where it would not wake the pc after HomeBridge had been running for a while.

[Kazbah]

Update ?

[AlexGustafsson]

@Kazbah still waiting for homebridge 2.0 to be released. If you're not on a beta branch, the latest release should continue to work, it's OK to disregard any potential warnings that the plugin "won't work in 2.0". If you're running a homebridge beta, I hope homebridge-wol v7.0.0-beta.0 works for you.

[maxileith]

@Kazbah still waiting for homebridge 2.0 to be released. If you're not on a beta branch, the latest release should continue to work, it's OK to disregard any potential warnings that the plugin "won't work in 2.0". If you're running a homebridge beta, I hope homebridge-wol v7.0.0-beta.0 works for you.

What is the benefit of waiting for Homebridge v2? You could just drop support for outdated Node LTS now. Outdated Node LTS version are not supported by Homebridge v1 and v2 anyhow. Releasing it now would have the benefit that people can see that the plugin is compatible with v2 which is a nice peace of mind when upgrading. I understand that v6 of the plugin is compatible with Homebridge v2 as well. However, some people are looking for the green checks in the Homebridge UI for sure.

[jedis00]

@AlexGustafsson Can the latest version of the plugin be tagged as the beta branch? This is the only plugin left that shows it may not be compatible with Homebridge v2.0. Plugin version v6.0.1.

[AlexGustafsson]

@jedis00, @maxileith There's a 7.0.0-beta.0 tag and version. If you're running home bridge v2 and use that plugin version, you should be all set.

I don't have the bandwidth to support two tracks ATM, so I guarantee that v6 of the plugin will work with v1 of home bridge. Once v2 is released I will guarantee that v7 of the plugin will work and v6 will become unsupported. Although it could seem easy to support both home bridge versions, verification and building confidence takes a bit of time.

Feel free to try out the 7.0.0-beta.0 version of the plugin with home bridge v1 and report back and suggest fixes in #268. If everything works for you in home bridge v1 and home bridge v2, I could probably release the new version early. v6 of the plugin has been tested to support home bridge 1.7.0 and later, but should support all 1.x.x versions - so if you test, be sure to try out a few versions along the way to make sure everything works.