Nortek z-stick not working #10178
Comments
|
Hi, That sounds like.. 1 - Something else is already using the Z-stick (ZHA perhaps) - I presume you tried a reboot. Simon. |
|
It still no work `[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
|
|
What port have you put in the configuration for the USB stick? It looks like Z2M can't find it. Go into supervisor then click system at the top and in the bottom corner of the host box is 3 small dots, If you click that, then hardware, it will list all your hardware, Scroll down untill you find your z-stick (usually ttyACM or ttyUSB), copy what is under that and put that in your configuration. Mine looks like this (yours wont be the same as we have different sticks.
I then enter the below in my configuration:
Si |
|
This stick is not supported by zigbee2mqtt: https://www.zigbee2mqtt.io/guide/adapters/#recommended |
|
Well that would explain it then. Si |
|
If updating its firmware it shall being possible running in EZSP V8 mode. |
|
I've updated my firmware on the HUSBZB-1 stick with walthowd's guide. I'm now at version 6.7.8 using the ezsp adapter setting in Z2M. It works for me, half the time. I'm using hassos inside vbox on a Windows 10 pc. It didn't work before I updated it, so flashing the stick helped. I can get it to pair with an Aqara water leak sensor after a few attempts. Everything reads and gets sent into HA as it should. Only thing is, I have to re-pair it every few days so I set up a link quality automation to alert me when it drops to "None". What logs would you need to see to find out what's happening? I don't get any errors in Z2M, and with herdsman debug on. It just all of a sudden stops reporting, all the while sending "Assertion Failed" I think every hour, regardless if the sensor reported. |
Thank you, |
|
Follow this guide https://github.com/walthowd/husbzb-firmware |
|
Thanks for your help but when i try to use the docker thing i get a "docker: Error response from daemon: error gathering device information while adding custom device "/dev/ttyUSB0": no such file or directory." error and i thought its in the wrong port but i realized that the usb is just off, and when i unplug it and plug it back it back in it goes on then turns back off. What should i do? |
|
Bruh i just installed docker and how Vurtual box is giving me this Result Code: |
If you're on Windows, you'll need to disable power saving for the two devices under "device management" |
|
I installed a fresh Ubuntu OS and used docker on that and it worked perfectly |
|
FYI, EZSP support is in a very experimental phase so you should really post your feedback here -> Koenkk/zigbee-herdsman#319 I am not even not sure if any developer(s) is currently actively working on improving or maintaining that experimental support(?). Only clear tips is to upgrade Zigbee EmberZNet NCP UART EZSP firmware version 6.7.9 or later and use dev branch (a.k.a. Edge): https://github.com/arendst/Tasmota/tree/development/tools/fw_SonoffZigbeeBridge_ezsp https://github.com/Koenkk/zigbee2mqtt/tree/dev There are some ezsp related fixes in the zigbee-herdsman dependency that might have not yet made it into Z2M dev/edge yet: https://github.com/Koenkk/zigbee-herdsman/ Regardless you still want to direct most if not all feedback/issues to subscribers of the WIP discussion in the zigbee-herdsman repo: Also, before buying any newer Silicon Labs based Zigbee Coordinator adpaters please take an extra note that WiFi based Zigbee bridges like ITead Sonoff ZBBridge are generally not recommended with the Silabs EZSP protocol. See the warnings about it: https://www.zigbee2mqtt.io/guide/adapters/#notes WiFi-based Serial-to-IP bridges are not recommended for Silicon Labs EZSP adapters as the serial protocol does not have enough fault-tolerance to handle packet loss or latency delays that can normally occur over WiFi connections. If cannot use a locally connected USB or UART/GPIO adapter then the recommendation is to use remote adapter that connected via Ethernet (wired) to avoid issues with EZSP caused by WiFi connections. https://www.zigbee2mqtt.io/advanced/remote-adapter/connect_to_a_remote_adapter.html WiFi-based Serial-to-IP bridges are not recommended for Silicon Labs EZSP adapters as the serial protocol does not have enough fault-tolerance to handle packet loss or latency delays that can normally occur over WiFi connections. More warning about Zigbee to WiFi bridges for EZSP is not recommended for production as it does not do well with packed loss: https://github.com/zigpy/bellows#warning-about-zigbee-to-wifi-bridges FYI, I also understand that the EFR32 board antenna design of the "SM-011 V1.0" Zigbee module used inside ITead's Sonoff ZBBridge have very high receive sensitivity to electromagnetic interference (EMI) / radio-frequency interference. This means that it will be extra important to keep it away from any other electronic devices or appliances that may generate an electromagnetic field (EM Field) or send our interfering radio signals. That includes the computer that you run your home automation application software on as well as any devices such as for example external harddrives or storage devices, power-supplies, etc., and of course any Wi-Fi access points or routers nearby. Note! The new ITead Zigbee 3.0 USB Dongle Model: 9888010100045 (Hardware Revision Version 1.3) circuit board share the same type of antenna design so its radio is as well extremely sensitive to signal interference on its receiving end. The current recommendation for using it is to connect it via a long USB extension cable and try to move it as far away from all electronics and other possible sources of signal interference. PS: Another general tip that always applies when building a Zigbee network is to begin by adding a few good mains-powered Zigbee router devices so that they will make use a stable baseline. Many start by buying three "IKEA TRADFRI Signal Repeater" (E1746). https://zigbee.blakadder.com/Ikea_E1746.html https://www.ikea.com/us/en/p/tradfri-signal-repeater-30400407/ https://www.ikea.com/gb/en/p/tradfri-signal-repeater-80424255/ https://www.ikea.com/se/sv/p/tradfri-signalfoerstaerkare-10400408/ |
|
Hey thanks for your help and sorry i have been offline for a while |
I mean its worth a try |
|
By the way, strongly recommend that you at least try upgrading HUSBZB-1 to the very latest Silabs EmberZNet 6.7.10.x firmware made available by the community, see here -> grobasoz/zigbee-firmware#17 and also here -> walthowd/husbzb-firmware#36 And of course, also make sure to always use latest "dev" branch (a.k.a. 'edge' version) of Zigbee2MQTT for experimental features. Note that with grobasoz EmberZNet 6.7.10.0 / EmberZNet 6.7.10.x firmware uses 115200 as its default baud rate for the serial port. Understand that Silicon Labs EM35x and ETRX35x Zigbee chip hardware used in Nortek HUSBZB-1 have already been end-of-life for a while and should now almost be considered obsolete as Silabs have started that they are deprecated in firmware newer than EmberZNet 6.7.10.x There may come a few updates bug-fix releases for EmberZNet 6.7.10.x but otherwise it will not get any new features or functions. PS: Before buying a newer adapter know that even some of the specific models Silicon Labs EFR32 Mighty Gecko Series 1 modules (i.e. EFR32MG1x e.g. EFR32MG12/EFR32MG13/EFR32MG14) based chip which does not feature enough flash storage size to fit firmware built with the newly released EmberZNet 7.0.0.0 Zigbee release have also reached the end of their planned lifecycle and been scheduled for obsolescence and discontinued by the manufacturer (Silicon Labs). So only Silicon Labs EFR32 Mighty Gecko Series 2 (i.e. EFR32MG2x e.g. EFR32MG21/EFR32MG23/EFR32MG24) and some of the Silicon Labs EFR32 Mighty Gecko Series 1 module model variants which feature more flash storage size is be supported by EmberZNet 7.0 Zigbee. |
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
|
@DJAMIRSAM It is indeed worth a try because some of us have been able to get the nortek z-stick working using the updated firmware mentioned in this issue, and some sample configurations posted in #8026 |
|
Since the EZSP support is still experimental recommend trying to keep discussions to that issue-> Koenkk/zigbee-herdsman#319 |
What happened
when i press the open in WebUI button i get a 502 Bad Gateway error
and a error on logs
Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
i also get this error in HA logs
21-11-02 21:33:29 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.4:8099 ssl:default [Connect call failed ('172.30.33.4', 8099)]
its trying to connect to 172.30.33.4 except my IP range is 192.168.1.XXX
What did you expect to happen
what open a ui
How to reproduce it (minimal and precise)
install the plugin
Debug info
Zigbee2MQTT version: 1.18.1-1
Adapter hardware: Norteck z-stick
Adapter firmware version: Dont Know
Please Help
The text was updated successfully, but these errors were encountered: