deCONZ - Official thread

enabled logger like, then see this:

2022-05-30 23:33:25 WARNING (MainThread) [pydeconz.models] Unsupported device type Unknown
2022-05-30 23:33:25 DEBUG (MainThread) [homeassistant.components.deconz] deCONZ event created: ikea_remote_2
2022-05-30 23:33:25 DEBUG (MainThread) [homeassistant.components.deconz] deCONZ event created: ikea_on_off_switch_3
2022-05-30 23:33:25 DEBUG (MainThread) [homeassistant.components.deconz] deCONZ event created: ikea_remote_1
2022-05-30 23:33:25 DEBUG (MainThread) [homeassistant.components.deconz] deCONZ event created: ikea_on_off_switch_2
2022-05-30 23:33:35 DEBUG (MainThread) [homeassistant.components.deconz] deCONZ HASSIO discovery {'addon': 'deCONZ',
 'api_key': 'xxxx',
 'host': 'core-deconz',
 'port': 40850,
 'serial': 'xxxx'}

Same warning here

Share a diagnostics file please. Me2 comments doesn’t help

Try sharing a diagnostics file instead

"hascolor": false, "lastannounced": null, "lastseen": "2022-05-31T04:45Z", "manufacturername": "dresden elektronik", "modelid": "RaspBee", "name": "Deconz", "state": { "reachable": true }, "swversion": "0x26720700", "type": "Unknown",

1 Like

Thanks, what I can see is that the Raspbee has type “Unknown”, it should have “Configuration tool”. I’ve pinged deconz devs on this.

1 Like

same for me:


      "9": {
        "etag": "cb4b4e24a20551d4af4a947847236ff8",
        "hascolor": false,
        "lastannounced": null,
        "lastseen": "2022-05-31T06:18Z",
        "manufacturername": "dresden elektronik",
        "modelid": "ConBee",
        "name": "Conbee",
        "state": {
          "reachable": true
        },
        "swversion": "0x26390500",
        "type": "Unknown",
        "uniqueid": "00:21:2e:ff:ff:02:a4:80-01"
      }

Could someone please explain me the source routing. What does the number 3-7 mean. And what should I choose?

Also, the fast neighbor discorvey. What is the purpose? and it says “use this only temporarily”, how long is temporarily 2022-06-03_09-50-55

Source Routing is an application based, alternate routing which is only possible between powerd devices. The way to the battery powerd switches and motion devices will be calculated via the old way.
The minimum LQI defines, which link should be considered for the route calculation from one divice to the next one. If you have a good network, you can use 150 and above.
The calculated routes will be stored in the application and primary used for communication.
Maximum hops is self explanatory.
Fast neighbor discovery is new for me as well but seem to be only good for the first, new route calculations.

I work with source routing for a long time and could solve all instability with that.
My recommendation to give it a try.

Before I spend a small fortune on a Philips Hue lamp (450 dollars)… Anyone running a Philips Hue Ensis on Deconz? Does it register as two colour lights? Most lights just work but I am unsure about this one.

I have the ensis and yes it reports as two lights

1 Like

I have some problems with the latest update 6.14.1.
some of my sensors (mostly aqara temp/humidity or sonoff door sensors) become suddenly unavailable and I have to pair them again. I restored a backup for now and will look if this happens again.

anyone else with problems on latest build? or do I miss something?

I cannot remember a release of HA or Deconz where we did not have a report of lost Aqara sensors.

It is not the release that is the problem. It is the fact that an upgrade means a restart. I sometimes see all my Ikea switches showing offline. Until I press then once which wakes then up.

You should try to wake up your sensors and switches first before you declare then disconnected and needing repairing. Battery devices sleep unless something happens that wake then up. Like pressing a button or opening a window. In some cases with some devices you need to short press the pairing button which makes then wake up but not doing a factory reset.

1 Like

Thanks for your reply. I don’t mean that the sensors are gone directly after the upgrade. They suddenly go off one or two days after last state change. And I don’t want to press a button every two days :smiley:

Hi,

Just a simple question, but any idea on when this “Fix setting lastannounced and sensor reachable by manup · Pull Request #6106 · dresden-elektronik/deconz-rest-plugin · GitHub” will released, i’m suffering from this bug.

It will be a part of 2.17 release, not sure when it will be out, there has been some different long time periods between releases this year.

2 Likes

This was also occurring for me, I am using the windows installer. Installed the 6/7/22 pre-release and has not happened since.

Same for me on HA startup.

Is it the conbee/raspbee device just like pergola.fabio and joselito1 reported?

Yep:

      "41": {
        "etag": "xxx",
        "hascolor": false,
        "lastannounced": null,
        "lastseen": "2022-06-13T18:55Z",
        "manufacturername": "dresden elektronik",
        "modelid": "ConBee II",
        "name": "Configuration tool",
        "state": {
          "reachable": true
        },
        "swversion": "0x26720700",
        "type": "Unknown",
        "uniqueid": "xxxx"
      },

Is this the right thread to post questions about the deconz addon?

thx