Issue with webthings 1.1.0-alpha2

arist0v commented 1 year ago

i updated to webthings 1.1.0-alpha2 and i now have this issue(fresh install from .img)

022-12-06 13:14:48.015 INFO   : zigbee2mqtt-adapter: Opening database: /home/pi/.webthings/config/db.sqlite3
2022-12-06 13:14:48.065 INFO   : zigbee2mqtt-adapter: Ignoring https://raw.githubusercontent.com/WebThingsIO/gateway-addon-ipc-schema/master/schema.json because it has no messageType
2022-12-06 13:14:50.433 INFO   : zigbee2mqtt-adapter: Ignoring https://raw.githubusercontent.com/WebThingsIO/gateway-addon-ipc-schema/master/messages/definitions.json because it has no messageType
2022-12-06 13:14:54.949 INFO   : zigbee2mqtt-adapter: Loading add-on zigbee2mqtt-adapter from /home/pi/.webthings/addons/zigbee2mqtt-adapter
2022-12-06 13:14:55.134 ERROR  : zigbee2mqtt-adapter: The `manifest` object is deprecated and will be removed soon. Instead of using `manifest.name`, please read the `id` field from your manifest.json instead.
2022-12-06 13:14:55.135 ERROR  : zigbee2mqtt-adapter: The `manifest` object is deprecated and will be removed soon. Instead of using `manifest.moziot`, please read the user configuration with the `Database` class instead.
2022-12-06 13:14:55.140 INFO   : zigbee2mqtt-adapter: this.config.manual_toggle_response was undefined. Set to BOTH
2022-12-06 13:14:55.141 INFO   : zigbee2mqtt-adapter: Serial port is not defined in settings. Will attempt auto-detect.
2022-12-06 13:14:55.175 INFO   : zigbee2mqtt-adapter: - USB stick spotted at: /dev/ttyACM0
2022-12-06 13:14:55.177 INFO   : zigbee2mqtt-adapter: this.zigbee2mqtt_dir_path =  /home/pi/.webthings/data/zigbee2mqtt-adapter/zigbee2mqtt
2022-12-06 13:14:55.210 INFO   : zigbee2mqtt-adapter: basic configuration.yaml file was succesfully created!
2022-12-06 13:15:05.187 INFO   : zigbee2mqtt-adapter: attempting to latch onto MQTT
2022-12-06 13:15:05.928 INFO   : zigbee2mqtt-adapter: ola running stdout:       Zigbee2MQTT requires node version ^14 || ^16 || ^18 || ^19, you are running v10.24.1!
2022-12-06 13:15:05.930 INFO   : zigbee2mqtt-adapter: 
2022-12-06 13:15:05.932 INFO   : zigbee2mqtt-adapter: 
2022-12-06 13:15:09.092 INFO   : zigbee2mqtt-adapter: ola stderr: (node:7439) UnhandledPromiseRejectionWarning: /home/pi/.webthings/data/zigbee2mqtt-adapter/zigbee2mqtt/node_modules/axios/index.js:1
2022-12-06 13:15:09.093 INFO   : zigbee2mqtt-adapter: import axios from './lib/axios.js';
2022-12-06 13:15:09.095 INFO   : zigbee2mqtt-adapter:        ^^^^^
2022-12-06 13:15:09.097 INFO   : zigbee2mqtt-adapter: 
2022-12-06 13:15:09.108 INFO   : zigbee2mqtt-adapter: SyntaxError: Unexpected identifier
2022-12-06 13:15:09.110 INFO   : zigbee2mqtt-adapter:     at Module._compile (internal/modules/cjs/loader.js:723:23)
2022-12-06 13:15:09.112 INFO   : zigbee2mqtt-adapter:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
2022-12-06 13:15:09.113 INFO   : zigbee2mqtt-adapter:     at Module.load (internal/modules/cjs/loader.js:653:32)
2022-12-06 13:15:09.115 INFO   : zigbee2mqtt-adapter:     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
2022-12-06 13:15:09.117 INFO   : zigbee2mqtt-adapter:     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
2022-12-06 13:15:09.119 INFO   : zigbee2mqtt-adapter:     at Module.require (internal/modules/cjs/loader.js:692:17)
2022-12-06 13:15:09.121 INFO   : zigbee2mqtt-adapter:     at require (internal/modules/cjs/helpers.js:25:18)
2022-12-06 13:15:09.123 INFO   : zigbee2mqtt-adapter:     at Object.getAxios (/home/pi/.webthings/data/zigbee2mqtt-adapter/zigbee2mqtt/node_modules/zigbee-herdsman-converters/lib/ota/common.js:464:19)
2022-12-06 13:15:09.125 INFO   : zigbee2mqtt-adapter:     at Object.<anonymous> (/home/pi/.webthings/data/zigbee2mqtt-adapter/zigbee2mqtt/node_modules/zigbee-herdsman-converters/lib/ota/inovelli.js:2:22)
2022-12-06 13:15:09.127 INFO   : zigbee2mqtt-adapter:     at Module._compile (internal/modules/cjs/loader.js:778:30)
2022-12-06 13:15:09.129 INFO   : zigbee2mqtt-adapter: 
2022-12-06 13:15:09.131 INFO   : zigbee2mqtt-adapter: ola stderr: (node:7439) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
2022-12-06 13:15:09.132 INFO   : zigbee2mqtt-adapter: (node:7439) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

benfrancis commented 1 year ago

Zigbee2MQTT requires node version ^14 || ^16 || ^18 || ^19, you are running v10.24.1!

Is this the problem?

WebThings Gateway 1.0 shipped with node 10.x as well. Is this problem reproduceable on a clean install of WebThings Gateway 1.0 as well?

arist0v commented 1 year ago

on webthings 1.0 it was working out of the box (maybe a max 3 months install)

this was on boot, when i try to pair i have no error, but i can't find any device (and with the zgibee-adapter i can )

benfrancis commented 1 year ago

If I've understood correctly, the add-on clones and builds the master branch of zigbe2mqtt from GitHub at run time.

Node 10 support was dropped from the master branch of zigbee2mqtt on 5th November.

This means that the add-on will no longer work with any version of WebThings Gateway.

The zigbee-adapter takes a different approach by talking to an existing installation of zigbee2mqtt rather than trying to install the whole zigbee2mqtt stack from source. I don't really like either approach.

Pulling down the latest master from GitHub is a bad approach because everyone gets a slightly different version of the software, which is then never updated. The master branch is very likely to contain bugs and it's impossible to audit the source code in advance of approving a new version of the add-on.

Relying on an existing installation means it can't be enabled from the graphical user interface and relies on a user manually installing dependencies on the command line.

I'm not familiar enough with the zigbee2mqtt stack to be able to suggest a better option. I assume it's not possible to just make the zigbee2mqtt npm package a dependency of the add-on and ship it with the add-on?

The quick and dirty fix to this bug would be to create a version of the add-on which checks out a specific tag of the zigbee2mqtt GitHub repo which is known to work with WebThings Gateway, then make that version available in the WebThings add-ons list.

However, I note that the WebThings Gateway add-ons list is now way behind on releases of this add-on which is now mainly aimed at Candle, so another option is to simply remove it from the add-ons list in favour of the original zigbee-adapter. This would help prevent confusion (between the two Zigbee add-ons, which both support zigbee2mqtt) and broken installs, but would make zigbee2mqtt harder for end users to set up on WebThings Gateway (when it's working).

arist0v commented 1 year ago

but zigbee2mqtt offer better device support than zigbee adapter(my ikea smart plug aren't visible at all, my sinope thermostat have better support) so i'm not sure removing it is the best solution since the addon is (in my opinion) better than zigbee-adapter

the best solution would be probably to package the addon with a static version of zigbee2mqtt instead of getting the latest at install time,

maybe this check could be based on the node version available on the system

benfrancis commented 1 year ago

but zigbee2mqtt offer better device support than zigbee adapter

The zigbee-adapter supports all the same devices as the zigbee2mqtt-adapter, the difference is just in how zigbee2mqtt is installed, and the user interface. I don't think either currently has the best solution.

the best solution would be probably to package the addon with a static version of zigbee2mqtt instead of getting the latest at install time, maybe this check could be based on the node version available on the system

It can only be one or the other of these, it can't be both.

arist0v commented 1 year ago

I can assure you some of my device didn't work with zigbee-adapter, or have not optimal support. So it's wrong to say it's the same!

Le mar. 6 déc. 2022, 10 h 42, Ben Francis @.***> a écrit :

but zigbee2mqtt offer better device support than zigbee adapter

The zigbee-adapter supports all the same devices as the zigbee2mqtt-adapter, the difference is just in how zigbee2mqtt is installed, and the user interface. I don't think either currently has the best solution.

the best solution would be probably to package the addon with a static version of zigbee2mqtt instead of getting the latest at install time, maybe this check could be based on the node version available on the system

It can only be one or the other of these, it can't be both.

— Reply to this email directly, view it on GitHub https://github.com/kabbi/zigbee2mqtt-adapter/issues/56#issuecomment-1339572185, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSPAACIHAGMWAQ6NZXK2TLWL5NEXANCNFSM6AAAAAASVP3NCI . You are receiving this because you authored the thread.Message ID: @.***>

benfrancis commented 1 year ago

I can assure you some of my device didn't work with zigbee-adapter, or have not optimal support. So it's wrong to say it's the same!

I don't think you've understood what I'm saying. Did you install zigbee2mqtt and configure the add-on to use it as described in the README?

arist0v commented 1 year ago

I didn't install.it manually since there is no addon for it and zigbee2mqtt-adapter use to Handler everything without issue

Le mar. 6 déc. 2022, 10 h 46, Ben Francis @.***> a écrit :

I can assure you some of my device didn't work with zigbee-adapter, or have not optimal support. So it's wrong to say it's the same!

I don't think you've understood what I'm saying. Did you install zigbee2mqtt and configure the add-on to use it as described in the README https://github.com/WebThingsIO/zigbee-adapter/blob/master/README.md?

— Reply to this email directly, view it on GitHub https://github.com/kabbi/zigbee2mqtt-adapter/issues/56#issuecomment-1339578012, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSPAAAITOQJAK7CBGAQTGTWL5NUJANCNFSM6AAAAAASVP3NCI . You are receiving this because you authored the thread.Message ID: @.***>

flatsiedatsie commented 1 year ago

Zigbee2MQTT requires node version ^14 || ^16 || ^18 || ^19, you are running v10.24.1!

Is this the problem?

I'm not sure. The problem is indeed with Zigbee2MQTT.

It's easy to test. Does the Z2M addon still install and run OK on Gateway 1.0? If so, then something has changed with this alpha. If not, then Zigbee2MQTT has finally made a breaking change (that warning has been there for months).

I did a quick search and the first hit - from a different project but with the same error - mentions that this is indeed related to Node 10. They recommend upgradind to node 12.

https://stackoverflow.com/questions/74214663/unexpected-identifier-import-axios-from-lib-axios-js-requireaxios

Luckily Candle is on Node 12.

Did you install zigbee2mqtt and configure the add-on to use it as described in the README

If the addon can't install it, won't a user run into the same problem with a manual installation? Although they could try to install an older version of Zigbee2MQTT.

Pulling down the latest master from GitHub is a bad approach

True. I've been meaning to switch that to downloading the latest official release. Although it's never caused problems because the Z2M project does development in a dev branch, and they keep the main branch pretty stable.

another option is to simply remove it from the add-ons list

If Gateway 1.1 remains at node 10 then there is little other choice.

benfrancis commented 1 year ago

Zigbee2MQTT requires node version ^14 || ^16 || ^18 || ^19, you are running v10.24.1! Is this the problem?

I'm not sure. The problem is indeed with Zigbee2MQTT.

It's easy to test. Does the Z2M addon still install and run OK on Gateway 1.0?

I haven't tested this. @arist0v says it works, but I think that's because he installed it before the change was made to zigbee2mqtt. I note that removing the zigbee2mqtt add-on does not remove zigbee2mqtt, so it would need to be tested on a clean install of 1.0.

If so, then something has changed with this alpha. If not, then Zigbee2MQTT has finally made a breaking change (that warning has been there for months).

I did a quick search and the first hit - from a different project but with the same error - mentions that this is indeed related to Node 10. They recommend upgradind to node 12.

https://stackoverflow.com/questions/74214663/unexpected-identifier-import-axios-from-lib-axios-js-requireaxios

Luckily Candle is on Node 12.

Have you done a clean install using Node 12 recently? The warning says it requires version 14. It would be good to know whether it works with Node 12.

I'm reluctant to bump the Node version in WebThings Gateway 1.1 because I don't want to further delay the release, which fixes the urgent TLS certificate issue, and we don't know what new issues it will create.

We could definitely try to bump Node to version 12 in 1.2 though.

Did you install zigbee2mqtt and configure the add-on to use it as described in the README

If the addon can't install it, won't a user run into the same problem with a manual installation? Although they could try to install an older version of Zigbee2MQTT.

Yes, but this comment was about device compatibility, not Node.js compatibility.

Pulling down the latest master from GitHub is a bad approach

True. I've been meaning to switch that to downloading the latest official release. Although it's never caused problems because the Z2M project does development in a dev branch, and they keep the main branch pretty stable.

Downloading the latest official release wouldn't have prevented this bug, it would need to be pinned to a release which is known to work.

Is it possible to install zigbee2mqtt as an npm package dependency (pinned to a particular version) packaged with the add-on, or does it have to be checked out from git for some reason?

another option is to simply remove it from the add-ons list

If Gateway 1.1 remains at node 10 then there is little other choice.

The other choice is to release a version of the add-on which downloads a version of zigbee2mqtt which works with WebThings Gateway. Let me know which option you would prefer.

arist0v commented 1 year ago

My choice would go on a lower zigbee2mqtt version until we could fix the whole.things

arist0v commented 1 year ago

at my understanding, it could have multiple node version on the same system(same as python) so could it be a way to have a zigbee2mqtt addon (not zigbee2mqtt-adapter) that provide the zigbee2mqtt server directly into webthings?

edit: quick answer could be yes:

manifest.json:

"exec": "{nodeLoader} {path}",

replacing nodeLoader by the node executable provided by the package ex:

"exec": "./node/bin/node {path}",

flatsiedatsie commented 1 year ago

@aristov Addons are not allowed to make such big changes to the system (and on Candle it wouldn't even work because the system is read-only).

I just did a test and on Candle (read: Node 12) Zigbee2MQTT is still working.

or does it have to be checked out from git for some reason?

The idea is that people could update Z2M independently to get better device support even when the addon itself is not being updated.

aristov commented 1 year ago

/cc @arist0v

arist0v commented 1 year ago

So a solution could be to update node to 12

arist0v commented 1 year ago

In fact, after few research, you could package the binary of node and npm inside your addon : https://stackoverflow.com/a/13390989/19411871

so the point is now, could it run on a different version of node than the gateway, so the gateway didn'T change his node version, but the addon use a different one provided inside his own code ?

benfrancis commented 1 year ago

I don't think we would allow that in the WebThings add-on directory. If every add-on ships its own version of Node.js then things are going to get complicated quickly.

We need to be able to gracefully manage upgrades between versions in OTA updates, and most add-ons use the gateway's version of gateway-addon-node in order to prevent compatibility problems at the IPC layer.

I suggest either pinning an older version of zigbee2mqtt which is known to work with Node 10 (until we try to upgrade Node in WebThings Gateway 1.2) and releasing a version which uses that, or removing the add-on from the WebThings add-ons list until its compatible again.

Users can still use their own zigbee2mqtt installation using the WebThingsIO zigbee-adapter.

arist0v commented 1 year ago

@benfrancis

I belive (i could be wrong) that node is similar to python, multiple version could exist on a same os at the same time, so the following could apply to both:

I don't think we would allow that in the WebThings add-on directory. If every add-on ships its own version of Node.js then things are going to get complicated quickly.

There is no reason since the addon won'T install but only provide the binary the same way the lib folder provide the python pip library without installing it on the os for everyone (so we could in the same way have multiple version of a library on the gateway at the same time)

We need to be able to gracefully manage upgrades between versions in OTA updates, and most add-ons use the gateway's version of gateway-addon-node in order to prevent compatibility problems at the IPC layer.

if node is like python, a library design in python 3.7 should (in theory) run without any issue on a newer version of the same major branch (so 2.7 won'T work out of the box with 3.9) and since you told me if i want an addon that need python 3.10 i could install it manually on the os to be able to run my addon, there is then no difference at all between the two solution (manual os install of a different version and providing binary) so no issue on the IPC level since the same library will be used and the provided binary won'T affect the whole webthings gateway l Please confirm me if i'm wrong or not on any of the point, i think this solution could be a better way to work for those who may need a different version of a interpreter (python, node, etc...) and won'T affect the whole system at all since it will be like the way we package the library manually ourself by creating a lib folder and linking it from inside the code.

If you want to test, i could easily create a (python) example of this situation and create a test addon to demonstrate the whole concept and proove it wouldn't affect anything.

benfrancis commented 1 year ago

since you told me if i want an addon that need python 3.10 i could install it manually on the os to be able to run my addon, there is then no difference at all between the two solution (manual os install of a different version and providing binary)

I don't remember saying that, but there's a difference between you manually installing something on your own system, and your add-on acting as a package manager for other users without them necessarily knowing about it.

The add-ons system is designed to only show add-ons to users which are compatible with the versions of Node.js and Python running on their system. Circumventing this mechanism will break assumptions and cause problems.

It's possible that in 2.0 we may support a containerised base operating system in which this kind of thing would be safe to do, but for 1.x if you want to include your add-on in the WebThings add-on directory you need to find another solution.

All you need to do is ship a version of the Zigbee2MQTT library which works with Node 10. That could be a one line change to the source code of the add-on if you just check out a tag from GitHub.

arist0v commented 1 year ago

I don't remember saying that, but there's a difference between you manually installing something on your own system, and your add-on acting as a package manager for other users without them necessarily knowing about it.

there is a difference as acting as a package manager, and providing a binary file that is use by the addon, so the addon won'T act as a binary manager, the same way it didn'T act as a library manager (it didn'T replace pip for python, it only provide all the necessary binary)

But i understand your point of view even if i disagree. so let see what the maintainer of the addon will do , but thank you for your time and answer

flatsiedatsie commented 1 year ago

You could just use Candle?

The next release of Candle will run on Node 16, possibly 18. Addons will still run on Node 12, although they will be able to request running on later available versions.

benfrancis commented 1 year ago

@arist0v wrote:

there is a difference as acting as a package manager, and providing a binary file that is use by the addon, so the addon won'T act as a binary manager, the same way it didn'T act as a library manager (it didn'T replace pip for python, it only provide all the necessary binary)

I do agree with that bundling the runtime with the add-on is not the same as installing it system-wide, but I still don't think it's a good idea. I would encourage you to think not only about the initial installation, but the whole lifetime of the add-on, how it is updated and how it interacts with other aspects of the system such as automatic updates to the gateway-addon-node library, which may not remain compatible with the version of Node.js you ship.

I had a chat with Tim (the owner of the Add-ons System module), and he agrees that add-ons should not package their own runtime. The current add-on system is designed to use the resources provided by the system (including the runtime and the add-on library) and packaging the runtime with the add-on could cause "unforeseen consequences".

We would like to make add-ons more loosely coupled with the gateway in the future by running them inside containers and versioning the IPC protocol. This would allow more freedom in what can be safely bundled with an add-on without impacting the wider system.

In the meantime, we suggest doing two things:

Update the versions field in the current add-on manifest, because it currently claims the add-on will work with "any" version of Node.js, which is not the case
Consider providing a second package which is pinned to a Node 10 compatible version of Zigbee2MQTT

The former will prevent incompatible gateways running Node 10 from downloading the add-on whilst allowing other gateways to use a newer version of the library. The latter would provide an alternative option for gateways running Node 10 (including everyone using the WebThings Gateway Raspberry Pi image).

The first action is really a requirement if you want to continue to list the Zigbee2MQTT add-on in the WebThings add-ons directory, but whether you want to carry out the second action is up to you.

I hope this helps.

arist0v commented 1 year ago

so i replaced :

exec(`git clone --depth=1 https://github.com/Koenkk/zigbee2mqtt ${this.zigbee2mqtt_dir_path}`, (err, stdout, stderr) => {

by:

exec(`git clone --branch 1.28.0 --depth=1 https://github.com/Koenkk/zigbee2mqtt ${this.zigbee2mqtt_dir_path}`, (err, stdout, stderr) => {

and now everything is working!!!!

arist0v commented 1 year ago

at 1.28.1 it's not working so 1.28.0 is the latest that support the webthings gateway

flatsiedatsie commented 1 year ago

I've created a pull request to change the addon manifest. It now lists the node versions that Z2M officially works with. https://github.com/WebThingsIO/addon-list/blob/master/addons/zigbee2mqtt-adapter.json

arist0v commented 1 year ago

Could it be a good idea to provide a second version of the addon for webthings i'm probably not the only one to use it?

Le mer. 14 déc. 2022, 06 h 44, flatsiedatsie @.***> a écrit :

I've created a pull request to change the addon manifest. It now lists the node versions that Z2M officially works with.

https://github.com/WebThingsIO/addon-list/blob/master/addons/zigbee2mqtt-adapter.json

— Reply to this email directly, view it on GitHub https://github.com/kabbi/zigbee2mqtt-adapter/issues/56#issuecomment-1351122726, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSPAAFPJLQU3TMH5LVSI2LWNGXLBANCNFSM6AAAAAASVP3NCI . You are receiving this because you were mentioned.Message ID: @.***>

arist0v commented 1 year ago

I think you can include in the manifest a version for if the node version is lower, if you want i could try to create it

Le mer. 14 déc. 2022, 06 h 47, Martin Verret @.***> a écrit :

Could it be a good idea to provide a second version of the addon for webthings i'm probably not the only one to use it?

Le mer. 14 déc. 2022, 06 h 44, flatsiedatsie @.***> a écrit :

I've created a pull request to change the addon manifest. It now lists the node versions that Z2M officially works with.

https://github.com/WebThingsIO/addon-list/blob/master/addons/zigbee2mqtt-adapter.json

— Reply to this email directly, view it on GitHub https://github.com/kabbi/zigbee2mqtt-adapter/issues/56#issuecomment-1351122726, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSPAAFPJLQU3TMH5LVSI2LWNGXLBANCNFSM6AAAAAASVP3NCI . You are receiving this because you were mentioned.Message ID: @.***>

flatsiedatsie commented 1 year ago

I'm a little hesitant to have to manage addon store updates for two systems. In general the Webthings Gateway is rather unwelcoming towards my addons, so I'd prefer the lowest energy solutions to supporting existing users.

Some options I see:

Manage addon updates for two sytems
Make the Candle store available for the Webthings Gateway. That would mean I only have to manage updates in one location. It would create more incentive to keep addons cross-compatible. Some will likely never be 100% compatible though because the Webthings Gateway lacks things that the Candle disk image has, such as Bluetooth audio streaming support. Those could be filtered out or gracefully degraded.
Push for the Webthings Gateway to run on Node 12 or higher. Candle will soon run on node 18.

arist0v commented 1 year ago

In fact, doing it the right way mean:

creating a special release once only for webthings
editing the manifest to say, if node is 10.24 then the package is this release

After that no update necessary until webthings 2.0

I'm a beginner in node, but i could offer you to adapt both the zigbee2mqtt-adapter.js and manifest.json so you won't have to handle it

Second option, i could fork the current adapter and handle the webthings addons and yours could be removed from webthings and only be in candle.

Since it's your addon and i don't want to "steal" it, tell me ypur favorite option(credit to the official source will be in the readme)

Le mer. 14 déc. 2022, 06 h 57, flatsiedatsie @.***> a écrit :

I'm a little hesitant to have to manage addon store updates for two systems. In general the Webthings Gateway is rather unwelcoming towards my adons, so I'd prefer the lowest energy solutions to supporting existing users of my addons.

Some options I see:

Manage addon updates for two sytems

Make the Candle store available for the Webthings Gateway. That would mean I only have to manage updates in one location. It would create more incentive to keep addons cross-compatible. Some will likely never be compatible though because the Webthings Gateway lacks things that the Candle disk image has, such as Bluetooth audio streaming support.

Push for the Webthings Gateway to run on Node 12 or higher. Candle will soon run on node 18.

— Reply to this email directly, view it on GitHub https://github.com/kabbi/zigbee2mqtt-adapter/issues/56#issuecomment-1351173483, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSPAADEEXLD6WQXUEJ3FNTWNGY3FANCNFSM6AAAAAASVP3NCI . You are receiving this because you were mentioned.Message ID: @.***>

kabbi / zigbee2mqtt-adapter

Issue with webthings 1.1.0-alpha2 #56