Hi All,
My problem is that when I call https://phoscon.de/discover I get an incorrect IP address in return. Why is it the the ConBee/deCONZ reports an incorrect IP address? How can that be reset/changed/corrected?
Comment Removed.
External. The IP address shown in the upper right corner of Phoscon - is wrong.
(and I’m not using HassIO, but HA)
Shut down deconz try to set up the integration which will fail and then allow you to insert host address and port manually
I just migrated my Hassio from rpi to a diy NAS. All seems to be working fine except the deconz web ui. I get the error below. I’ve tried uninstall/install deconz from scratch but same problem.
Other addons gui is working though.
Any idea how to solve?
Hi, I asked sane question, hope for a solution
You would need to make sure that the API is available outside of the hassio instance. I think @frenck said that will be possible, then you should be able to pair your other hass instance to deconz
How come all other hassio addons gui is working? Seems strange. I do get these errors though…
So it used to work and now stopped?
For further reference - I’ve solved it buy adding this to the config yaml file.
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_networks:- 172.16.0.0/12
1 Like
After pairing the IKEA motion sensor in deCONZ, HA Automation GUI shows a new variable named “Duration” ;
What is this “Duration” and how should it be used?
Duration is from HA automations. The automation will only trigger if the entity changes to the new state (in your case “motion detected”) for the specified duration.
What does “for the specified duration” mean?
Example: If set to 2 min, someone must be running around in front of the sensor for minimum 2min before it triggers?
When there is no motion the state of the motion sensor is “off”. As soon as motion is detected, the state of the motion sensor changes to “on” and depending on the motion sensor it will stay “on” for some seconds/minutes before it goes to “off” again.
The duration parameter is not really suited when motion is detected, rather when motion is not detected anymore. You can have duration of 5 minutes for “no motion detected”, this way the automation will only trigger if the motion detector was in the state “off” for at least 5 minutes, meaning if motion is detected again during these 5 minutes, the “timer” will be reset.
Hi Together,
recently I bought a Fyrtur cover and added it to deconz. Everything looks fine, I see the entity in HA, see it in the Web GUI as well as in the VNC view.
In the beginning up, down and moving to a certain position worked in HA, in deconz and in automations. Unfortunately it stopped working, although the device is still online and available. When trying to execute commands via VNC I just get “timeout” and when trying it via HA I get the following logs:
14:27:14:901 delay sending request 1 dt 5 ms to 0x000D6FFFFE2FD78D, cluster 0x0102
14:27:14:917 0x000D6FFFFE2FD78D error APSDE-DATA.confirm: 0xA7 on task
0x000D6FFFFE2FD78D is the device ID, 0x0102 is the cluster to control the cover.
Any ideas or experiences with your Fyrtur covers?
Thx.
This happens all the time with ZigBee devices. Probably all you need to do is to restart HA, and perhaps also deCONZ.
@Burningstone, thank you so much. That’s a very good explanation. It allows me to continue experimenting. Happy New Year!
Are you using an USB extension cable for the ConBee stick? Did you add any new hardware close to the ConBee stick recently? Is ZigBee on a different channel than your/your neighbours WiFi? How far away from the stick is your cover?
You’re welcome 
Happy new year to you as well!
Hi @Rdoull , did you manage to add them yet? I’m experiencing the same issue. Resetting them right before or during discovery doesn’t help here.