Not sure how to word this…Ive just rebuilt my HA (Proxmox VM) - ive got the conbee setup and working…it did an initial discovery of devices but theres a bunch of them that are in the DeConz window but havent transferred over to HA…ie i can see 20 odd dimmers and lights in DeConz but only 4 or 5 in the HA…is there a way to force them over?
Cheers
Not quite clear what you mean with discovery - You have all the devices online and working in Deconz, but only a few of them show up through the integration? I see you previously have experimented with Z2M and ZHA, did you re-pair all the devices through Deconz?
Hi there. Well, as i say i might not be explaining myself correctly…when i say discovery…when i completed the deconz setup the adapter started to find devices and they appeared in the Deconz window - right now there are 19 lights and 27 sockets in deconz so thats 46 devices…the deconz integration in HA is showing 35 devices…so how to i get the missing ones in?
There is no way to “force” devices over. It should present every device as long as it’s paired correctly. I haven’t used Deconz in years, but I would try deleting the integration, reboot and then add it again.
Whats your weapon of choice then!? what do you prefer to use (if you say zigbee2mqtt) im knackered - already disappeared down that rabbit hole with no return!!
I use Zigbee2MQTT 
Lol - im screwed! - i did just try the ZHA integration (connecting to the Sonoff) but that also fails at the port speed point - just says “an error has occurred” i even flashed the latest firmware to it also (july last year i think was the date time)
Well - too pot luc and tried zigbee2mqtt - this is in the log…
| [2025-01-07 10:11:11] info: | z2m: Logging to console, file (filename: log.log) |
|---|---|
| [2025-01-07 10:11:11] info: | z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown) |
| [2025-01-07 10:11:11] info: | z2m: Starting zigbee-herdsman (3.2.1) |
| [2025-01-07 10:11:11] info: | zh:ember: Using default stack config. |
| [2025-01-07 10:11:11] info: | zh:ember: ======== Ember Adapter Starting ======== |
| [2025-01-07 10:11:11] info: | zh:ember:ezsp: ======== EZSP starting ======== |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: ======== ASH Adapter reset ======== |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control. |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: ASH COUNTERS since last clear: |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Total frames: RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Cancelled : RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: DATA frames : RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: DATA bytes : RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Retry frames: RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: ACK frames : RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: NAK frames : RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: nRdy frames : RX=0, TX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: CRC errors : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Comm errors : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Length < minimum: RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Length > maximum: RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Bad controls : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Bad lengths : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Bad ACK numbers : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Out of buffers : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Retry dupes : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: Out of sequence : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: ACK timeouts : RX=0 |
| [2025-01-07 10:11:11] info: | zh:ember:uart:ash: ======== ASH stopped ======== |
| [2025-01-07 10:11:11] error: | zh:ember:uart:ash: Failed to init port with error Error: Error Resource temporarily unavailable Cannot lock port |
| [2025-01-07 10:11:11] error: | z2m: Error while starting zigbee-herdsman |
| [2025-01-07 10:11:11] error: | z2m: Failed to start zigbee-herdsman |
| [2025-01-07 10:11:11] error: | z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions |
| [2025-01-07 10:11:11] error: | z2m: Exiting… |
| [2025-01-07 10:11:11] error: | z2m: Error: Failed to start EZSP layer with |
This is my serial config…
port: /dev/ttyUSB0
adapter: ember
This is how ive got the yaml config set… with the new updated additon to the script in there also…
version: 4
homeassistant:
enabled: true
advanced:
homeassistant_legacy_entity_attributes: false
homeassistant_legacy_triggers: false
legacy_api: false
legacy_availability_payload: false
device_options:
legacy: false
network_key:
- 87
- 141
- 202
- 113
- 105
- 191
- 254
- 18
- 113
- 174
- 69
- 50
- 69
- 173
- 166
- 198
pan_id: 31212
ext_pan_id:
- 42
- 176
- 233
- 173
- 122
- 138
- 186
- 204
mqtt:
server: mqtt://core-mosquitto:1883
user: addons
password: juquoh9aichoo9noosh0fioXoorise8asaowit9och7mooteibaesoquohoroo7o
frontend:
enabled: true
port: 8099
apologies - digressing now as this was a conbee question! - getting desparate.!
Figure out what you want to use and take it from there. It’s difficult to help you with a Deconz problem when you suddenly start mixing in Z2M.
What would you say is better Conbee or Sonoff?
It’s been years since I’ve used a Conbee and I’ve never used a Sonoff so I couldn’t tell you. Which of the two you use really shouldn’t matter too much unless you have coverage issues or a big, complex network. If you have both I’d probably try the Sonoff, seems a lot of people are using it. I use the SLZB-06p7 my self.
Wow - never heard of those before…whats that like to the sonoff…i have just ordered one of those SyConnect sticks… nothing more than a punt to see how it works (and if its less hassle than the sonoff)!