homebridge-button-platform

[homebridge]

homebridge-button-platform

[oznu]

Yep, confirmed working on a recent version of v10. All good 😄!

The Active LTS versions of Node.js only overlap for 6 months, v10 is actually leaving "Active" status next month.

Doing major Node.js version updates is a source of many issues for Homebridge users, I would rank it as the #1 issue by far that I have been solving for users recently, often caused by them attempting to upgrade using some random instructions on the internet and then ending up with multiple versions of Node.js installed.

I did add Node.js upgrade instructions to the wiki for each platform about 9 months ago, so hopefully anyone who's followed those guides since should be ok.

[oznu]

• - The plugin must successfully install.
• - The plugin must impliment the Homebridge Plugin Settings GUI.
• - The plugin must not start unless it is configured.
• - The plugin must not execute postinstall scripts that modify the users system in any way.
• - The plugin must not contain any analytics or calls that enable you to track the user.
• - The plugin must not throw unhandled exceptions, the plugin must catch and log it's own errors.
• - The plugin must be published to npm and the source code available on GitHub.
• - The plugin must run on all Active LTS versions of Node.js, at the time of writing this is Node.js v10 and v12.
• - The plugin must not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
• - If the plugin needs to write files to disk (cache, keys, etc.), it must store them inside the Homebridge storage directory.

---

The plugin must run on all Active LTS versions of Node.js, at the time of writing this is Node.js v10 and v12.

The node version requirements in the package.json are set to >=12.15.0 and a few errors are thrown when running v10.15.1.

[3/27/2020, 7:37:32 PM] Plugin homebridge-button-platform requires Node version of >=12.15.0 which does not satisfy the current Node version of v10.15.1. You may need to upgrade your installation of Node.
[3/27/2020, 7:37:33 PM] [Button Platform] warning: npm registry: TypeError: events.once is not a function

https://nodejs.org/en/about/releases/

[Djelibeybi]

Yeah, this in an issue with https://github.com/ebaauw/homebridge-lib. I'll check with @ebaauw to see what his plans are.

[ebaauw]

when running v10.15.1.

v10.15.1 is not current. The current v10 release is v10.19.0.

[3/27/2020, 7:37:33 PM] [Button Platform] warning: npm registry: TypeError: events.once is not a function

events.once() was introduced in v10.16.0, see https://nodejs.org/docs/latest-v10.x/api/events.html#events_events_once_emitter_name.

[3/27/2020, 7:37:32 PM] Plugin homebridge-button-platform requires Node version of >=12.15.0 which does not satisfy the current Node version of v10.15.1. You may need to upgrade your installation of Node.

This (warning) message is actually given by Homebridge itself, based on the engines.node value from the plugin's package.json.
https://github.com/homebridge/homebridge/blob/e67630a3978aa126786711f8ec06610db517ca74/lib/plugin.js#L64
Homebridge-lib will also issue a warning message when the Node.js version doesn't match. I think npm will also bitch if you try and install the plugin using an older Node.js version.

Note that these are warning messages and in themselves don't break any functionality. Having said that, I develop and test my plugins (and homebridge-lib) against the latest LTS version of Node.js, currently v12.16.1. Other versions might or might not work; I simply don't have the bandwidth to test these. I really want to see a warning message in the log file when they're using another version; I've already spent too much time debugging issues that were caused by an ancient Node.js version.

Interestingly, homebridge-zp and homebridge-ws got put on the verified plugins list. They're based on homebridge-lib as well and have the same limitation.

[Djelibeybi]

Thanks @ebaauw!