Have you tried to connect the stick directly with the USB extension cable to the USB port of the NUC leaving out that USB 2-hub?
It is not that those Zigbee-sticks are incompatible with USB 3 per-se. The problem is with the USB 3 signalling which causes high interference especially around 2.4GHz near those USB 3 ports in use. Just make sure the stick is put as far away from the NUC as possible.
the hub will arrive tomorrow/monday, so I just using the usb extension I was using with Conbee (removed Conbvee stick, put Sonoff stick).
Beside intereference (will check that later) , I do not have the stick recognizes in HA
Well, then wait for the USB 2-hub to arrive and try again.
Unfortunately I have no experience with Proxmox since all HA devices I maintain are on miniPCs and RPIs using HA Supervised.
why, that adds on complication!! It can’t be an interference issue, we are talking of basic installation, the stick is not seen, can’t be an interference, that is something else.
Which is the vendor ID of Sonoff?
The port was working with COnbee so its not a proxmox issue either
ID_VENDOR: ITead
ID_VENDOR_ENC: ITead
ID_VENDOR_FROM_DATABASE: Silicon Labs
ID_VENDOR_ID: 10c4
Here:
Bus 001 Device 003: ID 10c4:ea60
Just a shot in the dark, have you removed the Deconz software and rebooted the host before pluging-in the Sonoff Zigbee dongle?
I stopped the deconz addon and rebooted.
EDIT, does it come flashed? MAybe I need to flash firmwarte first???
EDIT2: I reflased the firmware with TI tool.,l and all went well (success on the flash tool, under window). But problem persist, the stick is not seen by my HA machine …
EDIT3: a reboot witrhout stick, then insert stick, shutdown, reboot machine, now it recognized it … very very strtange
Other problem
Zigbee2MQTT:info 2022-11-12 17:52:57: Connecting to MQTT server at mqtt://core-mosquitto
Zigbee2MQTT:error 2022-11-12 17:52:57: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2022-11-12 17:52:57: MQTT failed to connect, exiting...
Zigbee2MQTT:info 2022-11-12 17:52:57: Stopping zigbee-herdsman...
Zigbee2MQTT:error 2022-11-12 17:52:58: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2022-11-12 17:52:59: MQTT error: Connection refused: Not authorized
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
mqtt:
server: mqtt://core-mosquitto
username: username
password: xxx
serial:
port: /dev/ttyUSB0
and YES my username and password are correct
but still get the error???
EDIT, its user not username
I have a Sonoff Dongle on a nuc working fine (without extension cable) with z2mqtt.
But wifi is disabled on the nuc. Never had a problem.
This is my mqtt conf at z2mqtt.
Maybe you are missing :1883
server: mqtt://192.168.0.28:1883
user: blahblah
password: blehbleh
no, its user instead of username, but thanks, now all works fine.
When some devices are not working perfectly (and in meantime I added more AC connected devices), what do I have to do? Press RECONFIGURE on the troubled device, or ?
Please try not to go too much off-topic, Zigbee2MQTT specific questions are better asked in their discussions at https://github.com/Koenkk/zigbee2mqtt/discussions and Z2M specific problems/bugs to https://github.com/Koenkk/zigbee2mqtt/issues/ …or just start a new thread if the question is not directly related to this dongle.
Hi!
Could you please help on on that…
I bought a ZBDongle-P several months ago to replace my previous BitronVideo dongle. The new device worked fine from the start, I flashed with newer and newer FW-s more times, currently with the latest Koenk FW…
"manufacturer": "Texas Instruments",
"model": "CC1352/CC2652, Z-Stack 3.30+ (build 20220219)",
"class": "zigpy_znp.zigbee.device.ZNPCoordinator"
…it also works without any problems.
I just have one question what I definitely remember that saw somewhere before but now I can not find it.
From the start of its usage I always had/have 2 devices/entities as coordinator. One ZNP based and one unknown. The Zigbee mesh/network shows me that my Zigbee devices connected to the ZNP based controller/gateway but in this case what is the other? Do I need it at all? Could it be just an older bug related result, which currently is just a garbage? I have no problem with the whole setup, but sometimes I like to do some polish/sophisticate my settings, and ‘now’ I have catched this point.
The ZNP one:
And the other one:
Sorry if I’m redundant, I tried to search it everywhere but simply can not find now, but as I wrote I definitely remember that I saw somewhere before from other persons also.
Lot of thanks for any advice in advance!
That “unknown” Zigbee Coordinator that you see will surely be garbage left over from your old Zigbee Coordinator adapter. At least it should not be there. Must be a bug in ZHA integration so post new issue to → https://github.com/home-assistant/core/issues (it looks like a similar issue is posted here → https://github.com/home-assistant/core/issues/46258)
@Hedda thanks for the answer!
I have found one not same, but also interesting situation which also answered by you…
…so I could imagine two things:
I’m sure that I had deleted my old controller before I added the new one. I’m also sure that I tried it more times, as I remember that never understood why I have 2 controller right after ZHA initialization. But as this never lead me to any error I left it.
/dev/tty path. But later as I saw lot of suggestions about not to use them through such way but use them through their discrete device IDs, I changed my device attachments also.Maybe all these 3 reasons could lead me the mentioned situation.
Because your answer I have deleted the unknown device, restarted HA, and still seems everything fine, and the deleted device have not re-appeared yet.
But I also show you an interesting thing:
$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 7825:a2a4 Other World Computing External SATA Hard Drive Adapter cable PA023U3
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 nov 15 13:09 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 nov 15 13:09 /dev/ttyUSB1
$ ls /dev/serial/by-id/
usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_88a22df07c29ec119cf76d7840c9ce8d-if00-port0
usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_745441651e94eb119abd32703d98b6d1-if00-port0
There are 2 very same devices while I have really 2 but different USB dongles on the corresponding RPi4:
Both of them show the same device ID, name, etc, however they are really 2 discrete and different devices.
Could this be the reason of the earlier problem? Could the 2 device made some collision like result? They worked always, paralelly, but with the mentioned ‘superficial problem’. This is basically the 3. theory in my list above.
Thanks for your answer, in advance!
Well, I think the semantics is explained poorly there. While I guess it sort is true that their ZBDongle-E is technically “supported” from Itead/Sonoff point-of-view as a company as it works and should be usable for most people, but it is a fact that Zigbee2MQTT still does not list the ZBDongle-E as recommended and so far only list it as “experimental”.
So the user experience at this time is likely not to be as good as someone using the ZBDongle-P instead, for the reasons that Zigbee2MQTT codebase does not yet offer feature parity for all Zigbee Coordinator and Zigbee stacks chips from different manufacturers. At least the function for restoring the backup image is missing for Silicon Labs EmberZNet EZSP based adapters (and the Zigbee2MQTT codebase lacks some development regression tests in its ezsp adapter code), as well as stability in Zigbee2MQTT with Silicon Labs EmberZNet EZSP based adapters is not quite as stable as a Texas Instruments ZStack 3 ZNP based adapter due to not being as mature. See these three links for reference:
Hey everyone. It’s my frist post here. I’ve just buy ZBDongle-E - i fucked up? There is some new firmware? My HA discover the dongle and i try to integrate sonoff and zigbee tuya curtain module. I think that i’ve got bad range and i don’t know how to get better of that.
To sum up…
You posted in the wrong thread then, instead see this other thread which covers the ZBDongle-E model and many questions related to it → ITead’s “Sonoff Zigbee 3.0 USB Dongle Plus V2” (model "ZBDongle-E") based on Silicon Labs EFR32MG21 +20dBm radio SoC/MCU
Read and follow guidelines in this other thread → Zigbee networks: how to guide for avoiding interference and optimize for getting better range + coverage
I noticed there is a new firmware v20221226. I can’t remember, will updating the firmware wipe all paired devices?
Didn’t for me. Just updated and all is still working. I used the method without opening the case
