Version 2.0.0: Test help needed! #73

madchicken · 2021-01-10T13:43:40Z

madchicken
Jan 10, 2021
Maintainer

Hi! thanks a lot to support this project by opening issues and PRs! Latest month was exiting for me since I was able to finally working again on this side project and fix many issues I knew were hitting many users out there.
Thanks to the Christmas break I started rewriting a bit the core layer of the plugin, and I am now in the process to release a new 2.0.0 version. The plugin is still the same, but internally I worked to better reuse code between different devices and going towards a more generic approach in mapping ZigBee devices into HomeKit. This should allow me in the future to map new and unsupported devices by just adding them in the configuration (and unburden your pain when you have a new device that doesn't work yet). The current way of writing support for devices will still be available to support special cases where the generic approach is not enough to make the device work properly. This is the case for example of multi switches, where they are all exposing different actions and it would be confusing (although not impossible) using a configuration to map them.
This change also make writing new device classes easier, since the update process is now centralised into the ZigBeeAccessory abstract class. You need to override the update method only if you need to handle a non-common behaviour.
I am also expanding the UI: now you can set and get custom device states using the new tab in the device properties side panel. Using that, you can configure specific parameters that cannot be exposed to HomeKit (such as the sensibility of a light ambient sensor). For the first release the UI will be very basic, with just a text area where you have to past a valid JSON state to configure the device, but in the future I would like to add specific panels depending on the device.

Before releasing this new version I'd like some of you to test it, to understand if I not broke anything that I could not test (I don't own all the devices the plugin supports!!!)

To install this version, please use the unstable npm tag:

npm i homebridge-zigbee-nt@unstable -g

to go back to the stable release just use the latest tag:

npm i homebridge-zigbee-nt@latest -g

Mentioning some of you here
@manuchis @EdwardChamberlain @zeno-at @wamfox @lucaskoehler @AlexKusnezov @madmarf @L-C-P @jandre3000 @maccoylton

manuchis · 2021-01-10T14:23:47Z

manuchis
Jan 10, 2021

Glad to hear that, Great job! I will try to test it. Because I built it in my RPi, I don’t know if I will lose my devices if I do the npm install or I need to rebuild it locally. What do you suggest?

1 reply

madchicken Jan 10, 2021
Maintainer Author

You won't loose your devices in both cases. Just a warning: the build process is now much heavier because of the UI. I suggest you to install using npm, or build it on a computer and the copying the dist folder into the raspberry

manuchis · 2021-01-10T14:33:36Z

manuchis
Jan 10, 2021

Yes, indeed, it was a pain last time. That is why asked. Thanks, I will tell you later.

0 replies

EdwardChamberlain · 2021-01-10T15:00:05Z

EdwardChamberlain
Jan 10, 2021

I will attempt to install this and let you know how it goes.

A potential issue I noticed and was wanting to raise with you is that currently the webUI on port 9000 doesn't require authentication but exposes the option to delete accessories - a potential security risk! Would it be possible to explore the option of either requiring authentication (similar to the home bridge webUI) or introducing a toggle to disable the webUI when not required?

Edit: I see a toggle to disable the UI! Please ignore!

1 reply

madchicken Jan 10, 2021
Maintainer Author

Yes, you can disable it. Anyway having a simple basic authentication would help to protect your network!

EdwardChamberlain · 2021-01-10T15:24:01Z

EdwardChamberlain
Jan 10, 2021

Picking up a few (new) errors on the latest 2.0.0 version.

[1/10/2021, 15:14:12] [ZigBee] Reporting state for 0x680ae2fffe770c4f: OFF (false)
Rejecting unresolved promise after 9550ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 5876ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 6669ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 6020ms ("0x086bd7fffe3521ed|1")
[1/10/2021, 15:14:24] [ZigBee] Reading 'state' to '0x086bd7fffe3521ed' failed: 'Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))'
[1/10/2021, 15:14:25] [ZigBee] Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:367:23)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)
[1/10/2021, 15:14:45] [ZigBee] Reading 'state' to '0x086bd7fffe3521ed' failed: 'Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))'
[1/10/2021, 15:14:45] [ZigBee] Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:367:23)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)
[1/10/2021, 15:15:05] [ZigBee] Reading 'state' to '0x086bd7fffe3521ed' failed: 'Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))'
[1/10/2021, 15:15:05] [ZigBee] Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:367:23)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)
[1/10/2021, 15:15:26] [ZigBee] Reading 'state' to '0x086bd7fffe3521ed' failed: 'Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))'
[1/10/2021, 15:15:26] [ZigBee] Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:367:23)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)
[1/10/2021, 15:19:50] [ZigBee] Reading 'state' from '0x000d6ffffeff6164, message in queue 0x000d6ffffeff6164|1'
[1/10/2021, 15:19:50] [ZigBee] Sent 1 messages for device TRADFRI control outlet
[1/10/2021, 15:19:50] [ZigBee] Reading 'state' from '0x086bd7fffe519524, message in queue 0x086bd7fffe519524|1'
[1/10/2021, 15:19:50] [ZigBee] Sent 1 messages for device TRADFRI control outlet
[1/10/2021, 15:19:50] [ZigBee] Reading 'state' from '0x086bd7fffe3521ed, message in queue 0x086bd7fffe3521ed|1'
[1/10/2021, 15:19:50] [ZigBee] Sent 1 messages for device TRADFRI control outlet
[1/10/2021, 15:19:50] [ZigBee] Reading 'state' from '0x680ae2fffe7d5012, message in queue 0x680ae2fffe7d5012|1'
[1/10/2021, 15:19:50] [ZigBee] Sent 1 messages for device TRADFRI control outlet
[1/10/2021, 15:19:51] [ZigBee] Reading 'state' from '0x680ae2fffe770c4f, message in queue 0x680ae2fffe770c4f|1'
[1/10/2021, 15:19:51] [ZigBee] Sent 1 messages for device TRADFRI control outlet
[1/10/2021, 15:19:51] [ZigBee] Zigbee message from 0x000d6ffffeff6164 readResponse

[1/10/2021, 15:20:11] [ZigBee] Reading 'state' to '0x086bd7fffe3521ed' failed: 'Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))'
[1/10/2021, 15:20:11] [ZigBee] Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:367:23)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)
[1/10/2021, 15:20:32] [ZigBee] Reading 'state' to '0x086bd7fffe3521ed' failed: 'Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))'
[1/10/2021, 15:20:32] [ZigBee] Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:367:23)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)
[1/10/2021, 15:20:52] [ZigBee] Reading 'state' to '0x086bd7fffe3521ed' failed: 'Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))'
[1/10/2021, 15:20:52] [ZigBee] Error: Read 0x086bd7fffe3521ed/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:367:23)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)

2 replies

madchicken Jan 10, 2021
Maintainer Author

Which device is 0x086bd7fffe3521ed? It seems to be offline. Errors you see are due to the fact that HomeKit is trying to read the state of the device (to show it in the Home App) but the device is not responding

EdwardChamberlain Jan 10, 2021

Which device is 0x086bd7fffe3521ed? It seems to be offline. Errors you see are due to the fact that HomeKit is trying to read the state of the device (to show it in the Home App) but the device is not responding

Ah yes, I have a socket which is powered off! Good catch!

manuchis · 2021-01-10T17:16:51Z

manuchis
Jan 10, 2021

Hi! I’m having issues installing it. It shows a permission error when installing serialport, even with “sudo su”. I don’t know why.

@***@***.*** install ***@***.***/bindings prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild

prebuild-install WARN install EACCES: permission denied, access '/root/.npm' gyp WARN EACCES current user ("nobody") does not have permission to access the dev dir "/root/.cache/node-gyp/12.19.0" gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/@serialport/bindings/.node-gyp" gyp WARN install got an error, rolling back install gyp WARN install got an error, rolling back install gyp ERR! configure error gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/@serialport/bindings/.node-gyp' gyp ERR! System Linux 5.4.51+ gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/@serialport/bindings gyp ERR! node -v v12.19.0 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok

1 reply

madchicken Jan 10, 2021
Maintainer Author

try adding --unsafe-perm to the npm install command

manuchis · 2021-01-10T18:04:00Z

manuchis
Jan 10, 2021

Excellent, everything looks good, no error so far.

0 replies

EdwardChamberlain · 2021-01-10T21:36:44Z

EdwardChamberlain
Jan 10, 2021

It may be worth considering adjusting the log levels of some information. This plugin can generate quite a large amount of logs even with debug mode off. For example toggling a socket (Another plugin, not Zigbee) this module generates the following logs while no other plugin generates a log. Perhaps some / all of these would be better as debug level logs. If you agree this is something I could potentially take a look at implementing.

[1/10/2021, 21:34:07] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:07] [ZigBee] Reporting state for 0x000d6ffffeff6164: ON (true)
[1/10/2021, 21:34:07] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:07] [ZigBee] Reporting state for 0x086bd7fffe519524: ON (true)
[1/10/2021, 21:34:07] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:07] [ZigBee] Reporting state for 0x680ae2fffe7d5012: ON (true)
[1/10/2021, 21:34:07] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:07] [ZigBee] Reporting state for 0x680ae2fffe770c4f: ON (true)
[1/10/2021, 21:34:10] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:10] [ZigBee] Reporting state for 0x000d6ffffeff6164: ON (true)
[1/10/2021, 21:34:10] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:10] [ZigBee] Reporting state for 0x086bd7fffe519524: ON (true)
[1/10/2021, 21:34:11] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:11] [ZigBee] Reporting state for 0x680ae2fffe7d5012: ON (true)
[1/10/2021, 21:34:11] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:11] [ZigBee] Reporting state for 0x680ae2fffe770c4f: ON (true)
Rejecting unresolved promise after 5291ms ("0x086bd7fffe3521ed|1")
[1/10/2021, 21:34:12] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:12] [ZigBee] Reporting state for 0x000d6ffffeff6164: ON (true)
[1/10/2021, 21:34:12] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:12] [ZigBee] Reporting state for 0x086bd7fffe519524: ON (true)
[1/10/2021, 21:34:13] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:13] [ZigBee] Reporting state for 0x680ae2fffe7d5012: ON (true)
[1/10/2021, 21:34:13] [ZigBee] Device state (TRADFRI control outlet):  { state: 'ON' }
[1/10/2021, 21:34:13] [ZigBee] Reporting state for 0x680ae2fffe770c4f: ON (true)
Rejecting unresolved promise after 6640ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 9586ms ("0x086bd7fffe3521ed|1”)

2 replies

madchicken Jan 11, 2021
Maintainer Author

True. I'll do a pass in the code looking for important thins to be logged. I'll move the rest to debug level

maccoylton Jan 11, 2021

Can you also add a write of a version number to the log, makes it easy to know for sure you are running the intended version

I installed per instruction above, so far my Sonoff SNZB-04/eWelink DS01 is working fine with no issue

madchicken · 2021-01-19T11:18:32Z

madchicken
Jan 19, 2021
Maintainer Author

Version 2 is now out! Try it please!

5 replies

lucaskoehler Jan 19, 2021

So far everything seems to be working fine for me.
No problems while pairing all devices again.
I am not sure anymore if there was a warning in the release notes of v2.0 telling that all paired devices get lost after the update?! I think this would be an important information.

Do you already have plans for future updates?
Keep up the good work! 💪🏼

EdwardChamberlain Jan 19, 2021

Is losing devices across the update expected behaviour? Im on v2.0.0-unstable.1 now and didn’t see loss of devices going from v1.X

madchicken Jan 19, 2021
Maintainer Author

The Problem is related to a major change happened in the herdsman lib: with the latest version they changed the allowed panId default value (it was 0xFFFF, now that value is not allowed anymore) and it seems that is causing issues with the ZigBee antenna :(
I introduced an automatic backup of the zigbee database every time you restart homebridge (will need to work more and limit the number of backup retained). You can find them in /var/lib/homebridge folder

madchicken Jan 19, 2021
Maintainer Author

Oh, it seems now it accept a new 'GENERATE' value for the pan ID. Please, wait a new version, I'll add it as default like now. It should fix the problem (maybe)

Koenkk/zigbee2mqtt#5745

madchicken Jan 19, 2021
Maintainer Author

Sorry, I was wrong. Generating a random panId would not solve the problem, since it will be different from the previous one. I think there is no solution about this.

manuchis · 2021-01-19T13:13:25Z

manuchis
Jan 19, 2021

I’m also in 2.0.0-unstable and didn’t loss the devices. The question is if the loss is in the v2 or is it because you have an old version. I think in some point there were changes on zigbee database.

1 reply

madchicken Jan 19, 2021
Maintainer Author

Please, see my response above #73 (reply in thread)

madchicken · 2021-01-19T16:39:46Z

madchicken
Jan 19, 2021
Maintainer Author

Thanks to @tr1ng0 we now have a discord server to use as internal chat https://discord.gg/bDgUzDdt
Adding it to the readme soon

0 replies

EdwardChamberlain · 2021-01-25T21:52:13Z

EdwardChamberlain
Jan 25, 2021

Im seeing some odd behaviour on v2.0.0-unstable.1

My lights will turn themselves on and off randomly. It happens about once a day. It may not be a plugin issue - in which case I need to check my setup - but I have only noticed it since updating.

Im sorry that this doesn't have any more info that might be helpful for debugging!

12 replies

madchicken Jan 28, 2021
Maintainer Author

It doesn't @EdwardChamberlain. You can safely update.

EdwardChamberlain Jan 28, 2021

It doesn't @EdwardChamberlain. You can safely update.

I can confirm that completing this update has caused all accessories to be forgotten and require re-pairing.

EdwardChamberlain Jan 28, 2021

That was v2.0.0-unstable.1 to v2.0.2-unstable-10

tr1ng0 Jan 28, 2021
Collaborator

@EdwardChamberlain weird ... I had no issue upgrading

EdwardChamberlain Jan 28, 2021

@EdwardChamberlain weird ... I had no issue upgrading

Seems like a couple of restarts later and the main issues have gone away - I had to repair my sockets but it was able to find my motion sensors and switches on its own. Odd! I will leave one socket unpaired and see if it can find it overnight.

EdwardChamberlain · 2021-01-28T20:38:11Z

EdwardChamberlain
Jan 28, 2021

Picking up a number of errors and poor performance on v2.0.2-unstable-10

-1000-8000-0026BB765291. Adding anyway.
HAP Warning: Characteristic 0000007A-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000047-0000-1000-8000-0026BB765291. Adding anyway.
HAP Warning: Characteristic 000000D2-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000047-0000-1000-8000-0026BB765291. Adding anyway.
[1/28/2021, 20:35:13] [ZigBee] Device TRADFRI control outlet is a router, install ping
[1/28/2021, 20:35:14] [ZigBee] Device TRADFRI control outlet successfully configured on attempt 1!
[1/28/2021, 20:35:29] [ZigBee] Device TRADFRI control outlet is a router, install ping
[1/28/2021, 20:35:29] [ZigBee] Device TRADFRI control outlet is a router, install ping
[1/28/2021, 20:36:42] [ZigBee] Accepting joining whitelisted device '0xbc33acfffeab43b4'
[1/28/2021, 20:36:42] [ZigBee] Interview progress started for device 0xbc33acfffeab43b4
Rejecting unresolved promise after 12497ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 12489ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 12483ms ("0x680ae2fffe770c4f|1")
[1/28/2021, 20:36:53] [ZigBee] Accepting joining whitelisted device '0xbc33acfffeab43b4'
(node:657) UnhandledPromiseRejectionWarning: Error: Bind 0xbc33acfffe8924ad/1 genOnOff from '901' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/utils/waitress.ts:70:35)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
(node:657) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:657) [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.
[1/28/2021, 20:37:07] [ZigBee] Accepting joining whitelisted device '0xbc33acfffeab43b4'
Rejecting unresolved promise after 14706ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 14701ms ("0x680ae2fffe770c4f|1")
Rejecting unresolved promise after 11199ms ("0x086bd7fffe3521ed|1")
Rejecting unresolved promise after 11195ms ("0x680ae2fffe7d5012|1")
Rejecting unresolved promise after 11191ms ("0x680ae2fffe770c4f|1")
[1/28/2021, 20:37:20] [ZigBee] Accepting joining whitelisted device ‘0xbc33acfffeab43b4’

[1/28/2021, 20:37:33] [ZigBee] Can't find message in queue for key 0x680ae2fffe7d5012|1 [
  {
    timestamp: 1611866248593,
    message: '0x680ae2fffe770c4f|1',
    promise: DeferredPromise {
      resolve: [Function],
      reject: [Function],
      promise: [Promise]
    }
  }
]

HAP Warning: Characteristic 00000079-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000047-0000-1000-8000-0026BB765291. Adding anyway.
HAP Warning: Characteristic 0000007A-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000047-0000-1000-8000-0026BB765291. Adding anyway.
HAP Warning: Characteristic 000000D2-0000-1000-8000-0026BB765291 not in required or optional characteristics for service 00000047-0000-1000-8000-0026BB765291. Adding anyway.

0 replies

EdwardChamberlain · 2021-01-29T07:58:35Z

EdwardChamberlain
Jan 29, 2021

On v2.0.2-unstable-10: TRADFRI ON/OFF switch has lost the long-press functionality. This is still presented in the switch page on the home app but doesn't seem to function (no logs in homebridge)

0 replies

manuchis · 2021-01-31T14:16:44Z

manuchis
Jan 31, 2021

Well, updated to 2.0.3 stable from 2.0.0-unestable and lost all the devices again 🤦‍♂️ Manuel Portela, PhD Cel Es. +34 600 851 104 Follow me: @Portela_Man manuchis.net El 29 ene 2021 8:58 +0100, Edward Chamberlain <notifications@github.com>, escribió:

…

On v2.0.2-unstable-10: TRADFRI ON/OFF switch has lost the long-press functionality. This is still presented in the switch page on the home app but doesn't seem to function (no logs in homebridge) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

0 replies

Version 2.0.0: Test help needed! #73

madchicken Jan 10, 2021 Maintainer

Replies: 14 comments · 25 replies

madchicken Jan 10, 2021 Maintainer Author

madchicken Jan 10, 2021 Maintainer Author

madchicken Jan 10, 2021 Maintainer Author

madchicken Jan 10, 2021 Maintainer Author

madchicken Jan 11, 2021 Maintainer Author

madchicken Jan 19, 2021 Maintainer Author

madchicken Jan 19, 2021 Maintainer Author

madchicken Jan 19, 2021 Maintainer Author

madchicken Jan 19, 2021 Maintainer Author

madchicken Jan 19, 2021 Maintainer Author

madchicken Jan 19, 2021 Maintainer Author

madchicken Jan 28, 2021 Maintainer Author

tr1ng0 Jan 28, 2021 Collaborator

madchicken
Jan 10, 2021
Maintainer

Replies: 14 comments 25 replies

madchicken Jan 10, 2021
Maintainer Author

madchicken Jan 10, 2021
Maintainer Author

madchicken Jan 10, 2021
Maintainer Author

madchicken Jan 10, 2021
Maintainer Author

madchicken Jan 11, 2021
Maintainer Author

madchicken
Jan 19, 2021
Maintainer Author

madchicken Jan 19, 2021
Maintainer Author

madchicken Jan 19, 2021
Maintainer Author

madchicken Jan 19, 2021
Maintainer Author

madchicken Jan 19, 2021
Maintainer Author

madchicken
Jan 19, 2021
Maintainer Author

madchicken Jan 28, 2021
Maintainer Author

tr1ng0 Jan 28, 2021
Collaborator