Default user and pw is „delight“, see here, page 11.
1 Like
Thank you, I’ll give that a try
Hi,
Might be a question that has been answered multiple times, but I simply haven´t managed to find an answer anywhere.
What is the schedule for updating deCONZ in the deCONZ integration? They have just recently added support for a much anticipated LK Wiser line-up (in the Nordics at least) in the latest update. But are there any rough idea about when this will be available in the HA integration?
Thank you! 
Its not that often that the integration needs to be updated, usually only if its a new device type or feature. What devices more exactly are you referring to?
Hi,
My specific request is primarily on the LK Wiser Motion Sensor (LK Wiser Motion Sensor · Issue #4817 · dresden-elektronik/deconz-rest-plugin · GitHub).
But the new LK Wiser line is a zigbee line from LK which is, by far, the largest manufacturer of regular switches etc. in Nordic homes. In Denmark I think their non-zigbee models are in like 90%+ of the homes. Now they have made this Zigbee line that is identical to their regular assortment and can be used in existing installations.
I have tried to pair the motion sensor, but without luck. So I assumed that it would work after the changes in the above request.
Other products from the line up which seems to supported by Deconz now:
And they are working on the switch too:
Hope this is enough information
Ok, so those are all device types which are already fully supported by the deCONZ integration, as soon as deCONZ supports those devices they should work in HASS.
Okay. Then I will give it a try again when arriving home
I thought the integration needed to be updated to get the new devices, but that might just be a misunderstandning.
The Integration is implemented to be as plug and play as possible
I think @jonasbuhlkristiansen talks about the addon and not the integration.
Integration is the Python code on the Home Assistant side that comminucates with the 3rd party software. In this case the 3rd party is Deconz.
You can install Deconz in different ways.
Most common is as an addon to Home Assistant. A Home Assistant addon is a Docker based installation that runs on the same machine as Home Assistant. It is the maintainer of this addon that decides when to release a new version of the addon and which version of Deconz to include.
You can also install Deconz on a different computer. This can be a Raspberry Pi or a Debian or Ubuntu based computer or virtual machine. Then you can install Deconz directly from the Dresden Elektronik repository and you can upgrade the minute there is a new version. And you can decide if you want to install their stable version or the beta.
I personally gave up on the addon because it gave me too much trouble with bugs that to my knowledge are still unresolved and I run Deconz beta branch on an intel NUC running Debian. I also run Mosquitto, ZwaveJS2MQTT and Unifi on this machine. I have much more stable performance by avoiding the addons.
1 Like
I’ve had the best success in keeping HA up-to-date by running deCONZ separately from HA (Hassio etc) as well.
1 Like
Anyone else having issues with Aqara Sensros in Deconz not updating in home assistant? I get the initial value from the sensor (iun this case a water leakage sensor and a temerature sensor). But then it wonr update. In phoscan i can see that the sensor is updating and when i us ethe REST API to deconz, i get the correct value. Anyone else have this issue?
I just tried with the new sensors and still with no luck unfortunately.
So KennethLavrsen might be correct about the add-on/integration. Might bee the addon that needs to be updated.
I will just cross my fingers that the add-on is updated at some point. I have previously been running Deconz in a seperate container, but after a few issues I decided to with the HA integration which has been running without a single problem for a loooong time. But so far without my Wizer sensors
1 Like
That typically means the websocket connection fails to establish
Alright. Is there any good infirmation/thread on how to test & troubleshoot?
What does your setup look like?
Running HAOS in a VM and Deconz in docker on my xpenology NAS.
For everyone who is unsure: The update to deConz 6.10 coming from a version before went smooth on a HA Blue!. First facts: 3.5% Swap released and less CPU use. Everything works fine for 20 hours now
Have you properly exposed the websocket from your docker? You need to configure it so deCONZ can tell home assistant on which port the websocket is available on.
Btw: I also don’t get any status changes for this sensor via the event node on node red. Don’t know if this is an deconz problem or related to the deconz home assistant integration.
At least there seems to be coming plausible data from deconz. This is what I get from the developers tools. There is state and orientation changes. So I guess the problem is within HA:
Ereignis 34 ausgelöst 20:00:
{
"event_type": "state_changed",
"data": {
"entity_id": "binary_sensor.garagentor",
"old_state": {
"entity_id": "binary_sensor.garagentor",
"state": "on",
"attributes": {
"on": true,
"temperature": 23,
"orientation": [
2,
2,
87
],
"tiltangle": 71,
"vibrationstrength": 46,
"friendly_name": "Garagentor",
"device_class": "vibration"
},
"last_changed": "2021-08-24T18:00:27.525390+00:00",
"last_updated": "2021-08-24T18:00:37.625712+00:00",
"context": {
"id": "f118cf58b76ac3f8e23110b34e847eba",
"parent_id": null,
"user_id": null
}
},
"new_state": {
"entity_id": "binary_sensor.garagentor",
"state": "on",
"attributes": {
"on": true,
"temperature": 23,
"orientation": [
2,
73,
17
],
"tiltangle": 71,
"vibrationstrength": 46,
"friendly_name": "Garagentor",
"device_class": "vibration"
},
"last_changed": "2021-08-24T18:00:27.525390+00:00",
"last_updated": "2021-08-24T18:00:37.643055+00:00",
"context": {
"id": "457277388928f96c556c18e69026b3f8",
"parent_id": null,
"user_id": null
}
}
},
"origin": "LOCAL",
"time_fired": "2021-08-24T18:00:37.643055+00:00",
"context": {
"id": "457277388928f96c556c18e69026b3f8",
"parent_id": null,
"user_id": null
}
}
Ereignis 0 ausgelöst 20:03:
{
"event_type": "state_changed",
"data": {
"entity_id": "binary_sensor.garagentor",
"old_state": {
"entity_id": "binary_sensor.garagentor",
"state": "off",
"attributes": {
"on": true,
"temperature": 23,
"orientation": [
2,
73,
17
],
"tiltangle": 71,
"vibrationstrength": 46,
"friendly_name": "Garagentor",
"device_class": "vibration"
},
"last_changed": "2021-08-24T18:01:32.724077+00:00",
"last_updated": "2021-08-24T18:01:32.724077+00:00",
"context": {
"id": "9b0136258eea97a5baa84a9a1e0c5e8b",
"parent_id": null,
"user_id": null
}
},
"new_state": {
"entity_id": "binary_sensor.garagentor",
"state": "on",
"attributes": {
"on": true,
"temperature": 23,
"orientation": [
2,
73,
17
],
"tiltangle": 71,
"vibrationstrength": 46,
"friendly_name": "Garagentor",
"device_class": "vibration"
},
"last_changed": "2021-08-24T18:03:33.418602+00:00",
"last_updated": "2021-08-24T18:03:33.418602+00:00",
"context": {
"id": "3e698fe0431d7a20d3a4a61986ae91e6",
"parent_id": null,
"user_id": null
}
}
},
"origin": "LOCAL",
"time_fired": "2021-08-24T18:03:33.418602+00:00",
"context": {
"id": "3e698fe0431d7a20d3a4a61986ae91e6",
"parent_id": null,
"user_id": null
}
}
I would guess not then
I followed a guide i found and i mapped up ports 80, 443, 5900, and 6080. Since 443 and 80 are used for other stuff i mapped them to 8080,8443 and used thoose ports to connect. Since i got trough the wizard, i expected it to be finished. Do i need to do something else?