Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homebridge 2.0 #91

Open
rionshin opened this issue Jul 22, 2024 · 13 comments · May be fixed by #95
Open

Homebridge 2.0 #91

rionshin opened this issue Jul 22, 2024 · 13 comments · May be fixed by #95

Comments

@rionshin
Copy link

@nfarina 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

@JasonGoldenDDT
Copy link

**Receiving this message in Homebridge today.

is there any support this community can provide to assist in this remediation?**

Screenshot 2024-08-29 at 7 27 47 AM

@SawkeeReemo
Copy link

SawkeeReemo commented Sep 23, 2024

Please. 🙏 I rely on these too much.

@mmenanno
Copy link

mmenanno commented Oct 10, 2024

Notably once the plugin is tested for v2.0, updating the package.json's engines.homebridge value is how this plugin can get that green check.

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

@mserajnik
Copy link

mserajnik commented Oct 14, 2024

Comparing the plugin code to what's written here, it appears that there are no actual code changes necessary and simply updating the package.json should suffice:

diff --git a/package.json b/package.json
index 4be6bec..40def60 100644
--- a/package.json
+++ b/package.json
@@ -14,8 +14,8 @@
     "url": "http://github.com/nfarina/homebridge-dummy/issues"
   },
   "engines": {
-    "node": ">=0.12.0",
-    "homebridge": ">=0.2.0"
+    "node": "^18.20.4 || ^20.15.1 || ^22.0.0",
+    "homebridge": "^1.6.0 || ^2.0.0-beta.0"
   },
   "dependencies": {
     "node-persist": "^2.1.0"

I might test this later today and if it works, I'll open a PR.
Edit: I sadly didn't get around to test this yet because some other stuff came up but I hope to be able to do so within 1-2 weeks.

@brianleesmith
Copy link

@mserajnik Were you ever able to test this for compatibility?

@brianjw
Copy link

brianjw commented Dec 24, 2024

+1 for Homebridge 2.0 support

@Fofer
Copy link

Fofer commented Jan 1, 2025

I came here to request the same. Happy New Year to all!

@rjschutten
Copy link

rjschutten commented Jan 4, 2025

Bump on this issue; this is a core homebridge plugin used by many.

Should be fairly easy to check for compatibility with 2.0?

@TesterTi
Copy link

TesterTi commented Jan 4, 2025

I have just tested the plugin on beta23 of v2.0.0 and all seems to be working fine (for my setup)

@Lammiwinks
Copy link

Thanks, +1 for this too. Is this project abandoned?

@JasonGoldenDDT
Copy link

If the project has been abandoned, has anyone found a stable alternative? Can this project be transferred to a new developer?

If it's not abandoned can we understand the roadblocks so the community can assist?

@mserajnik mserajnik linked a pull request Jan 24, 2025 that will close this issue
@mserajnik
Copy link

@mserajnik Were you ever able to test this for compatibility?

Sorry for the delay. I finally got around to test it and like @TesterTi can also confirm it works for me; I've opened a PR accordingly.

@Plankske
Copy link

Hello,

I developed the plugin @vandubois/homebridge-virtual-switch that is Homebridge 2.0 ready and may be able to do what you need. It can be set to be persistent (or not), timed (or not), normally open (or closed).
(I needed it to check the Homebridge log file for certain log messages to appear – hence the development.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.