Ok, so now I think I realize what the issue is. I also have a Z-Wave stick. So the traditional numbering likely won’t work either, as the Z-Wave stick and the conbee stick will be switching device numbers. I’ll have to do some testing.
They may, or they may not. It’s just a possibility to be cognizant of if things suddenly stop working.
It seems dependent on what kind of system you run. It’s stable for me.
Also, that should only be a race condition on a host reboot I believe. Just restarting HA (for a config change, for example) should not effect this. So it hopefully shouldn’t be something that happens often (or at all).
1 Like
After a day of just testing different versions, I tried updating to the latest version 26680700 with Win 10 (again), and it finally worked… After a day wasted on testing different versions frustrated (even tried the latest version 3 times before)… it just worked like magic. I have no idea why it worked this time, but i won’t ask questions at this point.
In the deCONZ Integration options page, ‘Allow automatic addition of new devices’ what is supposed to do? I can’t find anything in the integration wiki page.
It is actually a good feature to turn off. Before it was added as a config, all new devices added in Phoscon were sucked into Home Assistant the minute it was discovered and before you had the chance to rename the default name to something useful.
By turning this off, you can pair new devices and rename then first, and then pull them into Home Assistant so you avoid having to rename the devices and their entities in Home Assistant.
To pull devices in you go to developer tools > services and key in deconz.device_refresh and submit it with no data. That makes HA pull in new devices when you decide you are ready for it
6 Likes
thanks @KennethLavrsen
i might submit this to the deconz integration documentation page in github
And CLIP sensors is that daylight sensor tha deconz generates automatically?
I have a conbee II stick with several zigbee sensors like the aqara motion/temperature/door sensors and some lux sensors (from AliExpress).
They are all at the same place and I’m still in testing mode to see if everything is reliable. I noticed that one temperature sensor and one lux sensor were not updating anymore (after some days) for a period of 16 hours. I have pressed the buttons on the devices to reconnect them and now they are working correctly.
What could be the reason for this? All the sensors are on the same table, so they are all at the same distance.For me this is a serious issue because you don’t know if all sensors are still working. So you have to check them the whole time?
Is z-wave more reliable or must be the conclusion that you should only have wired sensors for reliable working?
I noticed also that when you stop deconz software, you change some states of the sensors, so for example open the door/window or close it ==> then you restart deconz, the states of the sensors are not always correctly. I think this is because of the battery sensors are one way sending the information and that deconz software cannot poll the information. So you have to wait till a change of the state of the sensor is pushed to the zigbee network. Is that correct?
Hello
I have a conbee II stick with several zigbee sensors like the aqara motion/temperature/door sensors
and many light like hue, osram, and legrand netatmo roller cover switch.
I use rasperry pi 4 with hassio.
My problem is about :
when a power cut occurs and my rasperry restart, the xiaomi sensors and only them become not working in home assistant.
In the phoscon application they are ok, change state correctly but in ha they no longer change state.
I tried to use the deconz_refresh_device service in ha but it is the same. I tried to restart ha then start deconz , same issu .
To solve it I have to remove all of them from phoscon, restart ha and then put them back in part one.
thx a lot for help
just got things working, but i have noted that phoscon drops outs a lot where it says “not reachable”
otherwise very easy to config things
EDIT: adding the ikea trådfri lights and the puck remote, i can turn the brightness up and down, but change of color temperature only works from within phoscon, not from the remote. brightness from the remote do work and on/off
Hi,
After an upgrade of HA and HA OS I got complete radio silence for my Conbee II. Any ideas?
sorry to bump this question, but I am out of my options … I have only 1 (the Daylight CLIP) sensor in my new Deconz setup, after having had a Tradfri option sensor for half a day. I took that out, and after restart, the integration still showed 4 devices:
The Daylight sensor and the Deconz Phoscon-Gw, which are supposed to be there I guess.
It did however also show the Tradfri motion sensor. Since no Delete button was available, I had to edit the .storage core.device_registry file, and delete it from there. Which, after 3! attempts finally worked.
There’s still this odd unnamed/unknown device, registered to the same Deconz config_entry, which keeps returning. I can even see it being restored in real time after deleting the entry in the core.device_registry file.
Do we have any clue what this might be, and how to get rid of it?
{
"config_entries": [
"a0redactedcfa"
],
"connections": [
[
"mac",
"02:42:ac:1e:21:06"
]
],
"identifiers": [],
"manufacturer": null,
"model": null,
"name": null,
"sw_version": null,
"entry_type": null,
"id": "fec62ac3595cb23a78ff29f941ea2607",
"via_device_id": null,
"area_id": null,
"name_by_user": null,
"disabled_by": null
}
thanks for any help you can lend me.
Btw, why does the CLip Daylight sensor show
"manufacturer": "Philips",
"model": "PHDL00",
"name": "Daylight",
"sw_version": "1.0",
while I havent even enabled my Hue Hubs on this instance? Is that available without even doing so? Which would seem an unwanted Hue leakage to the Zigbee network to be honest. It doesnt even show up on my Production system with 2 Hue registered hubs …
You can use the service remove orphaned devices to clean up stuff
This is probably a dumb question but I haven’t been able to find an answer myself (noob as I am).
Love the integration btw!
When a new update to Home Assistant is released there seems to be a 50/50% chans that Deconz changes the signal channel, giving me logs saying something like “channel is 22 should be 11”. After having tried to revert the Channel manually I still have to add my lights and sensors again. Could there be something in my setup that is wrong?
I’m holding off on the january update since I just added my hallway lights (IKEA) again.
A yes, I. use admit I went al the way down there before, I think deCONZ - Home Assistant
Still, it doesn’t explain why it is called a Philips sensor PHDL sensor. IN fact, I would feel this needed to be changed, because it simply isn’t a Philips Hue Daylight Sensor…
Is this done in the implementation of the Home Assistant integration, or in the Deconz library. Maybe I can ask the dev’s about that.
this is a true PHDL sensor:
and the Deconz is clearly copied from that, even its attributes are named like the PHDL.
‘door Philips’ …
Btw, its workings are rather useless, since it was Golden Hour until midnight, and the same for the morning golden hour. Same goes for the midnight state itself, but I think that has been touched somewhere else already.
seems to be defined here: Sensors - deCONZ REST-API
and calculated according to deconz/pydeconz/sensor.py at c89a33b0f72216567209a8cab1e0ebd65111d1d6 · Kane610/deconz · GitHub
so, all based on offset minutes, which is surprising to me because I had understood it to be calculated based on the elevation of the sun as explained here GitHub - mourner/suncalc: A tiny JavaScript library for calculating sun/moon positions and phases.
Yes, thanks, I did that (should have mentioned it, sorry), but it doesnt take out the unknown sensor.
Is there a spot in a config file somewhere we can see which are these orphaned devices? Doesn’t seem to be in the .storage files, because everything I edit there simply gets restored…
As written… and you can also read this in the Phoscon documentation is it from the deCONZ software. It is not added by HA.
I guess you need to convince the people at Dresden Elektronik to make that change.
Do you mean upgrading the addon changes channel? Or ha core? Because core doesn’t care about what zigbee channel you use.
It calculates what devices are orphaned on the fly here https://github.com/home-assistant/core/blob/ab25c5a2bdb010fc9ae68bdc0eb5a96dc461e46d/homeassistant/components/deconz/services.py#L155
thanks!
must study that some more, but up to now, it doesnt take away this orphaned device:
Unless this is yet another device enabled by default in the Deconz, which I simply dont know of…
btw, Ive disabled the Clip sensors in the Deconz setting, but the daylight sensor is still there as you can see, and Verwijderen (delete) is greyed out:
