In the Integration GUI in HA, old deCONZ groups are still there (same issue here), even after calling deconz.device_refresh service or restarting HA and Deconz.
Calling API /groups/ shows only the current groups defined in Phoscon but HA also keeps old groups.
Would it be possible to be able to delete old “ghost” groups from HA ?
I have IKEA light and several aqara sensors set up in deconz and working fine in HA.
However I tried adding a Aqara multisensor (temp/humid/pressure) and it works fine in deconz, however it does not show up in HA. I even added another sensor after that and it shows up fine in HA. It seems others have same sensor working with HA. I’ve tried rebooting HA and HASSOS, but does not help. Any suggestions ?
How do you make use of the ‘long-press’ action on the dimmer switches. The Philips for example has a long-press action ‘xxx1’ for every physical button on it.
My current plan is to have different cleaning zones assigned to short and long press actions. The problem is that when i press and hold one of the buttons the normal deconz_event ‘xxx0’ is already sent to the vacuum and it starts cleaning the zone assigned to it.
long press triggers xxx1, (after about 1 sec of pressing and without triggering xxx2 first) and then release triggers xxx3
So you can easily differenciate long and short presses.
I’m testing with the conbee2 now and have a Philips hue dimmer connected. I can see it in deconz, and HA, but I can’t find it in node-red. Any pointers where to look for troubleshooting?
what is your advice to slow deconz reactions.
Example:
Click on IKEA button, and after 5 seconds IKEA bulb is turned on.
Funny is that another IKEA bulb (E14) is working fast - max delay is 1s.
I already checked free chanells, i am using channell 15 as default and it looks free.
I am running latest version of HA and deCONZ, running from RaspberryPi3.
IKEA Fyrtur only works properly with deConz if both the remote and the blinds are directly connected to the coordinator (Conbee). I tried that and it worked for a while but, as soon as I restarted HA, both devices got paired with a light bulb nearby and now it doesn’t work. You press the button and it respond after 5 min. Deconz is pointless. Every time I need to add a device I need to spend a week troubleshooting.
my fyrtur are having issues all the time.
They are just 3 or 4m away from my conbee II and in a range of 30cm up to 1,5 m there are several routers.
In the deconz app I can see that it is connected to the nearest router, but after some time (somtimes days, somtimes only hours) the connection is lost indefinitely.
Only a reset of the blinds can help here.But that means, that the reporting to home assistant and the max. length must be set again.
I like them, but they are not working very well.
The complaints here are not the only one, as you can see here
I noticed a new entity related to the Deconz integration. The entity is light.configuration_tool_6 and the name is Configuration Tool 6. It’s part of the Daylight sensor device in HA.
This entity showed up the first time when I upgraded to Home Assistant 0.108.x and is still present on 0.108.6. My setup is based on docker.
I’ve noticed the same, but here it’s called “Configuration tool 11”.
It seems that this feature/bug that was introduced with one of the latest deCONZ updates and as far as I understand it relates to the Zigbee controller, e.g. ConBee, itself:
Does someone has an issue with aqara PIR sensor?
I have one aqara and one xiaomi. On both, time between detected and clear states was 1min and 30s. Since yesterday (saw it on the history tab) on the aqara time between states is 5min. Does that means I need to change the battery? Or is this a bug in deconz?
Thanks for linking to the issue. I still don’t understand what this Configuration Tool is for. Hopefully it will be “fixed” in an upcoming release of deconz.
Hopefully deleting the entity in HA won’t cause any trouble.
Anyone knows how to get a scene in HA, after created in deconz?
I tried deconz.device_refresh service, which gives me new devices but didn’t fetch the scene until a restart.
I did it as follows:
Start the scene via Phoscon.
Go to the scene editor in HA and add a new one.
Add all the devices which are relevant in their current state and save the scene.
Delete the scene in deConz.
Restart HA.
This process works as well vice versa.
But remember: Sometimes it could be more efficiant to keep the screne in deConz. Especially in scenes with many devices, the wireless traffic, HA produces is much higher, then produced by deConz. As I understood, HA fires one command per device meanwhile deConz is more efficiant and saves the configuration on the devices. That reduces the wireless traffic and is more reliable. There is a post I gess written by @KennethLavrsen which explains this a little bit more professional
My own experience is, that even if HA lost connection to a certain device and will not work, the deconz controlled scenes still work. I manage the basic scenes like dark, medium, bright, nightlight and so on with deConz/Phoscon and some special scenes like TV-Light, Crime, Party etc. with HA.
Thanks for the detailed answer. I wanted the scene defined in deConz since it is much easier and quicker.
I wanted to get the deconz scene imported to HA, it was not visible there after i created it in deconz. I needed to restart homeassistant to see scene.room_name
Btw. had some strange issues after moving some lights and sensors from hue bridge to deconz, lost connection to all lights. Nothing worked, I read the a lot of posts… so i had to reset every light with a remote and rescan… i hope this is not happening again, since I want to get rid of my hue bridge