Can't configure the plugin.

[mdecaro]

Description of Issue

Can't configure the plugin. I tried using the UI, also tried manually editing the JSON.
ERROR LOADING PLUGIN homebridge-homeconnect SyntaxError Unexpected identifier assert

Expected Behaviour

Get to step where I get QR code for child bridge

Steps to Reproduce

Used UI or manual install - no luck

Plugin Version

1.0.3

Environment

• OS: macOS 14.6.1
• Node: 22.8.0
• Homebridge: 1.8.3 and 1.8.4

Home Connect Appliance(s)

Bosch frig

HomeKit App(s)

Apple Home

Diagnostic Checks

• Home Connect app is able to control the appliance with Wi-Fi disabled.
• Home Connect app shows three green lines in the Network section of the appliance Settings.
• Unofficial Home Connect Server Status shows servers up and no recent errors.
• Searched for previously reported issues and no similar ones found.
• Checked the Home Connect API errors and authorisation errors documentation.

Log File

[homebridge-homeconnect] file:///opt/homebrew/lib/node_modules/homebridge-homeconnect/dist/settings.js:3
import PACKAGE from '../package.json' assert { type: 'json' };
                                      ^^^^^^

SyntaxError: Unexpected identifier 'assert'
    at compileSourceTextModule (node:internal/modules/esm/utils:337:16)
    at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:166:18)
    at callTranslator (node:internal/modules/esm/loader:436:14)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:442:30)

Node.js v22.8.0

Configuration

Empty on new install for that plugin
Tried manually installing with client. - no luck

Additional Information

No response

[thoukydides]

I suspect that this is due to a change in Node.js 22, probably nodejs/node#51622. It looks like it should be a simple fix to adopt the new syntax for Node.js 22, and that new syntax appears to have been backported to Node.js 18 and 20… but I will need to run some tests to be sure, and will probably need to increase the minimum compatible version numbers on those branches, which will require some users to upgrade.

[mdecaro]

In the meantime, should I downgrade to node 20?

…

On Sep 16, 2024, at 3:34 PM, Alexander Thoukydides ***@***.***> wrote: I suspect that this is due to a change in Node.js 22, probably nodejs/node#51622 <nodejs/node#51622>. It looks like it should be a simple fix to adopt the new syntax for Node.js 22, and that new syntax appears to have been backported to Node.js 18 and 20… but I will need to run some tests to be sure, and will probably need to increase the minimum compatible version numbers on those branches, which will require some users to upgrade. — Reply to this email directly, view it on GitHub <#298 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AENJQIGCVGIA27JY4EON5R3ZW4XD5AVCNFSM6AAAAABOJ5LJEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTG42TINJUHA>. You are receiving this because you authored the thread.

[mdecaro]

I did downgrade to node 20.17 and it works fine.

…

On Sep 16, 2024, at 3:34 PM, Alexander Thoukydides ***@***.***> wrote: I suspect that this is due to a change in Node.js 22, probably nodejs/node#51622 <nodejs/node#51622>. It looks like it should be a simple fix to adopt the new syntax for Node.js 22, and that new syntax appears to have been backported to Node.js 18 and 20… but I will need to run some tests to be sure, and will probably need to increase the minimum compatible version numbers on those branches, which will require some users to upgrade. — Reply to this email directly, view it on GitHub <#298 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AENJQIGCVGIA27JY4EON5R3ZW4XD5AVCNFSM6AAAAABOJ5LJEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTG42TINJUHA>. You are receiving this because you authored the thread.

[thoukydides]

Homebridge officially only supports Node.js LTS releases - which are currently 18 and 20 - so downgrading is a good workaround.

However, Node.js 22 is expected to become an LTS release next month (October 2024) so I do need to fix this.

It looks like the fix will require a minimum of Node.js 18.20.0.
Node.js 19 (which is not an LTS release) will not be supported.

[thoukydides]

Should be fixed in v1.0.4.