ebaauw/homebridge-deconz

Homebridge plugin for deCONZ

homebridge-deconz's Issues

Sensors are exposed as buttons?

eg. motion sensors are exposed as buttons to HOME. Is it wanted like that?
also it should splittet into sensors AND switches.
My switches are never exposed to HOME because they are fully configured with deconz.

for my setup, i used the homebridge-hue plugin twice for many month in sub bridges (so this is not a big problem for me):

1. only sensors (together with the homebridge-alexa plugin and some other..)
2. only lights from deconz are exposed in an sub bridge (Alexa got the lights directly from deconz)

this is mandatory so alexa can control lights even my internet is broken or the alexa homebridge service is broken.. again..

in this case, i replaced my "light only" homebridge-hue bridge with this plugin and its work great. thank you!

Danfoss Ally thermostat: The history does not show up in Eve app

Hello,
I am quit sure that we had the history of the thermostat through Homebridge-Hue and Eve app. Now, no such information is displayed.

warning potentially stale api key

On restart, I get three of these warnings in a row [deCONZ] ZigbeeGateway: warning: XXXXXXXXXX: potentially stale api key: {"create date":"2022-03-15T08:17:31","last use date":"2022-03-15T08:35:21","name":"homebridge-deconz#homebridge"}

Everything works despite the warning

error: TypeError: Cannot read properties of undefined (reading 'mode')

Hi there, suffering from this error every few seconds or so when connecting to a deCONZ 0.14.1 gateway with a significant number of devices attached.
Previously using Homebridge Hue with no issues, I set up the auto discovery (gateway was found correctly) and enabled connection to the bridge in the phoscon web app.

(Looks like there's something in the Tradfri Dimmers that are proving an issue here - removing them from the phoscon app allowed the initialisation to proceed.)

It connected, but am stuck here:

[07/03/2022, 16:50:03] [deCONZ] flush cachedAccessories
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 3: GET /config
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 3: 200 OK
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 4: GET /lights
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 4: 200 OK
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 5: GET /sensors
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 5: 200 OK
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 6: GET /groups
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 6: 200 OK
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 7: GET /groups/0
[07/03/2022, 16:50:03] [deCONZ] Mordin: request 7: 200 OK
[07/03/2022, 16:50:03] [deCONZ] Mordin: error: TypeError: Cannot read properties of undefined (reading 'mode')
at Resource.patchSwitch (/usr/lib/node_modules/homebridge-deconz/lib/Deconz/Resource.js:659:26)
at new Resource (/usr/lib/node_modules/homebridge-deconz/lib/Deconz/Resource.js:248:14)
at Gateway.analyseResource (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:905:22)
at Gateway.analyseFullState (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:754:16)
at Gateway.poll (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:669:18)
at runMicrotasks (:null:null)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Gateway.heartbeat (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:256:9)

[07/03/2022, 16:50:03] [deCONZ] Mordin: error: TypeError: Cannot read properties of undefined (reading 'mode')
at Resource.patchSwitch (/usr/lib/node_modules/homebridge-deconz/lib/Deconz/Resource.js:659:26)
at new Resource (/usr/lib/node_modules/homebridge-deconz/lib/Deconz/Resource.js:248:14)
at Gateway.analyseResource (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:905:22)
at Gateway.analyseFullState (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:754:16)
at Gateway.poll (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:669:18)
at runMicrotasks (:null:null)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Gateway.heartbeat (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:256:9)

[07/03/2022, 16:50:03] [deCONZ] Mordin Gateway Settings: set Last Updated from "Mon Mar 07 2022 16:49:33" to "Mon Mar 07 2022 16:50:03"

deconz cli node missing

Hi,

I can't start the deconz cli anymore. I get the following error message:
root@homebridge:/homebridge# deconz
/homebridge/node_modules/.bin/deconz: 16: exec: node: not found

I'm running homebridge-deconz plugin in a docker container (oznu/homebridge) in the latest version from this week on a Synology NAS

I can't tell you, if this comes up due to the newest version of your plugin or from the last version of the docker container and their changes.

If you need further informations or some debug messages, please come back to me.

Thanks,
Roland

Cannot read properties of undefined (reading 'sat')

Device LIDL Livarno Lux HG06467 Christmas Stripe

homebridge-deconz v0.0.13

[2/18/2022, 4:32:34 PM] [deCONZ] Eingang Treppe: error: TypeError: Cannot read properties of undefined (reading 'sat')
    at CharacteristicDelegate.<anonymous> (/homebridge/node_modules/homebridge-deconz/lib/DeconzService/Light.js:154:42)
    at CharacteristicDelegate.emit (node:events:520:28)
    at CharacteristicDelegate.emit (/homebridge/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/Delegate.js:174:13)
    at CharacteristicDelegate._onSet (/homebridge/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/CharacteristicDelegate.js:441:10)
    at Saturation.emit (node:events:520:28)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1725:16
    at new Promise (<anonymous>)
    at Saturation.<anonymous> (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1723:14)
    at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
    at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)

how to expose sensors and switches separately

hey,

is it possible to expose only "sensors" OR "switches"?

i need a 2nd bridge with homebridge-deconz which only expose real sensors (eg. temp, contact, motion, smoke).

thank you!

Elko Super not working

I got the following error when using the plugin in a setup with Elko Super Thermostat:

[deCONZ] Ekraveien 18: error: TypeError: Cannot set properties of undefined (setting 'heatValue')
at Resource.patchThermostat (/homebridge/node_modules/homebridge-deconz/lib/Deconz/Resource.js:1190:34)
at new Resource (/homebridge/node_modules/homebridge-deconz/lib/Deconz/Resource.js:248:14)
at Gateway.analyseResource (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:904:22)
at Gateway.analyseFullState (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:754:16)
at Gateway.poll (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:669:18)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Gateway.heartbeat (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:256:9)

Switch service is Sensor?

I see that Switch service is extended by DeconzService.SensorsResource, is that correct?
Seems like a wrong mixup with Button service.

Thanks

Home+ no response

Hello,

i successfully added all the accessories to HomeKit and they work fine.
But I have an issue on the home+ app, even if all the accessories works fine they are all in a “not responding” status in home+. Can you help me with that ?

nothing is exposed to HomeBridge/Homekit

After initial setup absolutely no devices (lights/sensors/switches/groups) are exposed to homebridge or homekit. do i miss any necessary config?

{ "name": "ZigBee_newer", "hosts": [ "10.10.11.2" ], "platform": "deCONZ", "_bridge": { "username": "0E:64:43:39:03:B9", "port": 34214 } }

phoscon: request 1: http status 502 Bad Gateway

Hello,
homebridge-deconz v0.0.15, Home 1.4.1, NodeJS 16.14.2,
Since yesterday I have the below messages on the console:

[07/05/2022, 20:22:44] [deCONZ] phoscon: request 1: GET /
[07/05/2022, 20:22:44] [deCONZ] warning: phoscon: request 1: http status 502 Bad Gateway
[07/05/2022, 20:22:44] [deCONZ] phoscon: request 1: GET /
[07/05/2022, 20:22:44] [deCONZ] warning: phoscon: request 1: http status 502 Bad Gateway
[07/05/2022, 20:27:44] [deCONZ] phoscon: request 1: GET /
[07/05/2022, 20:27:44] [deCONZ] warning: phoscon: request 1: http status 502 Bad Gateway
[07/05/2022, 20:27:44] [deCONZ] warning: phoscon: request 1: http status 502 Bad Gateway
[07/05/2022, 20:27:44] [deCONZ] phoscon: request 1: GET /

The Homebridge and deCONZ are running on the same Raspberry pi 4.

[deCONZ] Phoscon-GW: warning:

05FB9B6CAE: potentially stale api key: {"create date":"2022-02-22T16:22:22","last use date":"2022-02-22T16:53:32","name":"homebridge-deconz#dockerpi"}
is this normal, or a config error

Additional light bulbs for ikea sensors and switches

Hi Erik!
I successfully switched to the deconz plugin!
All lights an sensors are working great! Thx for your work! Great Plugin!
One question: for certain switches and sensors i get an additional light 💡. It is for ikea products mainly but not for aqara sensors e.g
Whats that for?

Thx, Paul

Ikea Fyrtur not working

Hello,

I have a weird issue with my IKEA fyrtur and the plugin.

I cannot control them through HomeKit, it says opening or closing but nothing moves.

when I try with the home+ app it’s the same thing never works.

I also tried with the web phoscon app but they don’t move neither.

I tried with the Deconz gui app and there they work correctly when sending an open/close command.

I tried to remove them from HomeKit accessory cache and restated but still the same issue.

What is weird is that they were working correctly 3 days ago and I didn’t change anything in the configuration.

I have also some zigbee lights connected through the plugin and they work fine

can you help me with that ?

How do I expose Light Bulbs?

This may be a dumb question but I have read through all the documentation and I can not figure out how to expose my lightbulbs to homekit. Would someone be able to help me?

TypeError: this.updateConfig is not a function

4/22/2022, 8:48:09 PM] [deCONZ] Studio Pacman: error: TypeError: this.updateConfig is not a function
    at Outlet.update (/homebridge/node_modules/homebridge-deconz/lib/DeconzService/index.js:86:12)
    at Light.<anonymous> (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/index.js:81:21)
    at Light.emit (node:events:526:28)
    at Light.emit (/homebridge/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/Delegate.js:174:13)
    at Gateway.analyseFullState (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:859:34)
    at Gateway.poll (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:712:18)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Gateway.heartbeat (/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:258:9)

• innr SP 120
• homebridge-deconz v0.0.15
• homebridge 1.4.0

homebridge-hue -> homebridge-deconz

Just thought I'd share my experience of moving to homebridge-deconz from homebridge-hue

I set up a new homebrdge instance on a different machine, installed homebridge-deconz, pressed the 'authenticate app' button in phoscon - all good - I did get the settings not showing up the first time I tried:

In the original homebridge-hue install, I changed the config to false for lights, sensors etc

In eve, I selected the new deconz gateway, and expose, and then expose for the lights and sensors etc.
I then had to move the accessories to the correct rooms.

All seemed ok. I then installed homebridge-deconz on the original homebridge instance, and removed the temporary homebridge instance from homekit, having to move accessories to their correct rooms again.

I do seem to have an extra 'settings' accessory for every real accessory - haven't figured out how not to have those yet.

Aside from that, bit of a no-brainer.

Thanks again for your work!

New to HomeBridge, Phoscon, & Json coding

I'm having issues adding the code to the HomeBridge config. Whenever I add the code, and attempt to save, I get JSON errors and doesn't save. Both HomeBridge and Phoscon is running on the same server. I'm thinking I just have a "{" or a "[" in the wrong place but no matter what I try, I can't get it to save.

Can we disable Stateless Programmable Switch Service (logs)?

Hello, I just downloaded your new plugin and I am beginning to test it now.
For now everything seems working fine! Great work.

But one little thing is annoying to me: The logs of home bridge are filled with the Stateless Programmable Switch Service: "Button: Programmable Switch Event: Single Press" every minute. Can we disable this or switch off the logs?
So what is the sense for this Service, why is it enabled by default?

Thanks in advance!

set Expose to obtain an API key

Having trouble exposing on the gateway accessory - not sure where that is :-)

A quick how to or code sample anywhere?

Error with Window Covering device, but it does work

Switched one of my "homes" over to homebridge-deCONZ today and it went smooth as silk!

This is a very simple home, which is why I started with it.

Devices:

• 1 x Aqara wall switch (single rocker, with neutral, US style) - LUMI, Transmitter 1-gang, 09-06-2019
• 1 x Aqara wall switch (double rocker, with neutral, US style) - LUMI, lumi.switch.b2naus01, 0x00000019
• 3 x YookSmart roller shades - yooksmart, D10110, 20201120

There are errors for the roller shade devices which show up in the log. Pasted below. The device DOES work, though. The same device in homebridge-Hue did not generate any errors.

(These roller shade devices have been problematic in general. It is possible to make them work, though the open/closed/percentage reporting doesn't seem to be very reliable. One of the three behaves differently than the other two despite showing the same version. I assume this is all down to deCONZ.)

---

[04/02/2022, 21:31:27] [deCONZ] Office Shade 1: error: TypeError: service.update is not a function
at WindowCovering. (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/index.js:81:21)
at WindowCovering.emit (node:events:390:28)
at WindowCovering.emit (/usr/local/lib/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/Delegate.js:174:13)
at Gateway.analyseFullState (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:812:34)
at Gateway.poll (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:670:12)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Gateway.heartbeat (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:264:9)

Yooksmart D10110 shows as "Not Supported" -- Used to work

Upgraded to .12, after updating NodeJS, and three Yooksmart D10110 devices now show as "Not Supported" and their associated Scenes have disappeared.

I suspect this might be a deCONZ issue, because I saw that the deCONZ dependency had bumped up to 2.14.1, so I updated deCONZ as well. I think maybe I should have left it alone.

I did try rolling homebridge-deCONZ back to .11, and it still shows "Not Supported", which also points me to the problem being deCONZ.

Is it as easy to roll-back to the previous version deCONZ as it is for a Homebridge plugin? I suspect it is a bit harder... hah

Where to find ID of the Homebridge deCONZ migration resource link

Hi,

sorry for that question. I searched all Readmes but I could't find an answer.

Where can I find the ID of the migration resource link?

Thanks for help!

Cannot obtain an api key

I'm trying to link deconz with the plugin right now. but i can't tell if it works or not. when i start the api sharing in phoscon, apparently an api key can be obtained. but this is not written in the config. in my old homebridge hue plugin, such a users config was written. Also, no devices (sensors, lights, etc) are published in homebridge (even i share it in config).

homebride log:
Phoscon-GW: warning: 042DC3A196: potentially stale api key: {"create date":"2022-04-04T16:42:23","last use date":"2022-04-04T17:10:03","name":"homebridge-deconz#futro-s940"}

homebridge config.yaml

{
"bridge": {
"name": "Homebridge 3CB6",
"username": "xx:xx:xx:xx:xx",
"port": 53473,
"pin": "xx-xx-xx-xx",
"advertiser": "bonjour-hap"
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8088,
"platform": "config"
},
{
"name": "deCONZ",
"hosts": [
"192.168.1.101:2080"
],
"platform": "deCONZ"
}
]
}

Lights cooler than in Homebridge Hue - won't go above 454 mired?

I'm beginning to migrate to the Deconz plugin, and I was running it simultaneously with Homebridge-Hue to swap presets etc. over and test run a bit. During that time, all lights colour temperatures responded the same whether sending a request to change it via the 'Deconz hub' or the 'Hue plugin' hub. Set a light to max warm white, get 500 mireds in the Homebridge log/Phoscon GUI whether through Deconz or Hue hubs etc.

I then disabled the hue hub as a trial, and noticed that the lights colour temperatures now won't go as warm, and it seems that the hue hub was overriding this setting while both were running.

The maximum mired I can get through the Deconz plugin is now 454, whereas through Homebridge-Hue I can get 500, which as expected disables the cool white LED's on the fixtures. I can see evidence of this in the Phoscon app and the Homebridge logs.

Could this be related to the 'Brightness Adjustment Factor' for Adaptive Lighting in the Homebridge Hue plugin, which I have set to 55/100? Adaptive lighting is definitely cooler in Deconz now I disabled the hue hub, however this occurs whether adjusting temperature via the adaptive lighting colour wheel, or the regular colour temperature wheel. I'm unsure how the adjustment factor works so if it applies a colour shift to everything then it could be responsible but I'm guessing to be honest!

If it is it would be great if this feature could be added to the Deconz plugin at some point in the future :)

get worng meassage if try get api key

Hello,
I try activate this plugin.
1st start:

[27.4.2022, 17:55:19] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge 72C6) is running on port 51963.
[27.4.2022, 17:55:19] [deCONZ] hardware: x64
[27.4.2022, 17:55:19] [deCONZ] os: Ubuntu 21.10
[27.4.2022, 17:55:19] [deCONZ] ui server: listening on http://127.0.0.1:33717/
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: set Serial Number to "00212EFFFF0137C7"
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: set Manufacturer to "dresden elektronik"
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: set Model to "deCONZ / ConBee"
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: set Firmware Revision to "0.0.0"
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: set Software Revision to "2.14.1"
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: dresden elektronik deCONZ / ConBee gateway v2.14.1
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Expose to true
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Expose Lights to false
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Expose Sensors to false
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Expose Groups to false
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Expose Schedules to false
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Heartrate to 30 seconds
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Log Level to 2
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Restart to false
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Search to false
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Transition Time to 0.4 seconds
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Gateway Settings: set Unlock to false
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW Button: set Service Label Index to 1
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: warning: websocket communication error: 127.0.0.1:443: cannot connect: ECONNREFUSED
[27.4.2022, 17:55:20] [deCONZ] Phoscon-GW: websocket connection to ws://127.0.0.1:443 closed - retry in 15s
[27.4.2022, 17:55:21] [deCONZ] Phoscon-GW: set Firmware Revision from "0.0.0" to "0x26400500"
[27.4.2022, 17:55:21] [deCONZ] Phoscon-GW: warning: 001D6D3949: potentially stale api key: {"create date":"2022-04-27T14:54:06","last use date":"2022-04-27T15:18:11","name":"homebridge-deconz#pi386"}
[27.4.2022, 17:55:21] [deCONZ] Phoscon-GW: warning: 131EA6A729: potentially stale api key: {"create date":"2022-04-27T14:46:31","last use date":"2022-04-27T14:51:52","name":"homebridge-deconz#pi386"}
[27.4.2022, 17:55:21] [deCONZ] Phoscon-GW: warning: CF4F00EF90: potentially stale api key: {"create date":"2022-04-20T18:44:17","last use date":"2022-04-20T19:02:26","name":"homebridge-deconz#pi386"}
[27.4.2022, 17:55:21] [deCONZ] 1 gateways
[27.4.2022, 17:55:21] [deCONZ] created debug dump file /var/lib/homebridge-test/homebridge-deconz.json.gz
[27.4.2022, 17:55:35] [deCONZ] Phoscon-GW: websocket connected to ws://127.0.0.1:8088
[27.4.2022, 17:56:21] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press

and get no ligths :-(
and yes the phoscon app have active "accept new app"

regards

Enhancement: dew point characteristic for temperature/humidity sensors?

Hello again,

For me it would be a great benefit to have an additional characteristic „dew point“ for all temperature/humidity sensors, which must be calculated from temperature and humidity (e.g. for deciding whether it makes sense to open windows to get rid of humidity).

Not sure whether that can be done within the plugin - before I did that via FHEM, but I am trying avoid FHEM.

Would that be possible?

Best regards
Thomas

Observations as of 0.13

I love the leaner (since I don't use Hue) Homebridge-deCONZ plugin! And it is becoming completely usable for daily use much more rapidly that I thought, so thank you very much!

I have noticed a couple of things, that I thought I might post about.

1. EXPOSE LIGHTS - I'm not sure if I am understanding this correctly, but I thought if I left the main EXPOSE 'ON' and turned EXPOSE LIGHTS to 'off' the light devices would either disappear or become No Response in HomeKit. When I did this, they never went away. The lights continued to show up in Home app and be function even after waiting 30 minutes. When I turned the main EXPOSE to 'off' everything disappeared, and I had to re-name, re-room re-scene all devices when I turned the main EXPOSE back 'on'.

2. Adding devices - One of the nice benefits of the new plugin is not needing to restart Homebridge when you add devices! I've noticed a bit of a drawback, too, though... When I add devices in Phoscon, I always name them of course, and in the past, that naming carried over to HomeKit because by the time they were exposed to HomeKit, the renaming was complete. The new plugin exposes them SO fast that I haven't yet had a chance to rename them, so HomeKit gets the generic name. I added a bunch of temperature sensors at one time, renaming them in Phoscon, like I used to do, but then when I went to Home app, I had 10 new temperature sensors, which I would need to rename again, but worse, I didn't know which one was which, so I had to delete everything and go back and re-add them 1-by-1, renaming them twice, once in Phoscon, then again in Home app. Is there a better way, am I doing something wrong?

Crash and loosing setting in Home app

Hi Erik!

I'm quite desperate. About some hours ago I lost all my settings in home app for the second time and I have to reconfigure all may Lights, Sensors and Switches ... :(
I switched from hue- to deconz-plugin (50+ accessories ... ) before and generally it was working flawless.
Homebridge-deconz runs on a dedicated raspberry pi in a child bridge no other plugins except home bridge-ui and the deconz software.

I lost all my home app settings 2 times:

1st incident:

• i was updating raspberry pi software ( sudo npm -g update / sudo hb-servoce update-node ))
• i restarted homebridge using homebridge-ui
• all settings were gone ...

2nd incident:

• i updated my Synology NAS (that shouldn't effect the raspberry)
• after updating I checked homebridge-ui and i saw some errors in the log, here an example:

�[37m[12.4.2022, 20:50:15] �[39m�[36m[deCONZ]�[39m �[31merror: RangeError: 00212EFFFF0101A8-G5: unknown device ID�[39m
�[31m�[0m�[90m    at Gateway.addAccessory (/usr/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:505:13)�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at DeconzPlatform.accessoryRestored (/usr/lib/node_modules/homebridge-deconz/lib/DeconzPlatform.js:241:19)�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at DeconzPlatform.emit (node:events:526:28)�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at DeconzPlatform.emit (/usr/lib/node_modules/homebridge-lib/lib/Delegate.js:174:13)�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at DeconzPlatform.configureAccessory (/usr/lib/node_modules/homebridge-lib/lib/Platform.js:416:10)�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at /usr/lib/node_modules/homebridge/src/bridgeService.ts:328:25�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at Array.filter (<anonymous>)�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at BridgeService.restoreCachedPlatformAccessories (/usr/lib/node_modules/homebridge/src/bridgeService.ts:288:69)�[39m�[31m�[0m�[39m
�[31m�[0m�[90m    at ChildBridgeFork.startBridge (/usr/lib/node_modules/homebridge/src/childBridgeFork.ts:170:24)�[39m�[31m�[0m�[39m

Here is the full log:
homebridge.log

• i restarted home bridge using the ui plugin
• all settings gone ... :( :(

I don't know what I do wrong, I tried to describe what happened, if you need further information, please tell me

hopefully you can give me advice, since this happened 2 times now and i'm really frustrated spending hours in reconfiguring everything.

thanks in advance

Paul

Cannot connect to deconz 2.17.00

Cannot connect to deconz 2.17.00 running on same device. I get the following errors:
[deCONZ] warning: heartbeat 0, drift 265
[16/06/2022, 12:59:18] [deCONZ] warning: 127.0.0.1:4530: not a deCONZ gateway - retrying in 60s

I have tried with different host addresses including: the actual local IP address and localhost. I have confirmed I am using the correct port. (Installed deconz in homebridge raspberry pi using hb-config)

api error 1: unauthorized user

Hi @ebaauw ,

I'm trying to setup my Raspbee II in Homebridge. With some struggles I have my Raspbee working and I'm able to add switches and lights in the Phoscon GUI. So that's great.

Now I'm trying to connect the "Homebridge Deconz" plugin but somehow I'm not getting it connected to the API.
In the log console I'm getting the error:
[deCONZ] Phoscon-GW: warning: request 14: api error 1: unauthorized user

My config looks like this:

{
    "name": "deCONZ",
    "hosts": [
        "192.168.68.114:4530"
    ],
    "platform": "deCONZ"
}

I'm not sure how or where to set "Expose". (Set Expose on the Gateway Settings service of the gateway accessory to retry obtaining an API key)
How does this work?

I hope you can help me out on this.

Thank you very much.

Side-by-side with Homebridge-Hue during testing

I have two "homes" where I'm using Homebridge-Hue... One is quite a bit more simple than the other, so I figured I would start testing Homebridge-deCONZ there first.

I'm not as technical as some others here, but I'm hoping to maybe be of some help. But I want to make sure I understand the current usage scenario first.

I have hb-Hue in a child bridge, and I've also put hb-deCONZ in a child bridge. Can I run hb-deCONZ and have it connect to the same ConBee II as hb-Hue is connected to at the same time and exposing the same devices? Or will that break something?

I know that hb-deCONZ doesn't yet fully expose devices, they're just there to test and observe their characteristics in a more advanced HomeKit app. I'm looking forward to that, to see what characteristics my devices have.

Thanks for your work on this! I'm really excited about it.

[deCONZ] Roomname: warning: assertion failed

Hi,

since today i am getting the mesage "[deCONZ] Roomname: warning: assertion failed" in the log. Do you have any suggestions to this message? Wasn`t there before.

Devices are not added, only two buttons

• When trying to add two bridges only two buttons are shown (see screenshots)
• Second screenshot shows the homebridge message
• homebridge-hue is installed in parallel

Bug? 🐞

Cannot expose a group without also exposing all scenes from the group

I'm able to expose all groups, and then hide the individual groups that I do not want exposed in HomeKit. However, when I expose groups that contain scenes, I also see that all scenes in that group are exposed as switches. When I uncheck expose on the unwanted individual scene switches from an exposed group, the whole group is then also removed from HomeKit.

My use case is multiple Hue Downlights that I'd like to expose as a single bulb to HomeKit. They are grouped in deCONZ, but also have scenes associated. I've hidden (un-exposed) the individual bulbs, but can't expose the group without also exposing the scenes, which is not what I want.

Any workaround for this?

noResponse false/true

In the wiki, it mentions an advanced feature "noResponse" with the description "Report unreachable lights as No Response in HomeKit."

Would this apply to sensors as well?

Expose devices as fans, switches etc

Good Afternoon, is it possible to expose the devices from Deconz in Homekitas fans and switches, rather than lights?

Danfoss Ally thermostat: Cannot set properties of undefined (setting 'heatValue')

Hello Erik,
I have 2 Danfoss Ally thermostat, working with DECONZ & Homebridge Hue. Now I get the below message in Homebridge Deconz:

[13/02/2022, 20:23:08] [deCONZ] HB-deCONZ: error: TypeError: Cannot set properties of undefined (setting 'heatValue')
at Resource.patchThermostat (/usr/local/lib/node_modules/homebridge-deconz/lib/Deconz/Resource.js:1192:34)
at new Resource (/usr/local/lib/node_modules/homebridge-deconz/lib/Deconz/Resource.js:248:14)
at Gateway.analyseResource (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:904:22)
at Gateway.analyseFullState (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:754:16)
at Gateway.poll (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:669:18)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Gateway.heartbeat (/usr/local/lib/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:256:9)

And they don't show up in Homekit

Adaptive lighting: 'Characteristic Value Transition Control': characteristic was supplied illegal value: undefined

With homebridge deconz and deCONZ 2.14.01, when adaptive lighting is enabled, I pick up a bunch of errors from a set of lights that all follow the same pattern.
Homebridge Deconz is running as a child bridge.

Bulbs are different manufacturers (Tuya and Ikea at least two of them) - might possibly relate to 'special effects' options on them?

[07/03/2022, 18:23:50] [homebridge-deconz] This plugin generated a warning from the characteristic 'Characteristic Value Transition Control': characteristic was supplied illegal value: undefined. See https://git.io/JtMGR for more info.
[07/03/2022, 18:23:50] [homebridge-deconz] Muservatory Drums Light: Adaptive Lighting: disabled
[07/03/2022, 18:23:50] [homebridge-deconz] Muservatory Drums Light: error: TypeError: Cannot read properties of undefined (reading 'generateControl')
at CharacteristicDelegate.getter [as _getter] (/usr/lib/node_modules/homebridge-deconz/lib/DeconzService/Light.js:209:40)
at CharacteristicDelegate._onGet (/usr/lib/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/CharacteristicDelegate.js:354:26)
at CharacteristicValueTransitionControl.emit (node:events:520:28)
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1592:14
at new Promise ()
at CharacteristicValueTransitionControl. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1590:12)
at step (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
at Object.next (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
at /usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
at new Promise ()

No Eve history for Aqara Temp/Humidity/Pressure sensor

Hello,

yesterday I set up a new homebridge instance and used homebridge-Deconz the first time. Everything works so far, but I cannot see the history for my Aqara sensors in Eve app, which is an essential feature for me. Is there a way to activate it?

Best regards

Any way to re-sync names from deCONZ to HomeKit?

Great plugin!

Just added some Hue lights and dimmer switches but they appear in HomeKit with the name deCONZ assigns when the device is found rather than what I rename it to in the deCONZ app.

Is there any way to have the plugin sync the current accessory names from deCONZ?

Thanks

Ubisys Universal Dimmer D1-R, 1137 is not working properly

I use deconz version 2.14.01 and homebridge-deconz version 0.0.14
If you are using a Ubisys Universal Dimmer D1-R, 1137, you always get the following entry in the log file and the energy consumption display in the Eve Home app does not work.

[17/03/2022, 09:45:44] [deCONZ] SmartHome S&K Button: Programmable Switch Event: Single Press
[17/03/2022, 09:45:44] [deCONZ] Ganglicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:45:44] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:45:46] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:45:49] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:45:53] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W [min]
[17/03/2022, 09:45:56] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:45:59] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W [min]
[17/03/2022, 09:45:59] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:01] [deCONZ] Ganglicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:02] [deCONZ] Ganglicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:03] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:05] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:10] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:12] [deCONZ] Ganglicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:13] [deCONZ] Ganglicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:13] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:16] [deCONZ] Ganglicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:17] [deCONZ] Ganglicht: set Current Consumption from 12000 W to 0 W [min]
[17/03/2022, 09:46:18] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W [min]
[17/03/2022, 09:46:18] [deCONZ] Schlafzimmerlicht: set Voltage from 233 V to 234 V
[17/03/2022, 09:46:23] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:27] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:29] [deCONZ] Ganglicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:30] [deCONZ] Ganglicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:30] [deCONZ] Schlafzimmerlicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:36] [deCONZ] Ganglicht: set Current Consumption from 0 W to 12000 W [max]
[17/03/2022, 09:46:37] [deCONZ] Ganglicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:42] [deCONZ] Schlafzimmerlicht: set Current Consumption from 12000 W to 0 W
[17/03/2022, 09:46:44] [deCONZ] SmartHome S&K Button: Programmable Switch Event: Single Press

The error did not occur on homebridge-hue v0.13.38.
Based on the data I provided, would it be possible for you to solve the failure?
I want to say thank you for the great plugin and for the work you did already!
Looking forward to get an answer from your side soon.

Characteristic was supplied illegal value: number -127 exceeded minimum of 100

If have just installed the homebridge-deconz plugin and added a few lights and an IKEA Tradfri motion sensor and on/off switch. After about 2 to 3 minutes after startup of homebridge, I get this error:

[10/04/2022, 14:12:43] [homebridge-deconz] This plugin generated a warning from the characteristic 'Status': characteristic was supplied illegal value: number -127 exceeded minimum of 100. See https://git.io/JtMGR for more info.
[10/04/2022, 14:12:43] [homebridge-deconz] Error: 
    at Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
    at Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2045:14)
    at Characteristic.<anonymous> (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1582:21)
    at step (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
    at Object.next (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
    at /usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
    at new Promise (<anonymous>)
    at __awaiter (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:113:16)
    at Characteristic.handleGetRequest (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:689:38)
    at Characteristic.<anonymous> (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2207:22)
    at step (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
    at Object.next (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
    at /usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:117:75
    at new Promise (<anonymous>)
    at __awaiter (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:113:16)
    at Characteristic.toHAP (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Characteristic.js:1328:38)
[10/04/2022, 14:12:43] [deCONZ] TRÅDFRI Bewegungsmelder History: send data: 00
[10/04/2022, 14:12:43] [deCONZ] VPIR test Bewegung History: send data: 00
[10/04/2022, 14:12:43] [deCONZ] TRÅDFRI Bewegungsmelder History: get History Entries: return "AA=="

I get this error more than once, but I haven't figured out when exactly, because even when I don't control anything, the error gets called.

Additionally all homebridge accessories are extremely slow after installing this plugin, they stay in "updating" for about one minute and after that they show the corresponding value. The same minute waiting is present whey I try to control anything via homebridge, although the message of control pops up the second it responds again.

Light Groups which are not dimmable showing as dimmable

Apologies if this isn't the right place to inquire about this. I have a suspicion that this is something Phoscon should be in charge of, because I assume the plugin just passes the info provided to it along to HomeKit.

In Phoscon, I've created a Group of 12 lights which are all identical and are simple on-off mains wall switches. (Wall switches exposed as lights.)

I've never used Groups before and it was great. I put the light switch for every room in the basement into the Group, and I can turn off the entire basement with one tap. But I still have all the individual rooms available as well. Previously, I made a scene for all the light switches, and it did the same thing, but was a scene rather than a "device" and the lights all flicked off in a random cascading pattern. It was kind of futuristically cool, actually, but I still prefer the Group method because it comes through as a device of its own, and the lights all operate in perfect unison.

The issue is that the Group device comes through as a dimmable light, rather than just an on-off light. Those same switches would expose as a simple on-off light if they were on their own.

Originally it was coming through as an Adaptive Lighting "light" but I did turn that off. But I can't figure out how to make it just on-off rather than dimmable. Currently, it shows as "100%" (rather than ON) when its on, and OFF when off.

If this is just because that is how Phoscon makes the Group and there is no real way around it, no worries, at least I'll know and I can stop looking for a solution. hah

Installation

Do you have to uninstall previously installed HomeBridge-hue plugin? My phoscon website doesn't seem to take the new plugin but shows version of homebridge-hue plugin under "homebridge version"

stopping deConz installation if make fails.

Hi,

I am likely at the wrong spot here, but if so I guess it is also the best place to redirect me.

If I understand it correctly you may run into the situation where the make command fails when you try to install the deConz package via "sudo hb-config" on a fresh install of the Homebridge raspberry installation.

Dresden-elektronik had a ticket open for that too dresden-elektronik/raspbee2-rtc#13

So my suggestion is rather than continuing with the installation as nothing happen, to either stop the installation of the package. Or to provide more information at the end of the installation (e.g. in the blue screens of hb-config) on what happen or how to address this.

The Homebridge image I used is the latest image that is currently installed by the "Raspberry Pi Imager".

example logs (This is from the rerun of the install as i had some network issues):

pi@homebridge:~ $ sudo hb-config
Setting up for RaspBee...
Get:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Get:2 http://archive.raspberrypi.org/debian bullseye InRelease [23.5 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages [13.2 MB]
Get:4 http://archive.raspberrypi.org/debian bullseye/main armhf Packages [250 kB]
Fetched 13.5 MB in 1min 23s (162 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
31 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
build-essential is already the newest version (12.9).
The following additional packages will be installed:
libi2c0 read-edid
Suggested packages:
libi2c-dev python-smbus
The following NEW packages will be installed:
i2c-tools libi2c0 raspberrypi-kernel-headers read-edid
0 upgraded, 4 newly installed, 0 to remove and 31 not upgraded.
Need to get 27.8 MB of archives.
After this operation, 181 MB of additional disk space will be used.
Get:1 http://archive.raspberrypi.org/debian bullseye/main armhf raspberrypi-kernel-headers armhf 1:1.20220120-1 [27.7 MB]
Get:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libi2c0 armhf 4.2-1+b1 [10.4 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf i2c-tools armhf 4.2-1+b1 [78.0 kB]
Get:4 http://ftp.gwdg.de/pub/linux/debian/raspbian/raspbian bullseye/main armhf read-edid armhf 3.0.2-1.1 [14.9 kB]
Fetched 27.8 MB in 39s (713 kB/s)
Selecting previously unselected package libi2c0:armhf.
(Reading database ... 45281 files and directories currently installed.)
Preparing to unpack .../libi2c0_4.2-1+b1_armhf.deb ...
Unpacking libi2c0:armhf (4.2-1+b1) ...
Selecting previously unselected package i2c-tools.
Preparing to unpack .../i2c-tools_4.2-1+b1_armhf.deb ...
Unpacking i2c-tools (4.2-1+b1) ...
Selecting previously unselected package raspberrypi-kernel-headers.
Preparing to unpack .../raspberrypi-kernel-headers_1%3a1.20220120-1_armhf.deb ...
Unpacking raspberrypi-kernel-headers (1:1.20220120-1) ...
Selecting previously unselected package read-edid.
Preparing to unpack .../read-edid_3.0.2-1.1_armhf.deb ...
Unpacking read-edid (3.0.2-1.1) ...
Setting up libi2c0:armhf (4.2-1+b1) ...
Setting up read-edid (3.0.2-1.1) ...
Setting up raspberrypi-kernel-headers (1:1.20220120-1) ...
Setting up i2c-tools (4.2-1+b1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u2) ...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 52260 100 52260 0 0 51691 0 0:00:01 0:00:01 --:--:-- 51742
Selecting previously unselected package wiringpi.
(Reading database ... 100070 files and directories currently installed.)
Preparing to unpack /tmp/wiringpi-latest.deb ...
Unpacking wiringpi (2.52) ...
Setting up wiringpi (2.52) ...
Processing triggers for man-db (2.9.4-2) ...
############################################################################################################################################ 100.0% #=O=# # #
Archive: /tmp/raspbee2-rtc.zip
6fabff2ee826c004dfb17eb4a5df115e262a0157
creating: /tmp/raspbee2-rtc-master/
inflating: /tmp/raspbee2-rtc-master/LICENSE
inflating: /tmp/raspbee2-rtc-master/Makefile
inflating: /tmp/raspbee2-rtc-master/README.md
inflating: /tmp/raspbee2-rtc-master/rtc-pcf85063.service
checking deb package dependencies...
i2c-tools
build-essential
raspberrypi-kernel-headers
download rtc-pcf85063.c for kernel version 5.10 ...
curl -O --max-time 10 https://raw.githubusercontent.com/torvalds/linux/v5.10/drivers/rtc/rtc-pcf85063.c
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 16326 100 16326 0 0 21710 0 --:--:-- --:--:-- --:--:-- 21710
build rtc module...
make -C /lib/modules/5.10.63+/build M=/tmp/raspbee2-rtc-master modules
make[1]: *** /lib/modules/5.10.63+/build: No such file or directory. Stop.
make: *** [Makefile:17: build] Error 2
install rtc module...
make[1]: *** /lib/modules/5.10.63+/build: No such file or directory. Stop.
could not install rtc module file (did you run make?)
make: *** [Makefile:42: install] Error 1
--2022-02-13 13:59:27-- http://phoscon.de/apt/deconz.pub.key
Resolving phoscon.de (phoscon.de)... 144.76.96.194
Connecting to phoscon.de (phoscon.de)|144.76.96.194|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1692 (1.7K) [application/octet-stream]
Saving to: ‘STDOUT’

•                                100%[=====================================================================>]   1.65K  --.-KB/s    in 0s      
  

2022-02-13 13:59:27 (16.0 MB/s) - written to stdout [1692/1692]

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
OK
Get:1 http://phoscon.de/apt/deconz bullseye-beta InRelease [2,876 B]
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Get:4 http://phoscon.de/apt/deconz bullseye-beta/main armhf Packages [733 B]
Fetched 3,609 B in 5s (706 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
31 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:

homebridge-deconz spamming logfile

Hey,

the deconz plugin is spamming my log file every minute. Here is a snippet of it but it goes on much longer, since it pushes the message every minute with no breaks:

[09/04/2022, 11:59:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:00:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:01:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:02:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:02:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Double Press
[09/04/2022, 12:03:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:04:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:05:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:06:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:07:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press
[09/04/2022, 12:08:35] [deCONZ] Phoscon-GW Button: Programmable Switch Event: Single Press

Hope someone can clarify why this is happening and how to stop it.

Setting websocket server port

Hi!

I have configured deconz on a non-standard websocket port, using 8443. It seems 443 is hardcoded in this project, I didn't see a config option for it. It would be useful to add a config option for it.

Alternatively, it can also be discovered from the deconz config endpoint: http://127.0.0.1/api/<ID>/config which contains a websocketport value

EDIT:

homebridge-deconz/cli/deconz.js

Lines 703 to 704 in 421d6d8

	const { websocketport } = await this.client.get('/config')
	options.host = this.client.host + ':' + websocketport

hmm it seems it's being set. I'll need to take a closer look.

HB-deCONZ: unlock gateway to obtain API key

Nice work, I was using Homebridge-Hue, you made a great job. I wanted to switch to Homebridge DECONZ, but no luck.

I have the Homebridge and Deconz installed on the same system. The config JSON is setup to discover the Deconz Gateway. But i receive the below message:
[13/02/2022, 19:04:21] [deCONZ] 1 gateways
[13/02/2022, 19:04:21] [deCONZ] HB-deCONZ: request 1: POST / {"devicetype":"homebridge-deconz#homebridge"}
[13/02/2022, 19:04:21] [deCONZ] HB-deCONZ: warning: request 1: api error 101: link button not pressed
[13/02/2022, 19:04:21] [deCONZ] HB-deCONZ: unlock gateway to obtain API key - retrying in 15s
[13/02/2022, 19:04:36] [deCONZ] HB-deCONZ: request 2: POST / {"devicetype":"homebridge-deconz#homebridge"}

How do I obtain the API key?
Thanks for you feed-back