deCONZ - Official thread

Hi @pergola.fabio - just did that and still get the warning message.

Any other suggestions on how I can fix?

you are correct, i am still seeing it too , it was gone for a while , now my logbook is indeed filled again with those messages

21-02-09 07:15:19 WARNING (MainThread) [supervisor.addons.options] Unknown options vnc_password
21-02-09 07:16:19 WARNING (MainThread) [supervisor.addons.options] Unknown options vnc_password
21-02-09 07:17:19 WARNING (MainThread) [supervisor.addons.options] Unknown options vnc_password
21-02-09 07:18:19 WARNING (MainThread) [supervisor.addons.options] Unknown options vnc_password
1 Like

anyone knows if there is an issue created for this : WARNING (MainThread) [supervisor.addons.options] Unknown options vnc_password

my log file is now flooded with those messages

2 Likes

have a setup like yours, well, almost, using a dedicated HA config for the conbee II / Deconz (and the bluetooth tracker), and trying to use Mqtt to transmit the registered entities to my other production system.

How do you do that, considering an entity has several attributes, like eg:

do you create mqtt sensors for each and every attribute? (up to now, I use mqtt state_streams to transmit the Bluetooth device_trackers this instance registers, and don’t want to set the publish_attributes: true config option, because I only need there state for these BT device_trackers.

thanks for having a look

Just installed latest add-on update (6.7.0) and got somehow confused…

  • add-on shows now that installed Phoscon version is v2.09.03 dated 23/12/2020
  • change log shows that the latest available version is v2.09.02 dated 08/02/2021 (and it is beta)
    So we have some mismatch in latest available version (current version seems not to be available yet) and dates (it is older than latest available beta with lower version number). Whats up here?

Dresden Elektronik suck at keeping their website up to date. Always look at github. https://github.com/dresden-elektronik/deconz-rest-plugin/releases

1 Like

I just switched from a Zigate Wifi Stick to a ConBee II stick connected to a Raspberry Pi with Phoscon-GW on it.

Is there any way to manage these through Home Assistant?
I can only specify a device parameter in the addon configuration for a local device, is there any other way to get the gateway page visible within Home Assistant?

I have already tried using the iframe Panel, however my installation works on https and no http can be displayed in an iframe. Or is it somehow possible to enable https on the Phoscon-GW?

Just to answer the question why I don’t put the stick in the Home Assistant server, is that the server is hanging in a place where there is almost no coverage.
I also control my z-wave devices through a Fibaro Home Center stationed elsewhere in the house.

You should remove the add-on as you already have deCONZ running. Just add the integration if it’s not automatically discovered.

The integration is working, its only for administrative purpose.

I have a Mi Magic Cube (new) linked to my Conbee II. I seem not to get the rotate left and right working. The rest of the actions seems to work fine. I have checked the device to connect to the MI app and it works fine. I am on Conbee version 2.9.3. If I look at the deconz_event I don’t see any events.

For experimenting, I now own 4 Ikea Tradfri gadgets: motion sensor, pushbutton, on/off switch and volume “dimmer”. I have some mixed success with them, and just can’t get to the bottom of it:

  • Motion sensor and on/off switch integrated immediately, as they should. They provide events, battery status and everything expected.
  • The Symfonik volume “dimmer” was recognised in Phoscon, is showing up as device in HA and offers the list of events to attach an action to. But it doesn’t provide a battery sensor and doesn’t send any events when operated.
  • The Push Button doesn’t show up in Phoscon, but it does in DeConz map. It also shows up as HA device, but doesn’t offers any events to attach an action to. It also exposes no battery sensor and doesn’t actually produce any events when pushed.

So the Symfonik and the Push Button are basically “dead” to HA and don’t produce any events (also confirmed when listening to deconz_events in dev. tools). The other two do, though. I re-linked them and made sure that they are very close to the Conbee itself (no routing), but it doesn’t make a difference at all.

image

I have the latest DeConz SW that already has the proper button map (checked directly in button_maps.json in deconz docker container), as this was at least one issue with the Symfonik controller.

So any more suggestions how to proceed with those welcome. I really would love to integrate them with my other setup!

Thanks, habitoti

Battery sensors can sometimes take a few hours to appear as it depends on when the device itself sends the update back to the conbee.

Are you on the latest firmware for your conbee stick? And latest version of deconz? if its an old firmware then the device may appear in the map but it won’t send anything useful via the rest api to Home Assistant

Updated to 6.7.0 and found that it had the annoying problem of reporting false positives on my Samsung buttons once an hour (including my doorbell). Reverted to a backup of 6.5.0. My ConbeeII stick firmware is up to date. Anyone else seen this?

can someone help me out with this one?
i reinstalled my home assistant docker from hdd to my SSD and loaded my backup, but deconz won’t start anymore, nginx problems?

[cont-init.d] novnc.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[06:37:22] INFO: Websockify waiting for VNC to start
[06:37:22] INFO: Running the IKEA OTA updater...
[06:37:22] INFO: Running the deCONZ OTA updater...
[06:37:22] INFO: Running the OSRAM LEdvance OTA updater...
[06:37:22] INFO: Starting VNC server (local/yes)...
[06:37:23] INFO: Starting websockify...
WebSocket server settings:
  - Listen on 127.0.0.1:5901
  - Flash security policy server
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from 127.0.0.1:5901 to 127.0.0.1:5900
[06:37:25] INFO: deCONZ waiting for VNC to start
[06:37:25] INFO: Starting the deCONZ gateway...
QCoreApplication::arguments: Please instantiate the QApplication object first
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
06:37:27:917 HTTP Server listen on address 0.0.0.0, port: 40850, root: /usr/share/deCONZ/webapp/
06:37:27:945 CTRL. 3.27.206:37:27:995 COM: /dev/ttyACM0 / serialno: , ConBee II
06:37:27:996 ZCLDB init file /data/.local/share/dresden-elektronik/deCONZ/zcldb.txt
Error: no such column: createdate
[06:37:28] INFO: Starting Nginx...
**nginx: [emerg] open() "/dev/stdout" failed (30: Read-only file system)**
06:37:28:154 shutdown after signal(15)
In exit
Closing socket listening at 127.0.0.1:5901
06:37:28:160 parent process s6-supervise
06:37:28:160 gw run mode: docker/hassio
06:37:28:160 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
06:37:28:161 DB sqlite version 3.27.2
06:37:28:161 DB PRAGMA page_count: 9
06:37:28:164 DB PRAGMA page_size: 4096
06:37:28:164 DB PRAGMA freelist_count: 0
06:37:28:164 DB file size 36864 bytes, free pages 0
06:37:28:165 DB PRAGMA user_version: 0
06:37:28:165 DB upgrade to user_version 1
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
06:37:29:490 DB write sqlite user_version 1
06:37:29:551 DB PRAGMA user_version: 1
06:37:29:551 DB upgrade to user_version 2
06:37:29:736 DB write sqlite user_version 2
06:37:29:801 DB PRAGMA user_version: 2
06:37:29:801 DB upgrade to user_version 6
06:37:29:995 DB write sqlite user_version 6
06:37:30:072 DB PRAGMA user_version: 6
06:37:30:072 DB upgrade to user_version 7
06:37:30:250 DB write sqlite user_version 7
06:37:30:326 DB PRAGMA user_version: 7
06:37:30:326 DB cleanup
06:37:30:331 DB create temporary views
06:37:30:334 started websocket server at port 8081
06:37:30:337 create default username and password
06:37:30:342 [INFO] - Found file containing button maps. Parsing data...
06:37:30:349 [WARNING] - Button map 'sunricherCCTMap' in JSON file has no assigned ModelIDs. Skip loading button map...
06:37:30:352 [INFO] - Button maps loaded.
06:37:30:353 dlg action: Read binding table
06:37:30:353 found node plugin: libde_rest_plugin.so - REST API Plugin
06:37:30:357 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
06:37:30:392 OTAU: create 117C-1101-20024623.zigbee
06:37:30:408 OTAU: create 117C-11C5-22010631.zigbee
06:37:30:430 OTAU: create 117C-2201-23050631.zigbee
06:37:30:448 OTAU: create 117C-2801-13013572.zigbee
06:37:30:468 OTAU: create 117C-2203-23050631.zigbee
06:37:30:488 OTAU: create 117C-1187-22009631.zigbee
06:37:30:504 OTAU: create 117C-1102-22005631.zigbee
06:37:30:522 OTAU: create 117C-4204-20029623.zigbee
06:37:30:538 OTAU: create 117C-11C8-20022623.zigbee
06:37:30:559 OTAU: create 117C-4205-23050631.zigbee
06:37:30:577 OTAU: create 117C-11CA-21024631.zigbee
06:37:30:598 OTAU: create 117C-4103-23050631.zigbee
06:37:30:618 OTAU: create 117C-4206-23050631.zigbee
06:37:30:633 OTAU: create 117C-11C6-23015631.zigbee
06:37:30:657 OTAU: create 117C-2802-10021655.zigbee
06:37:30:676 OTAU: create 117C-4104-00010021.zigbee
06:37:30:694 OTAU: create 117C-4101-23068631.zigbee
06:37:30:712 OTAU: create 117C-2202-23050631.zigbee
06:37:30:729 OTAU: create 117C-2101-23068631.zigbee
06:37:30:752 OTAU: create 117C-4202-23068631.zigbee
06:37:30:770 OTAU: create 117C-4201-23068631.zigbee
06:37:30:790 OTAU: create 117C-11C1-23014631.zigbee
06:37:30:807 OTAU: create 117C-11C4-12214572.zigbee
06:37:30:825 OTAU: create 117C-11C2-23028631.zigbee
06:37:30:843 OTAU: create 117C-0002-165801BC.zigbee
06:37:30:866 OTAU: create 117C-4203-20029623.zigbee
06:37:30:882 OTAU: create 1189-0019-00102428.zigbee
06:37:30:900 OTAU: create 1189-000D-00102428.zigbee
06:37:30:915 OTAU: create 1189-000C-00102428.zigbee
06:37:30:931 OTAU: create 1189-003D-00103101.zigbee
06:37:30:984 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
06:37:31:007 COM: /dev/ttyACM0 / serialno: , ConBee II
s6-svwait: fatal: timed out
06:37:31:302 Skip idle timer callback, too early: elapsed 949 msec
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

It seems to me that your Conbee stick is no longer on this /dev/ttyACM0 port. As the serialno is not detected. There are several posts above that mention changing the port numbers when you also have a different stick in there as well. You can have a look at Supervisor → System → Log provider: Host. Mine is detected there and the serial no is posted:

[    4.238636] usb 1-1.3: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
[    4.238655] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.238670] usb 1-1.3: Product: ConBee II
[    4.238685] usb 1-1.3: Manufacturer: dresden elektronik ingenieurtechnik GmbH
[    4.238701] usb 1-1.3: SerialNumber: DE212XXXXX

If you do not see it there it is probably not a changed port issue but something else.
HTH

it’s the nginx error, but i don’t know why this is happening ??

[19:58:07] INFO: Starting Nginx...
nginx: [emerg] open() "/dev/stdout" failed (30: Read-only file system)
[19:58:08] INFO: Starting Nginx...
nginx: [emerg] open() "/dev/stdout" failed (30: Read-only file system)
[19:58:09] INFO: Starting Nginx...
nginx: [emerg] open() "/dev/stdout" failed (30: Read-only file system)

There seem to be an update - could it help?

helped for not killing the service. deconz is running now, but the error stillt exists as you can see above. so i cant access the gui… seems to be a problem with docker/permissions, but i don’t understand that exactly.
it was runnig before with the same permissions on the same server, just swaped the hdd

Is it possible to add a Binary_sensor ‘tampered’ for some ZHAPresence devices that have state attribute ‘tampered’ ? Deconz rest api already supports this

Hi, I am running deConz 6.7.0 (HA: supervisor-2021.02.9, core-2021.2.3)

6.7.2 is currently offered as an update, changelog says:

6.7.1 Restart nginx server on error

6.7.2 Revert restart nginx server on error

so, to me it looks like deConz 6.7.2 == deConz 6.7.0
and i shouldn’t be doing anything.

Is this Correct?