Turn off gold DDF support and your aqara sensors will start working again. Wonder who gave these sensors gold support, anyway? They clearly dont work with DDF
Then there is nothing I can do, its an issue on deCONZ side and I’ve pointed it out to the devs.
1 Like
thx.
Another question: Is this the right thread to post questions about the deconz addon?
Ill give that a try!
Hi, that might not be the only reason.
I have xiaomi/aquara motion/water and temperature sensors and DDF Gold activated.
No issues so far. I’m even not sure, when to activate hybrid or later strict.
PS: I like to understand a little more about these options. Since version 6.13.x i notice the phenomen, that out of nothing the processor use of deconz raises from near 0 up to 10% and after a while, everythings calm down. When I do nothing, the frequency of this behavior increases and the value of cpu use as well. As soon as I restart deconz, I have no issues for a few days before it happens again.
Can this have something to do with the Gold option? As I thought about what @stigvi wrote and noticed, that I had activated this option I was unsure if this could have caused the issue. Can somebody tell a little more about that? I did not find something via google which could bring light into the darkness…
Been running now for 6 days without any of my aqara devices that where unavailable coming back. So for me, having no checkbox for bronze, silver and gold did not make any difference than having gold checked. I have not re-added any of the devices yet
OK. I did not wait long enough to lost my sensors, but noticed that they didn’t report any longer. I then unchecked gold support and saw that they started to report values.
Are you running the latest version of your Conbee device?
On the changelog for 6.14.2, S6 V3 is mentioned. What is S6 V3?
This is a fresh install of HA. I installed the Deconz Add-On which let me access Phoscon and Deconz fine. Then I installed the Deconz integration using the IP address from Phoscon and port 40850. Here’s where the issues start, though:
- Deconz returns a bridgeId of 0000000000000000. It’s always been a string of numbers and letters before. It still is when I set it up on my desktop.
- Phoscon and Deconz state that the device is a Raspbee. It’s a Conbee 2. On my desktop it identifies as a Conbee2.
- Phoscon states that the firmware version is “Not connected” (even after I manually updated it to version 26780700)
- Scanning for devices in Phoscon no longer seems to turn up any devices, even when my bulbs, dimmers and switches are put in pairing mode.
- When adding the Deconz integration, it now no longer just adds the single Conbee2 device, it also adds a second device titled “Unknown device” with manufacturer and model being “Unknown”.
- Where I used to have my conbee configured to use something like /dev/manufacturer/dresden-electronics/deconz-longstringofnumbersandletters now the only config option is to use /dev/ttyAMA0
Is my Conbee 2/pi4 dead?
Should I have used a different port (80 and 8080 failed to get an API key)?
Is this something that can be fixed with a config change?
Any advice appreciated!
If you have a Conbee the device will be called ttyACM0 (or ttyACM1 if you already have some other USB serial). It is only the Raspbee that is called ttyAMA0.
Weird, because it definitely is a Conbee. It even identifies as a Conbee when I plug it into my desktop, although it never seems to connect. It’s only when I plug it into my Raspberry Pi with HA that it identifies as a Raspbee. 
On my desktop:
Your first problem to solve is to get the Conbee II detected as a serial USB device. And its name will be ttyACM0 or 1 or 2 if you already have ttyACM devices. All the other steps are pointless. As long as the deconz software cannot talk to the stick nothing else will work.
Thanks for the reply Kenneth!
Currently under settings > system > hardware > all hardware it shows up under:
Subsystem: tty
Device path: `/dev/ttyAMA0`
Attributes:
DEVLINKS: /dev/serial1 DEVNAME: /dev/ttyAMA0 DEVPATH: /devices/platform/soc/fe201000.serial/tty/ttyAMA0 MAJOR: '204' MINOR: '64' SUBSYSTEM: tty TAGS: ':systemd:' USEC_INITIALIZED: '4192715'
Which, to my untrained eye, looks like it’s showing up as a serial USB device? I’m just not quite sure what to look for next to troubleshoot, or how to test if it’s an actual hardware failure.
And you can see this device show up when you plug the Conbee2 abd disappear when you disconnect it? I think this is a different device
I think you may be right. I pulled out the Conbee, restarted HA and /dev/ttyAMA0 is still there. Strange thing is, I have nothing plugged into my pi other than the power and an ethernet cable going to the router.
When I plug the conbee in, nothing else shows up in hardware > all hardware except gpiochip0 and 1 and a mouse (weird as I don’t have a mouse plugged in )
Plugging the Conbee into my Linux desktop, deCONZ recognizes it, but seems to hang on trying to connect to it. There are no error messages in the console except an irrelevant looking one “libpng warning: iCCP: known incorrect sRGB profile”.
Hello all!
Another month comes with another release log on Phoscon forum for the HA deCONZ integration
As the beta has been cut I wanted to share what will be released with Home Assistant 2022.7.0
The Integration is starting to shape up and I look forward to start adding new functionality in a few releases which benefit this improved architecture. This rework has been ongoing since the later parts of November.
Two things I’d like feedback on from this beta run
- Verify controls for climate, lock, scenes and switches still work as expected
- Binary sensors are still created properly and without duplicates (I’m reworking how unique IDs are generated). This is needed in order to start moving attributes out to their own entities.
- Normalize generation of binary sensor unique IDs ← 2
- Use interface controls in Climate platform ← 1
- Use interface controls in Lock, Scene, Siren and Switch platforms ← 1
- Use more enums in Alarm Control Panel platform
- Fix group regression
- Remove repetitive steps related to groups in platform setup
The pydeconz library benefit from changing to utilizing orjson library. It will parse json faster than the stock json module.
Try the beta out and report any bugs you experience!
/R
1 Like
what is the most efficient way to change channel on the Zigbee network. Without having to re pair devices? (I have changed channel in phoscon a few times lately due to signal interference - error message 0xE1. But I usually have to re pair a few of the devices each time)
Hmmm… I’m starting to think there may be a hardware error with my Pi’s USB. I borrowed a Sonoff Zigbee 3 USB dongle, and that also doesn’t seem to be detected, just like the Conbee 2.
@Robban Am I understanding correctly that in the future we will not get three enitities for a multi sensor (ie. temp, humidity, pressure) but instead one entity with the measurements as attributes?
If so, yay! I’ve been thinking of how to improve naming from Phoscon to HA.