I am running my ConBee2 on Rpi4
Version 2.13.02 / 10.11.2021
At the moment there is only one Xiaomi water leakage sensor connected to my gateway. No other devices. The update to the current beta version was made yesterday, because with the last stable version I was not able to find my new MCCGQ14LM sensor.
I have 10 sensors of type MCCGQ14LM (just arrived) , and after updating deCONZ I found and connected the first one. After connecting the sensor it was working, but the Value in PhosconApp was “0,open / 0,closed” it seemed to be a mixtue of state and temperature. Beside that, open/close action was shown instantly when I moved the magnet.
To fix the problem with the displayed state, I removed it and connected it again. Values are now displayed correct. When I connect the sensor in an open state, it is now shown as “open”.
But when I close the contact, state is not updated anymore. As soon as I push the connect button, the correct state is displayed.
I connected a second sensor, but the problem is the same. That state never gets updated.
Is there anything that I can provide to solve that problem?
I read this post. https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5403
It seems that McCormick has the same issue.
Do you have some logs(check the deCONZ category for a how-to) and a screen of you deconz gui?
Gui is not running on my Pi.
Log will be provided later when I am back home.
Would be useful to have that
I also have some other Aqara OpenClose sensors and the sensor JSON seems to differ somewhat.
"name": "Sensor - OpenClose - Kitchen",
And then this new one:
"name": "OpenClose 55",
Here’s my network where we see the clusters of the two Aqara OpenClose sensors also seem to differ from each other:
And here’s the log: https://clientfiles.eu/deconz/deconz.log
[Edit] I opened and closed “OpenClose 55” 10 seconds apart, then opened, pressed button, closed pressed button. Then I opened “Sensor - OpenClose - Kitchen” and closed it 10 seconds later so you can see the differences. Hope this helps!
Hi, this is how it looks in the App:
I Just started my Pi. Now the sensor that was not working is suddenly working!
So I had 2 working door sensors. KontaktsensorA and KontaktsensorB. I opened/closed them both some more times.
So I added another one. It appeared, but the open/close state is not working. This was the behavior I had yesterday.
I opened an closed the “3rd/broken” sensor as well some more times.
Attached you find my debug.log
I stopped the debug mode and restarted the service: Now the 3rd sensor is working as well.
Open/Close states are show for all of them in the App
Is there something I should provide additionally?
What is this wizardry? After a deCONZ restart the sensor object has changed?!
"name": "OpenClose 55",
Mine is not updating either. It is recognized, but then it onl< says closed. After restarting deconz it suddenly shows temperature and closed. but it does not show open at all. Tried it with 3 sensors. pressing the update button doesn’t do the trick either.
So wait for deconz 2.13.03?
Which firmware are you running?
Using 2.13.02. FW is 26720700. Have 2 of these sensors.
Yesterday i added these 2 sensors to phoscon (with GUI), both of them were not working (On/off). I tried to remove and add many times. It didn’t worked, not even once. Today i read this forum and tried once more; without deleting and re adding. To my surprise both work perfectly fine… Weird.
Mine are working now too.
I think a restart is a good thing to do.
I guess my problem was, that the sensor got lost during restart.
Now it’s working like a charm!
The question is, what’s the difference after restarting the system…After connecting the sensor is saw an error in my log (provided above)
"…assertion ‘itemIasState’ failed… "
I am not sure… but after restart it startet showing the temperature, too. 25°C Even if it’s probably only 5-10°C.
You should NOT use temperature, as it’s utterly useless and inaccurate. It just pops up out of nowhere as the current DDF implementation does not yet fully replace the legacy code and associated automatic mechanisms
The assertion message mentioned above can be safely ignored, I’ll spare you the boring technical details around it
Another comment from Swoop:
The odd thing over here is that it worked and works flawlessly. However, there’s obviously a couple of things to follow:
- Make sure your running the latest Conbee/Raspbee firmware https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Firmware-Changelog
- If you run 2.13.0 or 2.13.1, make sure you update to 2.13.2
- If any of the above was not given before you paired the device(s), reset and re-pair while being up to date
- Pair in normal/hybrid mode (tab control)
- If you followed 1-4, try restarting deconz
I can confirm all above mentioned on raspbian with ConBee II. Adding these sensors worked after deconz update to 2.13.2 and (manual, not offered) firmware update to 26720700 well, but for instant sensor updates the pi needed a restart.
Thx to all, helped a lot.
if i want to connect more than one sensor do i have to include the DDF file again for each new sensor?
For me it´s working with RPI3B+ and RaspBee I with firmware: 26400500 on deConz: 2.13.02.
My second sensor is working well, BUT with deCONZ 2.13.03 it doesn´t work for me!!!
Phoscon can´t find/pair the sensor…
Everything was working like a charm. But a couple of days ago it stopped working. I was thinking of the deep temperatures, but maybe this was not the problem. Could it be related to the new update?
I am running 2.13.04.
I am able to connect the sensor. But it doesn’t show temperature anymore. And it is not changing from closed to open.
I know it is connected and is working somehow, because when I restart, it says “not reachable”. In the second I open/close the sensor, it says “closed” instead of “not reachable”