zigbee2mqtt not working anymore #41
Comments
|
also the log specified in the first one: 0 info it worked if it ends with ok |
|
Did you reboot your machine in June and did before that you had manually setup node to be a newer version than v10.23.0? According to your log there is a "/home/pi/.nvm/" directory which might indicates multiple and potentially conflicting version of node. |
|
This issue is now on a fresh new setup.
Le dim. 12 sept. 2021 16 h 59, Fabien Benetou ***@***.***> a
écrit :
… Did you reboot your machine in June and did before that you had manually
setup node to be a newer version than v10.23.0?
According to your log there is a "/home/pi/.nvm/" directory which might
indicates multiple and potentially conflicting version of node.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSPAAAOUG2PBWPCP7VNWFLUBUIBJANCNFSM5DATLI2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Indeed I checked while writing this because I also had nvmrc and couldn't remember if it was due to my own tinkering or WebThings. I see that https://github.com/WebThingsIO/gateway/blob/v1.1.X/.nvmrc it pines node 10 so now I'm wondering if a dependency of this add-on has been deprecated and thus doesn't work with WebThings anymore. |
|
I see that mqtt 4 deprecated node end of life versions, so 10 is out. Maybe that's the problem. PS: also just noticed that WebThingsIO/gateway#2873 should be 12. |
|
I'm using tye zigbee addon for now, i wait to see the update, if you need
me to test stuff just ask, i'll be glad to help
Le dim. 12 sept. 2021 17 h 33, Fabien Benetou ***@***.***> a
écrit :
… I see that mqtt 4 deprecated node end of life versions, so 10 is out.
Maybe that's the problem.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSPAAC33GJGLN3A4GG3PI3UBUMDTANCNFSM5DATLI2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Indeed the zigbee-adapter add-on does work. I recommend you check its mqtt optional feature in case some of your hardware is not fully supported as-in. Pulling in @flatsiedatsie as this seeems serious. If the main platform the add-on is for, WebThings, is not compatible anymore might be important to check either a patch here or upstream. |
|
I got some more feature qith zigbee2mqtt(like having the time on my
thermostat) but that's not a big deal
Le dim. 12 sept. 2021 18 h 10, Fabien Benetou ***@***.***> a
écrit :
… Indeed the zigbee-adapter add-on does work. I recommend you check its mqtt
optional feature in case some of your hardware is not fully supported as-in.
Pulling in @flatsiedatsie <https://github.com/flatsiedatsie> as this
seeems serious. If the main platform the add-on is for, WebThings, is not
compatible anymore might be important to check either a patch here or
upstream.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSPAAD2GIRVNNYXVTMUSR3UBUQOZANCNFSM5DATLI2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Hi, i have a similar issue which I have posted Here |
|
I checked and I also have Can I simply update nodejs to some more recent version? Or would this break some other stuff of the webthings image? |
|
I'm running into this too. I'm looking into it. |
|
I managed to fi the issue. I first ran
and then
It could be that only the second part is needed. |
|
Hi, even after rebooting the gateway. |
|
You have to run the commands from inside this directory:
If you want to try, you can then build the zigbee2mqtt instance by running this command:
and then this should work:
A new version of the addon is on its way |
|
Thanks for these suggestions. I tried them but it seems there is still an unhandled promise rejection. See terminal output below.
|
|
Hi, I saw zigbee2mqtt was updated, however, the issue still persists and I get this error messages now...
any news on this? |
|
sorry for the long delay, i just try to reinstall the addons, and i got this error now:
longer log: 2021-11-01 20:36:53.438 INFO : zigbee2mqtt-adapter: basic configuration.yaml file was succesfully created! |
|
What kind of system are you running? Is this a Raspberry Pi with the provided gateway 1.0.0 image? That missing Node module is a bit strange. |
|
Yes raspberry pi with provided image
Le mer. 1 déc. 2021, 05 h 08, flatsiedatsie ***@***.***> a
écrit :
… What kind of system are you running? Is this a Raspberry Pi with the
provided gateway 1.0.0 image? That missing Node module is a bit strange.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSPAAHYBJES654EFY6FDYLUOXXYRANCNFSM5DATLI2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Can confirm the other issue I raised is on a brand new 1.0 RPI build |
|
I just did a test with a Raspberry Pi 3 and a fresh image of Gateway 1.0.0, and a freshly flashed CC2251 Zigbee stick. It installed fine. Very strange. There clearly is an issue, but I can't seem to reproduce it. Could it be that the installation process was interupted? After adding the addon it takes an additional 30 minutes for Zigbee2MQTT to be fully installed. Could you try uninstalling the addon and then running this command via the Seashell addon? It will remove any lingering settings, and will force zigbee2mqtt to be reinstalled.
Then reboot. Also, keep the 'auto-update' feature disabled. |
|
@TobiBu your error indicates something else is already using the USB stick. Make sure you uninstall the other Zigbee addon. You could install a newer version of node, but it's quite a hassle (you will need to update the gateway itself too, and addons might need a reinstall too, etc), and it shouldn't be necessary. |
|
@flatsiedatsie thanks a lot for your answer. It seems that solves the issue. Didn't know I had to uninstall the other add-on. |
|
on my side it's now working so i close this |
Since june, i'm unable to have zigbee2mqtt working,
i try to erase the .webthings folder to reset my data, not working.
i try to just reflash my sd card (i have the raspberry pi image on raspberry pi 3)
my hardware is conbee II usb stick
and there is the log
2021-08-29 21:38:36.521 ERROR : zigbee2mqtt-adapter: (node:1460) UnhandledPromiseRejectionWarning: Error: Command failed: npm run build
2021-08-29 21:38:36.524 ERROR : zigbee2mqtt-adapter: sh: 1: tsc: not found
2021-08-29 21:38:36.530 ERROR : zigbee2mqtt-adapter: npm ERR! code ELIFECYCLE
2021-08-29 21:38:36.532 ERROR : zigbee2mqtt-adapter: npm ERR! syscall spawn
2021-08-29 21:38:36.534 ERROR : zigbee2mqtt-adapter: npm ERR! file sh
2021-08-29 21:38:36.535 ERROR : zigbee2mqtt-adapter: npm ERR! errno ENOENT
2021-08-29 21:38:36.537 ERROR : zigbee2mqtt-adapter: npm ERR! zigbee2mqtt@1.21.0 build:
tsc && node index.js writehash2021-08-29 21:38:36.539 ERROR : zigbee2mqtt-adapter: npm ERR! spawn ENOENT
2021-08-29 21:38:36.541 ERROR : zigbee2mqtt-adapter: npm ERR!
2021-08-29 21:38:36.543 ERROR : zigbee2mqtt-adapter: npm ERR! Failed at the zigbee2mqtt@1.21.0 build script.
2021-08-29 21:38:36.545 ERROR : zigbee2mqtt-adapter: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-08-29 21:38:36.547 ERROR : zigbee2mqtt-adapter:
2021-08-29 21:38:36.549 ERROR : zigbee2mqtt-adapter: npm ERR! A complete log of this run can be found in:
2021-08-29 21:38:36.550 ERROR : zigbee2mqtt-adapter: npm ERR! /home/pi/.npm/_logs/2021-08-29T20_38_36_460Z-debug.log
2021-08-29 21:38:36.552 ERROR : zigbee2mqtt-adapter:
2021-08-29 21:38:36.554 ERROR : zigbee2mqtt-adapter: at ChildProcess.exithandler (child_process.js:294:12)
2021-08-29 21:38:36.556 ERROR : zigbee2mqtt-adapter: at ChildProcess.emit (events.js:198:13)
2021-08-29 21:38:36.558 ERROR : zigbee2mqtt-adapter: at maybeClose (internal/child_process.js:982:16)
2021-08-29 21:38:36.560 ERROR : zigbee2mqtt-adapter: at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
2021-08-29 21:38:36.562 ERROR : zigbee2mqtt-adapter: (node:1460) 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)
2021-08-29 21:38:36.564 ERROR : zigbee2mqtt-adapter: (node:1460) [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.
The text was updated successfully, but these errors were encountered: