apollon77/iobroker.homekit-controller

Pair and control HomeKit devices directly

ioBroker.homekit-controller

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

homekit-controller adapter for ioBroker

This adapter allows you to pair and directly control devices with the "works with HomeKit" Logo that cna be used with Apple Home. The adapter supports IP/WLAN devices and also BLE (Bluetooth LE) devices. The adapter works completely local in your network.

The adapter is not ...

... offering ioBroker devices or states to be controlled by an Apple Home app/system. If you want this direction please use the yahka adapter.

... supporting Thread "only" based devices. The Homekit Thread specifications are not yet publicly available. From the current knowledge all devices on the market also support BLE or WLAN, so the adapter will simply not use Thread but other ways to communicate.

How to use the adapter

The adapter listens for available devices in your network.

There are three "types" of detected devices:

• Unpaired devices are devices that are discovered and available to pair. Some basic states are generated for these devices in ioBroker which contains some informational and administrative states. By providing the PIN you can pair these devices to this adapter instance (see "pairing" section below)
• Paired with this instance devices can be fully controlled, will update state values in "real time" using subscriptions (IP devices only) and data polling interval. The device can also be "unpaired" from this instance (see section below).
• Paired with someone else devices are devices that are discovered but already paired with some other controller. These are logged in debug mode but no states are created for them. If you want to use them with ioBroker you first need to unpair them from their current controller (sometimes only possible with a hard reset or such - refer to manual) and after this they should be shown as "unpaired device".

After pairing the supported states are read out from the device and objects and states are created. All known data points defined in the HomeKit standard should be named in a human-readable way. If you see UUIDs as names then the device manufacturer added self-defined data. If it is known what they provide this could be added to the adapter (e.g. as the ones added for Elgato devices) to show up as named in next version.

The data points are created with proper states and, if available, also correct roles. Else generic roles are used.

Identify information

Devices that are not paired with any controller have an admin.identify state that can be triggered with true. In this case the relevant device should identify itself (e.g. a lamp should blink or such, so that it can be identified). This function is only available as long as the device is not paired with an controller.

Pairing information

To pair the device with this adapter instance you need to provide the pin which is shown on the device, or a lable or such. The PIN is 8 numbers beside a QR-Code. The numbers need to be entered in the format 123-45-678 (also when the dashes are not printed on the label or shown on screen!)

Right now the PIN needs to be entered into the admin.pairWithPin state - an Admin UI will follow soon.

After pairing the device to this instance it is NOT possible to also add the device to Apple Home app or such in parallel.

There might be cases that are still problematic for pairing because I was only able to test with a very few devices, so please report issues, and I will support with instructions to get the needed debugging data.

Unpairing information

To unpair just trigger the admin.unpair state with "true" and the unpair process will be executed - an Admin UI will follow soon.

Special notes for use of IP devices

IP devices are discovered using UDP packages, so your host need to be in the same network as the devices. There is currently no real way around it because the MDNS record used contains important information for the pairing process. Especially when using Docker you need to find ways (host mode, macvlan, ...) to see the UDP packages.

The main challenge for WLAN based IP devices without controls or a screen is to get them into your WLAN network. Most likely there is a manufacturer specific Mobile app to add the devices initially to your network. If this initial process also pairs the device with Apple Home you might need to unpair it afterwards (e.g. https://www.macrumors.com/how-to/delete-homekit-device/). After this it should be in your WLAN and available to pair with this adapter.

Once an IP device is paired and the IP stays the same the adapter directly connects to the device on start. SO best pin the IP in your router. If the IP has changed then the connection should be established on next discovery and the IP should be updated.

Special notes for use of BLE devices

By default, BLE is disabled in the adapter settings. After enabling the devices that are reachable can be discovered.

Because of the limitations of Bluetooth devices no "real-time updates" of state changes are available. The devices will report "important state changes" (e.g. the "On" state changes) by special packages that will trigger an immediate data refresh. Additionally, data are refreshed in the defined data polling intervals. Do not set them too short!

After a restart of the adapter bluetooth devices can not be connected directly - the system needs to receive at least one discovery package from the device to get the needed connection details. This mean BLE devices might be available a bit delayed.

Troubleshooting

Known incompatible devices

If you have issues pairing the device with this adapter please try to pair it with the normal iOS Apple Home App. If this does not work then something is weird with the device and then also this adapter can not help. Pot try a reset, but else there is not chance.

This is currently that way for some Tado Door Locks as example. They need to be paired using the Tado App which is somehow registering the device into Apple Home, but not via an official pair process.

Additional also Nuki 3 Locks (BLE) are not possible to pair because they use Hardware Authentication components that are not publicly documented by Apple.

For Netatmo a user found out how pairing could be possible when it had issue. See #233 (comment)

Other potential issues to check before opening a ticket

for BLE devices

• If you have issues that the BLE connection do not work our you get Errors when the adapter tries to initialize the BluetoothLE connection, please first run iobroker fix to make sure that all permissions and needed capabilities are set correctly.
• If this do not help please check https://github.com/noble/noble#running-on-linux
• Please make sure that your system is up-to-date including kernel apt update && apt dist-upgrade
• Try to reset the relevant BLE device with e.g. sudo hciconfig hci0 reset
• For issues also provide the output of uname -a and lsusb
• Low level BLE device log can be obtained using sudo hcidump -t -x >log.txt (in a second shell additionally to run the adapter)

General advices

• Does the device have a Pairing Mode or such that needs to be activated first? But also read the manual careful, maybe the Pairing mode is for some other legacy protocol or bridge but not Apple Home.
• Basically if the error "pair-setup characteristic not found" pops up while trying to pair then the device do not support pairing via Homekit in its current state. The adapter cn not do anything then!
• Please make sure to enter the PIN mit Dashes in the form "XXX-XX-XXX". Other formats should be declined by the library already by an error, but just to make sure

Debugging

When you have issues and want to report an Issue (see below) then enhanced debug log is always helpful.

• Please stop the adapter instance in iobBroker Admin
• Open a shell on the relevant server
• Manually start the adapter using DEBUG=hap* node /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js 0 --debug --logs
• Then do whatever produces the error and grab the log from the shell and post with the Issue.
• post the console log also in the issue. This will generate a log on protocol level.
• Additionally, find the relevant object in Admin "Objects" tab and click the pencil on right and provide the JSON of the object.

Resources and Links

• Resource that tries to decode Elgato special states: https://gist.github.com/simont77/3f4d4330fa55b83f8ca96388d9004e7d

TODO

• check how the adapter works with buttons (they do not have a state, and I do not own such a device. need support for this)
• look into supporting video devices
• look into support devices that offer images (method is there but never saw it in action)

Changelog

0.5.10 (2024-01-26)

• (bluefox) Fix user interface

0.5.9 (2023-11-23)

• (Apollon77) Prevent crash when a single value is returned as error status
• (Apollon77) send booleans always as 0/1 to make sure all devices handle it correctly
• (Apollon77) Update dependencies

0.5.8 (2023-02-27)

• (Apollon77) Update Noble to address CPU/RAM issues

0.5.7 (2023-01-27)

• (Apollon77) Added support for Ikea Dirigera Hubs and other devices with very log Accessory IDs
• (Apollon77) Optimize handling of configuration changes
• (Apollon77) Optimize connection state handling

0.5.6 (2023-01-05)

• (Apollon77) Upgrade noble library

0.5.5 (2022-12-31)

• (Apollon77) Downgrade noble library again

0.5.3 (2022-12-22)

• (bluefox) Corrected active TAB Background

0.5.2 (2022-12-22)

• (bluefox) Updated GUI packages
• (Apollon77) Upgraded noble BLE library

0.5.1 (2022-06-10)

• (Apollon77) Optimizations for BLE connections

0.5.0 (2022-06-08)

• (Apollon77) Add Connection identifier for Admin object list
• (Apollon77) Count polling errors and reinitialize device connection when too many errors occur
• (Apollon77) Optimize adapter startup to prevent double initialization of devices

0.4.4 (2022-05-06)

• (Apollon77) Add Host header to HTTP devices to prevent issues with some devices
• (Apollon77) Fix several edge case issues

0.4.3 (2022-01-25)

• (Apollon77) make sure all connections get closed on reconnect

0.4.2 (2022-01-25)

• (Apollon77) Reset HTTP connection if timeouts happen on data polling

0.4.1 (2022-01-21)

• (Apollon77) Optimize close of connections on adapter stop

0.4.0 (2022-01-21)

• (Apollon77) performance increase by using persistent connections to IP devices and many more optimizations
• (Apollon77) Only use one queue for all BLE devices
• (Apollon77) Store pairing data directly after pair
• (Apollon77) Optimize handing of concurrent requests
• (Apollon77) Optimize value update handling and better detect stale data to force an update on next polling

0.3.3 (2021-10-26)

• (bluefox) Fix the Discovery checkboxes

0.3.1 (2021-10-25)

• (Apollon77) Fix datatype of lastDiscovered state

0.3.0 (2021-10-24)

• (Apollon77) BREAKING CHANGE: All channel names will be changed and a number gets added at the end of the name. Please manually delete the ones without such a number

0.2.0 (2021-10-23)

• (bluefox) Add Admin UI
• (Apollon77) Store pairing data additionally in an instance directory and retry them on start if objects where deleted or such
• (Apollon77) Add info.lastDiscovered state with a timestamp to allow manual cleanup of devices that are paired somewhere else then with the adapter instance (because such objects would currently not be deleted)
• (Apollon77) Add missing device and channel objects
• (Apollon77) Always convert bool-type to boolean because it might be numbers coming from the devices
• (Apollon77) sort devices for Admin UI to have those with available actions on top
• (Apollon77) Enhance error messages
• (Apollon77) Adjust some roles

0.1.0 (2021-10-19)

• (Apollon77) Optimizations and added some Elgato states
• (Apollon77) Initial GitHub release

0.0.x

• (Apollon77) Initial commit and Alpha GitHub testing

License

MIT License

Copyright (c) 2021-2024 Ingo Fischer [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.homekit-controller's Issues

[Feature request] Implement queue to avoid overload of Homekit Bridges/Devices

Background:

The HomeKit-Controller sends every state change immediately to the corresponding Homekit devices.
In most cases this works absolutely perfect and I am very happy yo have this adapter :)

But we also have situation where where homekti devices are used as a bridge, for example integrations to 1-home, loon or equal.
In that case not 1 (or maybe 3) states are attached to 1 HomeKit device, but we can for example implement up to 149 lights.
(example 1-home to KNX, alle lights are read from KNX and exposed as 1 Homekit device with al their relate light states.

Issue:
When multiple states are switched, like all lights in the mentioned scenario above, the Homekit gateway (not this adapter!) hangs up and get session timeouts. This is a well known behavior and no relation with this adapter.
We can reproduce this situation by adding the Device directly to HomeKit instead of this adapter, switching than all lights also cause a hangup.

Possible solution:
I execute multiple stress tests to identify the problem and how we could avoid that. By doing that, I figured out that an delay of 200-300ms between the switch actions helps to avoid this situation.

Feature request:
Add capability to the adapter if multiple states are triggered for 1 Homekit connected device/bridge a queue should be handled by (most happy if configurable) 200-300 ms between the different switch states.

I was able te reproduce a 100% stable situation by scripting, instead of change all the states at once having a 200ms between each change.

Why should we do that:
When integrating these kind of states to Alexa, google or HomeKit as example and you say "Turn all the lights of".... its just fired to the bridge in milliseconds which cause the connection to fail. Having this kind of queuing implemented would avoid this situation.

IP Discovery with mulithost environment

I'm trying to connect the Aqara FP2 presence Sensor. My setup is a master docker iobroker host in my trunk vlan via macvlan and an iobroker mulithost slave docker instance in an iot vlan also via macvlan network Interface (only this network adapter is connected to this host) where also the sensor is connected to. The homekit controller adapter instance is running on the slave host in the iot net.
Sadly the discovery of the instance only shows devices of the masters network.

Is this the expected behavior?
Or is it possible to change the discovery subnet or change the network Interface which the discovery is using?

Versions:

• Adapter version: 0.5.8
• JS-Controller version: 5.0.7
• Node version: 18.16.1
• Operating system: Debian bullseye docker

Aqara Hub E1 no human-readable names

Describe the bug
The devices from the Aqara hub E1 have no names, only generic ones.

To Reproduce
Steps to reproduce the behavior:

1. Connect Aqara hub E1
2. Add devices with Aqara app and give human-readable name
3. Connect hub to ioBroker with homekit-controller
4. All devices are listed, but without names

Expected behavior
I should see the names I have given in the Aqara app.

Screenshots & Logfiles

Versions:

• Adapter version: v0.5.1
• JS-Controller version: v4.0.24
• Node version: v16.14.2
• Operating system: linux

Update stable version in repo from 0.4.3 to 0.4.4

Think about update stable version to 0.4.4

Version: stable=0.4.3 (116 days old) => latest=0.4.4 (15 days old)
Installs: stable=2017 (70.13%), latest=171 (5.95%), total=2876
Click to edit

Devices gets added multiple times

Describe the bug
A temperature sensor lost the connection to my Aqara E1 Hub and after adding it again, it appears twice in iobroker. Although the serial number keeps the same.

To Reproduce
Steps to reproduce the behavior:

1. wait till sensor has lost connection
2. add again
3. see the device twice in iobroker

Expected behavior
The device should only show up once in iobroker

Screenshots & Logfiles
You can see that device 44 and 45 have the same serial-number

Versions:

• Adapter version: v0.5.8
• JS-Controller version: 4.0.24
• Node version: v16.19.1
• Operating system: linux

IT4WIFI position-hold option not working

Describe the bug

Homekit-Controller detects device option as bool but device expects 0 / 1 as number values.

{
  "type": "state",
  "common": {
    "name": "",
    "read": false,
    "write": true,
    "type": "boolean",
    "role": "button"
  },
  "native": {
    "iid": 14,
    "type": "0000006F-0000-1000-8000-0026BB765291",
    "perms": [
      "pw"
    ],
    "format": "bool",
    "aid": "1",
    "serviceUuid": "00000041-0000-1000-8000-0026BB765291"
  },
  "_id": "homekit-controller.0.IP-86:FC:20:76:77:08.1.garage-door-opener-2.position-hold",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "from": "system.adapter.homekit-controller.0",
  "user": "system.user.admin",
  "ts": 1686741245935
}

To Reproduce
Steps to reproduce the behavior:

1. buy a IT4WIFI device from nice
2. try to set value for position-hold

Expected behavior
Value should be accepted by device.

Screenshots & Logfiles

Not sure which logfiles are needed.

homekit-controller.0 | 2023-06-16 08:13:54.911 | debug | IP-86:FC:20:76:77:08 Accessory Structure: {"accessories":[{"aid":1,"services":[{"iid":1,"type":"0000003E-0000-1000-8000-0026BB765291","characteristics":[{"iid":4,"type":"00000023-0000-1000-8000-0026BB765291","value":"NiceIT4WIFI712D10","perms":["pr"],"format":"string","maxLen":64},{"iid":5,"type":"00000014-0000-1000-8000-0026BB765291","perms":["pw"],"format":"bool"},{"iid":6,"type":"00000020-0000-1000-8000-0026BB765291","value":"Nice Spa ","perms":["pr"],"format":"string","maxLen":64},{"iid":7,"type":"00000021-0000-1000-8000-0026BB765291","value":"IT4WIFI","perms":["pr"],"format":"string","maxLen":64},{"iid":8,"type":"00000030-0000-1000-8000-0026BB765291","value":"0Q01231200H9225CE","perms":["pr"],"format":"string","maxLen":64},{"iid":9,"type":"00000052-0000-1000-8000-0026BB765291","value":"0.3.2","perms":["pr"],"format":"string"}]},{"iid":2,"type":"00000041-0000-1000-8000-0026BB765291","characteristics":[{"iid":10,"type":"0000000E-0000-1000-8000-0026BB765291","value":1,"perms":["pr","ev"],"format":"uint8","minValue":0,"maxValue":4,"minStep":1},{"iid":11,"type":"00000032-0000-1000-8000-0026BB765291","value":1,"perms":["pr","pw","ev"],"format":"uint8","minValue":0,"maxValue":1,"minStep":1},{"iid":12,"type":"00000024-0000-1000-8000-0026BB765291","value":0,"perms":["pr","ev"],"format":"bool"},{"iid":13,"type":"00000023-0000-1000-8000-0026BB765291","value":"Garage Door ","perms":["pr"],"format":"string","maxLen":64},{"iid":14,"type":"0000006F-0000-1000-8000-0026BB765291","perms":["pw"],"format":"bool"}]},{"iid":3,"type":"D639B30A-0268-4824-9F82-CB03B449D5F0","characteristics":[{"iid":15,"type":"D66FD9FA-4D09-47F2-AB5F-298700DD92AC","perms":["pw","hd"],"format":"bool"}]}]}]}
-- | -- | -- | --

position-hold "iid":14 should be write only and bool as 0 / 1 values instead of true and false. This works also fine with homekit implementation of apple itself. As i don't expect that apple implemented a workaround for this device i think this must be a bug in homelkit implementation or apple always sends 0 / 1 instead of true false.

Thanks a lot for your great work @Apollon77 !

Update stable version in repo from 0.3.3 to 0.4.3

Think about update stable version to 0.4.3

Version: stable=0.3.3 (106 days old) => latest=0.4.3 (15 days old)
Installs: stable=2569 (91.16%), latest=232 (8.23%), total=2818
Click to edit

Connection to Aqara Hub E1 breaks with Could not initialize device: connect ECONNREFUSED

Describe the bug
The adapter connects successfully with my Aqara hub E1. But after a few hours the connection is dropped. A restart does not help, only a reinstall. Both without doing anything on the hub.

To Reproduce
Steps to reproduce the behavior:

1. Connect Aqara Hub E1 with homekit-controller
2. Use it for few hours
3. Connection is lost
4. Restart adapter
5. Connection still lost
6. Reinstall adapter
7. Adapter finds the hub from previous installation and can connect

Expected behavior
Should not need a reinstall to connect again to the hub

Screenshots & Logfiles
Here are the logs from a restart with no success and then a reinstall with a successfull connection afterwards

2023-01-21 00:00:00.030  - info: smartcontrol.0 (1204) Re-scheduling time triggers for updating astro times and updating 'info.astroTimes.' states.
2023-01-21 01:19:49.694  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d000484f1f2.temperature.json"
2023-01-21 01:19:49.779  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d00051e3a72.temperature.json"
2023-01-21 01:29:49.689  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d00052dc23c.temperature.json"
2023-01-21 01:29:49.693  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d00052dc23c.humidity.json"
2023-01-21 01:29:49.719  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d00051e3a72.humidity.json"
2023-01-21 01:59:49.698  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d00045bd521.temperature.json"
2023-01-21 01:59:49.702  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d00045bd521.humidity.json"
2023-01-21 02:29:49.696  - info: history.0 (1110) Delete old history "/opt/iobroker/iobroker-data/history/20230116/history.zigbee.0.00158d000484f1f2.humidity.json"
2023-01-21 05:57:01.096  - debug: homekit-controller.0 (2512) Discovered IP device changed: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 05:57:01.124  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Discovered IP device: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:01.126  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:46727
2023-01-21 05:57:01.131  - debug: homekit-controller.0 (2512) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:01.156  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 05:57:01.202  - info: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
2023-01-21 05:57:02.097  - debug: homekit-controller.0 (2512) Discovered IP device down: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 05:57:02.105  - debug: homekit-controller.0 (2512) Discovered IP device up: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 05:57:02.106  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Discovered IP device: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:02.107  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:46727
2023-01-21 05:57:02.108  - debug: homekit-controller.0 (2512) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:02.117  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 05:57:02.140  - info: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
2023-01-21 06:00:26.618  - info: admin.0 (1088) ==> Connected system.user.admin from ::ffff:192.168.178.80
2023-01-21 06:01:02.962  - info: admin.0 (1088) ==> Connected system.user.admin from ::ffff:192.168.178.80
2023-01-21 06:01:03.056  - debug: homekit-controller.0 (2512) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":289,"ack":false,"time":1674280863024},"_id":87710106})
2023-01-21 06:01:03.058  - debug: homekit-controller.0 (2512) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-9D:41:6F:FA:8D:A9","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Aqara-Hub-E1-5BF5","discoveredCategory":"Bridge","pairedWithThisInstance":true},{"id":"IP-C2:38:EC:19:3D:8D","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Philips hue - 1D7766","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2023-01-21 06:01:11.254  - debug: homekit-controller.0 (2512) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":290,"ack":false,"time":1674280871242},"_id":87710107})
2023-01-21 06:01:11.256  - debug: homekit-controller.0 (2512) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-9D:41:6F:FA:8D:A9","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Aqara-Hub-E1-5BF5","discoveredCategory":"Bridge","pairedWithThisInstance":true},{"id":"IP-C2:38:EC:19:3D:8D","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Philips hue - 1D7766","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2023-01-21 06:01:17.034  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 (force=false, process=true)
2023-01-21 06:01:17.075  - info: homekit-controller.0 (2512) Got terminate signal TERMINATE_YOURSELF
2023-01-21 06:01:17.107  - info: homekit-controller.0 (2512) terminating
2023-01-21 06:01:17.109  - debug: homekit-controller.0 (2512) Plugin sentry destroyed
2023-01-21 06:01:17.111  - info: homekit-controller.0 (2512) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-21 06:01:17.197  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 send kill signal
2023-01-21 06:01:17.740  - info: host.raspberrypi instance system.adapter.homekit-controller.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-21 06:01:20.312  - info: host.raspberrypi instance system.adapter.homekit-controller.0 started with pid 21807
2023-01-21 06:01:25.355  - debug: homekit-controller.0 (21807) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-01-21 06:01:26.285  - debug: homekit-controller.0 (21807) Objects client ready ... initialize now
2023-01-21 06:01:26.318  - debug: homekit-controller.0 (21807) Objects create System PubSub Client
2023-01-21 06:01:26.329  - debug: homekit-controller.0 (21807) Objects create User PubSub Client
2023-01-21 06:01:26.503  - debug: homekit-controller.0 (21807) Objects client initialize lua scripts
2023-01-21 06:01:26.535  - debug: homekit-controller.0 (21807) Objects connected to redis: 127.0.0.1:9001
2023-01-21 06:01:26.636  - debug: homekit-controller.0 (21807) Redis States: Use Redis connection: 127.0.0.1:9000
2023-01-21 06:01:26.681  - debug: homekit-controller.0 (21807) States create System PubSub Client
2023-01-21 06:01:26.685  - debug: homekit-controller.0 (21807) States create User PubSub Client
2023-01-21 06:01:26.768  - debug: homekit-controller.0 (21807) States connected to redis: 127.0.0.1:9000
2023-01-21 06:01:27.049  - debug: homekit-controller.0 (21807) Plugin sentry Initialize Plugin (enabled=true)
2023-01-21 06:01:28.203  - info: homekit-controller.0 (21807) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v16.14.2, js-controller: 4.0.21
2023-01-21 06:01:28.350  - debug: homekit-controller.0 (21807) Init 1 known devices without discovery ...
2023-01-21 06:01:28.353  - debug: homekit-controller.0 (21807) Init IP-9D:41:6F:FA:8D:A9 as known device
2023-01-21 06:01:28.356  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:33915
2023-01-21 06:01:28.363  - debug: homekit-controller.0 (21807) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":33915,"c#":2,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":4,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.381  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 06:01:28.413  - info: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
2023-01-21 06:01:28.655  - debug: homekit-controller.0 (21807) Discovered IP device up: C2:38:EC:19:3D:8D/Philips hue - 1D7766
2023-01-21 06:01:28.658  - debug: homekit-controller.0 (21807) IP-C2:38:EC:19:3D:8D Discovered IP device: {"name":"Philips hue - 1D7766","address":"192.168.178.61","port":8080,"c#":121,"ff":1,"id":"C2:38:EC:19:3D:8D","md":"BSB002","pv":"1.1","s#":66,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.662  - info: homekit-controller.0 (21807) IP-C2:38:EC:19:3D:8D (Philips hue - 1D7766) found without known pairing data and already paired: ignoring
2023-01-21 06:01:28.674  - debug: homekit-controller.0 (21807) Discovered IP device up: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 06:01:28.676  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Discovered IP device: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.677  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:46727
2023-01-21 06:01:28.678  - debug: homekit-controller.0 (21807) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.694  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 06:01:28.762  - info: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
2023-01-21 06:01:31.136  - info: admin.0 (1088) <== Disconnect system.user.admin from ::ffff:192.168.178.80 homekit-controller
2023-01-21 06:03:52.533  - info: host.raspberrypi iobroker del homekit-controller.0
2023-01-21 06:03:56.750  - info: host.raspberrypi iobroker Delete instance "homekit-controller.0"
2023-01-21 06:03:56.867  - info: host.raspberrypi iobroker host.raspberrypi Counted 1 instances of homekit-controller.0
2023-01-21 06:03:56.910  - info: host.raspberrypi iobroker host.raspberrypi Counted 3 devices of homekit-controller.0
2023-01-21 06:03:56.995  - info: host.raspberrypi iobroker host.raspberrypi Counted 16 channels of homekit-controller.0
2023-01-21 06:03:57.065  - info: host.raspberrypi iobroker host.raspberrypi Counted 65 states of homekit-controller.0
2023-01-21 06:03:57.108  - info: host.raspberrypi iobroker host.raspberrypi Counted 15 states of system.adapter.homekit-controller.0
2023-01-21 06:03:57.148  - info: host.raspberrypi iobroker host.raspberrypi Counted 61 states (io.homekit-controller.0.*) from states
2023-01-21 06:03:57.281  - info: host.raspberrypi iobroker host.raspberrypi Counted 15 states (system.adapter.homekit-controller.0.*) from states
2023-01-21 06:03:59.456  - info: host.raspberrypi iobroker host.raspberrypi Counted 2 objects of homekit-controller.0
2023-01-21 06:03:59.459  - info: host.raspberrypi iobroker host.raspberrypi Deleting 102 object(s).
2023-01-21 06:04:00.644  - info: host.raspberrypi object deleted system.adapter.homekit-controller.0
2023-01-21 06:04:00.647  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 (force=false, process=true)
2023-01-21 06:04:00.655  - info: host.raspberrypi iobroker host.raspberrypi Deleting 76 state(s).
2023-01-21 06:04:00.667  - info: homekit-controller.0 (21807) Got terminate signal TERMINATE_YOURSELF
2023-01-21 06:04:00.680  - info: homekit-controller.0 (21807) terminating
2023-01-21 06:04:00.682  - debug: homekit-controller.0 (21807) Plugin sentry destroyed
2023-01-21 06:04:00.684  - info: homekit-controller.0 (21807) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-21 06:04:00.759  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 send kill signal
2023-01-21 06:04:01.315  - error: host.raspberrypi instance system.adapter.homekit-controller.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2023-01-21 06:04:01.316  - info: host.raspberrypi Do not restart adapter system.adapter.homekit-controller.0 because desired by instance
2023-01-21 06:04:02.258  - info: host.raspberrypi iobroker exit 0
2023-01-21 06:04:11.123  - info: host.raspberrypi iobroker add homekit-controller --host raspberrypi 
2023-01-21 06:04:15.024  - info: host.raspberrypi iobroker host.raspberrypi create instance homekit-controller
2023-01-21 06:04:15.062  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.alive created
2023-01-21 06:04:15.081  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.connected created
2023-01-21 06:04:15.101  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.compactMode created
2023-01-21 06:04:15.121  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.cpu created
2023-01-21 06:04:15.142  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.cputime created
2023-01-21 06:04:15.165  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.memHeapUsed created
2023-01-21 06:04:15.186  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.memHeapTotal created
2023-01-21 06:04:15.210  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.memRss created
2023-01-21 06:04:15.254  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.uptime created
2023-01-21 06:04:15.278  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.inputCount created
2023-01-21 06:04:15.295  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.outputCount created
2023-01-21 06:04:15.314  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.eventLoopLag created
2023-01-21 06:04:15.362  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.sigKill created
2023-01-21 06:04:15.385  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.logLevel created
2023-01-21 06:04:15.423  - info: host.raspberrypi iobroker host.raspberrypi object homekit-controller.0.info created
2023-01-21 06:04:15.451  - info: host.raspberrypi iobroker host.raspberrypi object homekit-controller.0.info.connection created
2023-01-21 06:04:15.466  - info: host.raspberrypi iobroker host.raspberrypi Set default value of homekit-controller.0.info.connection: false
2023-01-21 06:04:15.496  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0 created
2023-01-21 06:04:16.604  - info: host.raspberrypi iobroker exit 0
2023-01-21 06:04:18.617  - info: host.raspberrypi instance system.adapter.homekit-controller.0 started with pid 21894
2023-01-21 06:04:24.134  - info: homekit-controller.0 (21894) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v16.14.2, js-controller: 4.0.21
2023-01-21 06:04:24.533  - info: homekit-controller.0 (21894) IP-C2:38:EC:19:3D:8D (Philips hue - 1D7766) found without known pairing data and already paired: ignoring
2023-01-21 06:04:24.715  - info: homekit-controller.0 (21894) IP-9D:41:6F:FA:8D:A9 Found stored Pairing data, try it ...
2023-01-21 06:04:25.896  - info: javascript.0 (1118) script.js.common.Badfenster_v2: start alert
2023-01-21 06:09:25.925  - info: javascript.0 (1118) script.js.common.Badfenster_v2: blinking on
2023-01-21 06:10:01.452  - info: javascript.0 (1118) script.js.common.Badfenster_v2: blinking off
niclas@raspberrypi:/opt/iobroker/log $ cat iobroker.current.log | grep homekit-controller
2023-01-21 05:57:01.096  - debug: homekit-controller.0 (2512) Discovered IP device changed: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 05:57:01.124  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Discovered IP device: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:01.126  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:46727
2023-01-21 05:57:01.131  - debug: homekit-controller.0 (2512) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:01.156  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 05:57:01.202  - info: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
2023-01-21 05:57:02.097  - debug: homekit-controller.0 (2512) Discovered IP device down: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 05:57:02.105  - debug: homekit-controller.0 (2512) Discovered IP device up: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 05:57:02.106  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Discovered IP device: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:02.107  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:46727
2023-01-21 05:57:02.108  - debug: homekit-controller.0 (2512) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 05:57:02.117  - debug: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 05:57:02.140  - info: homekit-controller.0 (2512) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
2023-01-21 06:01:03.056  - debug: homekit-controller.0 (2512) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":289,"ack":false,"time":1674280863024},"_id":87710106})
2023-01-21 06:01:03.058  - debug: homekit-controller.0 (2512) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-9D:41:6F:FA:8D:A9","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Aqara-Hub-E1-5BF5","discoveredCategory":"Bridge","pairedWithThisInstance":true},{"id":"IP-C2:38:EC:19:3D:8D","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Philips hue - 1D7766","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2023-01-21 06:01:11.254  - debug: homekit-controller.0 (2512) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":290,"ack":false,"time":1674280871242},"_id":87710107})
2023-01-21 06:01:11.256  - debug: homekit-controller.0 (2512) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"IP-9D:41:6F:FA:8D:A9","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Aqara-Hub-E1-5BF5","discoveredCategory":"Bridge","pairedWithThisInstance":true},{"id":"IP-C2:38:EC:19:3D:8D","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Philips hue - 1D7766","discoveredCategory":"Bridge","pairedWithThisInstance":false}]}
2023-01-21 06:01:17.034  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 (force=false, process=true)
2023-01-21 06:01:17.075  - info: homekit-controller.0 (2512) Got terminate signal TERMINATE_YOURSELF
2023-01-21 06:01:17.107  - info: homekit-controller.0 (2512) terminating
2023-01-21 06:01:17.109  - debug: homekit-controller.0 (2512) Plugin sentry destroyed
2023-01-21 06:01:17.111  - info: homekit-controller.0 (2512) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-21 06:01:17.197  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 send kill signal
2023-01-21 06:01:17.740  - info: host.raspberrypi instance system.adapter.homekit-controller.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-01-21 06:01:20.312  - info: host.raspberrypi instance system.adapter.homekit-controller.0 started with pid 21807
2023-01-21 06:01:25.355  - debug: homekit-controller.0 (21807) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-01-21 06:01:26.285  - debug: homekit-controller.0 (21807) Objects client ready ... initialize now
2023-01-21 06:01:26.318  - debug: homekit-controller.0 (21807) Objects create System PubSub Client
2023-01-21 06:01:26.329  - debug: homekit-controller.0 (21807) Objects create User PubSub Client
2023-01-21 06:01:26.503  - debug: homekit-controller.0 (21807) Objects client initialize lua scripts
2023-01-21 06:01:26.535  - debug: homekit-controller.0 (21807) Objects connected to redis: 127.0.0.1:9001
2023-01-21 06:01:26.636  - debug: homekit-controller.0 (21807) Redis States: Use Redis connection: 127.0.0.1:9000
2023-01-21 06:01:26.681  - debug: homekit-controller.0 (21807) States create System PubSub Client
2023-01-21 06:01:26.685  - debug: homekit-controller.0 (21807) States create User PubSub Client
2023-01-21 06:01:26.768  - debug: homekit-controller.0 (21807) States connected to redis: 127.0.0.1:9000
2023-01-21 06:01:27.049  - debug: homekit-controller.0 (21807) Plugin sentry Initialize Plugin (enabled=true)
2023-01-21 06:01:28.203  - info: homekit-controller.0 (21807) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v16.14.2, js-controller: 4.0.21
2023-01-21 06:01:28.350  - debug: homekit-controller.0 (21807) Init 1 known devices without discovery ...
2023-01-21 06:01:28.353  - debug: homekit-controller.0 (21807) Init IP-9D:41:6F:FA:8D:A9 as known device
2023-01-21 06:01:28.356  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:33915
2023-01-21 06:01:28.363  - debug: homekit-controller.0 (21807) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":33915,"c#":2,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":4,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.381  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 06:01:28.413  - info: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
2023-01-21 06:01:28.655  - debug: homekit-controller.0 (21807) Discovered IP device up: C2:38:EC:19:3D:8D/Philips hue - 1D7766
2023-01-21 06:01:28.658  - debug: homekit-controller.0 (21807) IP-C2:38:EC:19:3D:8D Discovered IP device: {"name":"Philips hue - 1D7766","address":"192.168.178.61","port":8080,"c#":121,"ff":1,"id":"C2:38:EC:19:3D:8D","md":"BSB002","pv":"1.1","s#":66,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.662  - info: homekit-controller.0 (21807) IP-C2:38:EC:19:3D:8D (Philips hue - 1D7766) found without known pairing data and already paired: ignoring
2023-01-21 06:01:28.674  - debug: homekit-controller.0 (21807) Discovered IP device up: 9D:41:6F:FA:8D:A9/Aqara-Hub-E1-5BF5
2023-01-21 06:01:28.676  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Discovered IP device: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.677  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Start Homekit Device Client initialization on 192.168.178.113:46727
2023-01-21 06:01:28.678  - debug: homekit-controller.0 (21807) Service: {"name":"Aqara-Hub-E1-5BF5","address":"192.168.178.113","port":46727,"c#":5,"ff":2,"id":"9D:41:6F:FA:8D:A9","md":"HE1-G01","pv":"1.1","s#":8,"sf":0,"ci":2,"availableToPair":false}
2023-01-21 06:01:28.694  - debug: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Request Accessory information
2023-01-21 06:01:28.762  - info: homekit-controller.0 (21807) IP-9D:41:6F:FA:8D:A9 Could not initialize device: connect ECONNREFUSED 192.168.178.113:33915 Error: connect ECONNREFUSED 192.168.178.113:33915
2023-01-21 06:01:31.136  - info: admin.0 (1088) <== Disconnect system.user.admin from ::ffff:192.168.178.80 homekit-controller
2023-01-21 06:03:52.533  - info: host.raspberrypi iobroker del homekit-controller.0
2023-01-21 06:03:56.750  - info: host.raspberrypi iobroker Delete instance "homekit-controller.0"
2023-01-21 06:03:56.867  - info: host.raspberrypi iobroker host.raspberrypi Counted 1 instances of homekit-controller.0
2023-01-21 06:03:56.910  - info: host.raspberrypi iobroker host.raspberrypi Counted 3 devices of homekit-controller.0
2023-01-21 06:03:56.995  - info: host.raspberrypi iobroker host.raspberrypi Counted 16 channels of homekit-controller.0
2023-01-21 06:03:57.065  - info: host.raspberrypi iobroker host.raspberrypi Counted 65 states of homekit-controller.0
2023-01-21 06:03:57.108  - info: host.raspberrypi iobroker host.raspberrypi Counted 15 states of system.adapter.homekit-controller.0
2023-01-21 06:03:57.148  - info: host.raspberrypi iobroker host.raspberrypi Counted 61 states (io.homekit-controller.0.*) from states
2023-01-21 06:03:57.281  - info: host.raspberrypi iobroker host.raspberrypi Counted 15 states (system.adapter.homekit-controller.0.*) from states
2023-01-21 06:03:59.456  - info: host.raspberrypi iobroker host.raspberrypi Counted 2 objects of homekit-controller.0
2023-01-21 06:04:00.644  - info: host.raspberrypi object deleted system.adapter.homekit-controller.0
2023-01-21 06:04:00.647  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 (force=false, process=true)
2023-01-21 06:04:00.667  - info: homekit-controller.0 (21807) Got terminate signal TERMINATE_YOURSELF
2023-01-21 06:04:00.680  - info: homekit-controller.0 (21807) terminating
2023-01-21 06:04:00.682  - debug: homekit-controller.0 (21807) Plugin sentry destroyed
2023-01-21 06:04:00.684  - info: homekit-controller.0 (21807) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-01-21 06:04:00.759  - info: host.raspberrypi stopInstance system.adapter.homekit-controller.0 send kill signal
2023-01-21 06:04:01.315  - error: host.raspberrypi instance system.adapter.homekit-controller.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2023-01-21 06:04:01.316  - info: host.raspberrypi Do not restart adapter system.adapter.homekit-controller.0 because desired by instance
2023-01-21 06:04:11.123  - info: host.raspberrypi iobroker add homekit-controller --host raspberrypi 
2023-01-21 06:04:15.024  - info: host.raspberrypi iobroker host.raspberrypi create instance homekit-controller
2023-01-21 06:04:15.062  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.alive created
2023-01-21 06:04:15.081  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.connected created
2023-01-21 06:04:15.101  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.compactMode created
2023-01-21 06:04:15.121  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.cpu created
2023-01-21 06:04:15.142  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.cputime created
2023-01-21 06:04:15.165  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.memHeapUsed created
2023-01-21 06:04:15.186  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.memHeapTotal created
2023-01-21 06:04:15.210  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.memRss created
2023-01-21 06:04:15.254  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.uptime created
2023-01-21 06:04:15.278  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.inputCount created
2023-01-21 06:04:15.295  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.outputCount created
2023-01-21 06:04:15.314  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.eventLoopLag created
2023-01-21 06:04:15.362  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.sigKill created
2023-01-21 06:04:15.385  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0.logLevel created
2023-01-21 06:04:15.423  - info: host.raspberrypi iobroker host.raspberrypi object homekit-controller.0.info created
2023-01-21 06:04:15.451  - info: host.raspberrypi iobroker host.raspberrypi object homekit-controller.0.info.connection created
2023-01-21 06:04:15.466  - info: host.raspberrypi iobroker host.raspberrypi Set default value of homekit-controller.0.info.connection: false
2023-01-21 06:04:15.496  - info: host.raspberrypi iobroker host.raspberrypi object system.adapter.homekit-controller.0 created
2023-01-21 06:04:18.617  - info: host.raspberrypi instance system.adapter.homekit-controller.0 started with pid 21894
2023-01-21 06:04:24.134  - info: homekit-controller.0 (21894) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.homekit-controller, node: v16.14.2, js-controller: 4.0.21
2023-01-21 06:04:24.533  - info: homekit-controller.0 (21894) IP-C2:38:EC:19:3D:8D (Philips hue - 1D7766) found without known pairing data and already paired: ignoring
2023-01-21 06:04:24.715  - info: homekit-controller.0 (21894) IP-9D:41:6F:FA:8D:A9 Found stored Pairing data, try it ...

Versions:

• Adapter version: v0.5.1
• JS-Controller version: v4.0.24
• Node version: v16.14.2
• Operating system: linux

Pairing failed - Host Unreachable

Describe the bug
Upon attempting to pair a Netatmo Air Quality Sensor to the adapter using IP, a "Host Unreachable" error appears and the device fails to pair (despite being, for sure, in pairing mode)

To Reproduce

• Pair the Netatmo Air Quality Sensor to Apple HomeKit on an iPhone/iPad to add it to local network
• • The Sensor appears as reachable but already paired on iobroker
• Put the sensor in pairing mode by long-pressing the top until the light blinks white (pairing mode)
• • The sensor now appears as reachable and ready to pair
• Input PIN number with the dashes
• (Almost) immediately fails and throws the following error:

Cannot pair with device IP-8C:D7:F4:CF:8A:81 because of error undefined (undefined): connect EHOSTUNREACH 192.168.200.244:5001

Expected behavior
Pairing is successful

Screenshots & Logfiles

Adapter	Timestamp	Loglevel	Message
homekit-controller.0	2022-11-10 23:27:42.979	info	Cannot pair with device IP-8C:D7:F4:CF:8A:81 because of error undefined (undefined): connect EHOSTUNREACH 192.168.200.244:5001
homekit-controller.0	2022-11-10 23:27:39.915	debug	IP-8C:D7:F4:CF:8A:81 Start Homekit Device Client initialization on 192.168.200.244:5001
homekit-controller.0	2022-11-10 23:27:39.914	info	Use PairMethod 1 to pair IP-8C:D7:F4:CF:8A:81
homekit-controller.0	2022-11-10 23:27:39.913	debug	state homekit-controller.0.IP-8C:D7:F4:CF:8A:81.admin.pairWithPin changed: xxx-xx-xxx (ack = false)

I don't know if 8C:D7:F4:CF:8A:81 was supposed to be a MAC address but this address is actually wrong for the device I have connected here

Versions:

• Adapter version: v0.5.1
• JS-Controller version: v4.0.23
• Node version: 16.17.1
• Operating system: RaspberryOS

Additional context
PiHole was disabled this time btw :)

Add Admin UI

The adapter offeres messages to get discovered devices and to trigger actions on devices.

The Admin UI should display a table with the discovered devices and a button to update the table with current adapter info (or auto update every 10s or such?). It migtj need some minites after adapter start for devices to appear.

The response from "getDiscoveredDevices" message looks like:

{
    "success": true,
    "error": false,
    "devices": [
        {
            "id": "IP-A9:69:E4:86:F7:2E",
            "serviceType": "IP",
            "connected": false,
            "discovered": true,
            "availableToPair": true,
            "discoveredName": "IP Accessory",
            "discoveredCategory": "Other",
            "pairedWithThisInstance": false
        },
        {
            "id": "IP-AD:62:54:73:8C:72",
            "serviceType": "IP",
            "connected": false,
            "discovered": true,
            "availableToPair": true,
            "discoveredName": "Philips hue - 84B26C",
            "discoveredCategory": "Bridge",
            "pairedWithThisInstance": false
        },
        {
            "id": "BLE-6F:63:9A:98:ED:52",
            "serviceType": "BLE",
            "connected": true,
            "discovered": true,
            "availableToPair": false,
            "discoveredName": "Eve",
            "discoveredCategory": "Outlet",
            "pairedWithThisInstance": true
        },
        {
            "id": "IP-CC:22:3D:E3:CE:30",
            "serviceType": "IP",
            "connected": false,
            "discovered": true,
            "availableToPair": false,
            "discoveredName": "Homebridge CAD8",
            "discoveredCategory": "Bridge",
            "pairedWithThisInstance": false
        }
    ]
}

For the table show:

• (unique device) id and name and detected category
• icons/info if device is an IP or BLE device
• when "pairedWithThisInstance===true" then this device is fully connected with this instance and only "unpair" is availabel as action. Connection status can be shown using "connected" field
• when "pairedWithThisInstance===false && availableToPair===true" then the device is available to be paired. In this case the actions "identify" and "pair" are available
• when "pairedWithThisInstance===false && availableToPair===false" then the device is paired with someone else and shpuld be displayed "grayed out" as "was discovered, but unavailable". maybe we add a button for the table to hide these unavailable devices in the list.

The actions are basically buttons that should be greyed out once clicked until response was received:

• The "unpair" button should trigger an "do you really want to unpair" dialog and send "unpairDevice" message with the device-id on "yes". After response the table should be reloaded to update the data
• The identify button should directly send the "identifyDevice" message with the device-id and gray that button out for 10s also after response.
• The "pair" button opens a dialog to ask for the PIN (in form 123-45-678 - maybe UI can support the user in entering correct format or validate it). The dialog sends the "pairDevice" message with device-id and pin as parameters. After response the table should be reloaded to update the data

The response contains a success flag (true) to mark success or an error field in case of an errror with the error mesaage to show.

Who is throttling messages from an Aqara FP2 presence detector?

Hello, just a quick question, and then you can probably close this issue right away: is there any throttling or scheduling going on when messages from an IP device are received?

I left the polling intervals as they are (30s and 60s), but they're not relevant here.

I see the following debug output when I move from one of the zones to an immediately adjacent zone. The presence messages and the corresponding brightness value changes (due to my light automation) are received with ca. 1 second in between them. I'm wondering if this is the sensor's fault or a problem in homekit-controller.

2023-05-18 20:49:03.986  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2702,"value":0}]}
2023-05-18 20:49:03.987  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2702,"value":0}]
2023-05-18 20:49:03.991  - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-occupancy-2700.occupancy-detected changed: 0 (ack = true)

2023-05-18 20:49:04.977  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2674,"value":17},{"aid":1,"iid":2706,"value":1}]}
2023-05-18 20:49:04.978  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2674,"value":17},{"aid":1,"iid":2706,"value":1}]
2023-05-18 20:49:04.983  - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-light-2672.light-level-current changed: 17 (ack = true)
2023-05-18 20:49:04.985  - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-occupancy-2704.occupancy-detected changed: 1 (ack = true)

2023-05-18 20:49:05.975  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2674,"value":5}]}
2023-05-18 20:49:05.976  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2674,"value":5}]
2023-05-18 20:49:05.982  - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-light-2672.light-level-current changed: 5 (ack = true)

2023-05-18 20:49:06.976  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F IP device subscription event received: {"characteristics":[{"aid":1,"iid":2674,"value":58}]}
2023-05-18 20:49:06.977  - debug: homekit-controller.0 (17479) IP-CF:F8:39:2A:1E:3F Set Values to ioBroker: [{"aid":1,"iid":2674,"value":58}]
2023-05-18 20:49:06.981  - debug: homekit-controller.0 (17479) state homekit-controller.0.IP-CF:F8:39:2A:1E:3F.1.sensor-light-2672.light-level-current changed: 58 (ack = true)

Ikea Dirigerga ist verbunden - Homekit-controller reagiert nicht auf Änderungen

Hallo,

ich habe das Ikea Dirigera in der Firmware-Version (2.256.3) und den Homekit-Controller (0.5.1).

Nach den pairen werden zwar Einträge zu den in Dirigera angelegten Ikea-Geräten erzeugt, aber die Werte (true/false) der Geräte scheinen nicht upzudaten.

Setze ich einen Wert (bspw. Lampe "OUTLET-.ON" auf true) wird der Eintrag sofort wieder auf false gesetzt.
Das Gerät OUTLET wird nicht gesteuert.

Einen Eintrag im LOG gibt es ebenfalls nicht für diesen Schaltvorgang.

Wenn der Dirigera-Hub mit Apple-Homekit (iPhone) verbunden ist, sind die Geräte steuerbar und legen auch Werte-Updates.

Ist der Fehler bereits bekannt?

Grüße
Sur.

Sporadische Fehlermeldung - Was ist die Ursache?

Hallo Zusammen,

ich nutze den HomKit-Controller in der Version 0.5.7 und erhalte sporadisch immer mal wieder folgende Fehlermeldungen:

Letztendlich scheint der Fehler nicht von Dauer zu sein, denn nach einer gewissen Zeit reinitialisiert sich die Verbindung von alleine. Während des Fehlers ist das Objekt nicht schaltbar. Was sind die Gründe für den Fehler? Wie kann ich das Problem abstellen?

Log error

Describe the bug
Running iobroker inside a Docker image.
When attached to container I can see an error message. Added as screenshot.

I don't know if it's affecting Adapter behavior.

To Reproduce
Steps to reproduce the behavior:

1. Run iobroker inside Docker from official latest Docker image
2. Attach to Docker Image
3. Install adapter
4. You will see the error message at the terminal

Expected behavior
Exceptions to be managed.

Screenshots & Logfiles

Versions:

• Adapter version: 0.5.9
• JS-Controller version: 5.0.17
• Node version: 18.19.0
• Operating system: Docker on Raspbian host.

Additional context
No additional context

Update stable version in repo from 0.4.4 to 0.5.1

Think about update stable version to 0.5.1

Version: stable=0.4.4 (50 days old) => latest=0.5.1 (15 days old)
Installs: stable=1251 (43.18%), latest=161 (5.56%), total=2897
Click to edit

Update stable version in repo from 0.5.8 to 0.5.9

Think about update stable version to 0.5.9

Version: stable=0.5.8 (293 days old) => latest=0.5.9 (24 days old)
Installs: stable=2416 (65.49%), latest=188 (5.1%), total=3689

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Adapter shows connection state FALSE due to timeout, but values are still coming in and devices can be controlled

The connections state indicates false positives after a Time out or miscommunication.
In the behavior I observed, the connection states was false for about 50 minutes.

As visible in this monitoring, connection is FALS but temp and motion sensor still submit their values

But during that time I still received values of motion and temperature sensor, after sending a switch command the adapter switch to connection state true

Debug logging send to developer

Update stable version in repo from 0.5.1 to 0.5.6

Think about update stable version to 0.5.6

Version: stable=0.5.1 (224 days old) => latest=0.5.6 (15 days old)
Installs: stable=2214 (71.7%), latest=123 (3.98%), total=3088
Click to edit

Adapter set values as default instead of initial value

When I start the adapter, connected to a bridge with multiple devices, I get first default values at the state objects (previous existing al always overwritten).
It needs 1 or 2 polling interfaalls before th correct data is loaded.

Example : Temps sensor are all set to 20 or 25 degrees instead of real value

Debug informatie of adapter boots is send to developer in private message

Please correct npm maintainers configuration.

ioBroker adapter checker for npm access

Access right check for adapter homekit-controller returned the following issue:

Bluefox was not found in the collaborators on NPM!.
Please execute in adapter directory: "npm owner add bluefox iobroker.homekit-controller"

Current maintainers are
apollon77 [email protected]

Please fix the above error as soon as possible.
All adapters listed at ioBroker repositories must have 'bluefox' added as maintainer.

Future version updates at the repositories will be suspended until this problem is fixed.

Eve Light Switch (BLE): pairing doesn't work

I have the following device which uses BLE (apart from Thread):
Service: {"name":"Eve Light Switch F797","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"af:96:df:07:43:9f","ACID":8,"GSN":2,"CN":2,"CV":2,"c#":2,"id":"af:96:df:07:43:9f","ci":8,"availableToPair":true}

When I try to pair I get:

2022-12-24 00:34:17.667  - info: homekit-controller.0 (11872) Cannot retrieve BLE PairMethod for device BLE-AF:96:DF:07:43:9F because of error undefined: Cannot read properties of undefined (reading 'state'), try default
2022-12-24 00:34:17.667  - info: homekit-controller.0 (11872) Use PairMethod 0 to pair BLE-AF:96:DF:07:43:9F
2022-12-24 00:34:17.668  - debug: homekit-controller.0 (11872) BLE-AF:96:DF:07:43:9F Waiting for BLE discovery of this device for proper initialization
2022-12-24 00:34:17.669  - info: homekit-controller.0 (11872) Cannot pair with device BLE-AF:96:DF:07:43:9F because Client initialization not successful

hciconfig hci0:
hci0: Type: Primary Bus: USB
BD Address: 5C:F3:70:93:BD:C6 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:19544418 acl:60 sco:0 events:627237 errors:0
TX bytes:4834 acl:17 sco:0 commands:260 errors:0

Simultaneous control doesn't work

Hi,

If several objects are controlled in direct succession, either none or only one object reacts.

For example if I control the target position of one of my roller shutters to a certain value (manually or by script), this works perfectly. However, if I control several roller shutters in sequence by a script, either only one or only one roller shutter is controlled.

However if I control each shutters with a delay of e.g. 500 ms, the control also works.

Automations in Homekit for more than one object results in the same issue.

I use
Linux on Raspberry Pi
Homekit Controller 0.0.31
JS-Controller 3.3.22
Node V14.18.2

Wrong IP for the device

I had a rogue DHCP Server in my network who gave the homekit device a wrong IP. No it seams to be saved some where in the instance. If I change the IP in the object folder nothing change.
Is there any place where I can change the IP? Or something else I can do to reach the device again?

the protocol gave me this:

<html>
<body>
<!--StartFragment-->

debug | Service: {"name":"VELUX Gateway","address":"192.168.115.8","port":5001,"c#":15,"ff":1,"id":"","md":"VELUX Gateway\u0000","pv":"1.1","s#":1,"sf":0,"ci":2,"availableToPair":false}
-- | --


<!--EndFragment-->
</body>
</html>

and later a timeout. Make sense this IP is not valid.

unable to pair Aqara FP2

Describe the bug
After the FP2 device is detected and I enter the pass code nothing happens. It does not pair successfully.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Instances'
2. Click on 'homekit-controller'
3. Go to 'Devices'
4. Find the FP2 Device
5. Enter Pairing Code
6. No Pairing occurs

Expected behavior
Device should be paired after a few seconds.

Screenshots & Logfiles

Logfile

2023-11-04 10:26:20.453  - info: host.iobroker stopInstance system.adapter.homekit-controller.0 (force=false, process=true)
--
2023-11-04 10:26:20.456  - silly:  homekit-controller.0 (1234331) States system redis pmessage  system.adapter.homekit-controller.0.sigKill/system.adapter.homekit-controller.0.sigKill:{"val":-1,"ack":false,"ts":1699089980455,"q":0,"from":"system.host.iobroker","lc":1699089980455}
2023-11-04 10:26:20.457  - info: homekit-controller.0 (1234331) Got terminate signal TERMINATE_YOURSELF
2023-11-04 10:26:20.461  - info: homekit-controller.0 (1234331) terminating
2023-11-04 10:26:20.462  - debug: homekit-controller.0 (1234331) Plugin sentry destroyed
2023-11-04 10:26:20.462  - info: homekit-controller.0 (1234331) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2023-11-04 10:26:20.498  - info: host.iobroker stopInstance system.adapter.homekit-controller.0 send kill signal
2023-11-04 10:26:20.963  - info: homekit-controller.0 (1234331) terminating
2023-11-04 10:26:20.978  - info: host.iobroker instance system.adapter.homekit-controller.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2023-11-04 10:26:23.530  - info: host.iobroker instance system.adapter.homekit-controller.0 started with pid 1234370
2023-11-04 10:26:23.782  - debug: homekit-controller.0 (1234370) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-11-04 10:26:23.790  - debug: homekit-controller.0 (1234370) Objects client ready ... initialize now
2023-11-04 10:26:23.791  - debug: homekit-controller.0 (1234370) Objects create System PubSub Client
2023-11-04 10:26:23.791  - debug: homekit-controller.0 (1234370) Objects create User PubSub Client
2023-11-04 10:26:23.795  - debug: homekit-controller.0 (1234370) Objects client initialize lua scripts
2023-11-04 10:26:23.796  - debug: homekit-controller.0 (1234370) Objects connected to redis: 127.0.0.1:9001
2023-11-04 10:26:23.797  - silly: homekit-controller.0 (1234370) redis psubscribe cfg.o.system.user.*
2023-11-04 10:26:23.799  - silly: homekit-controller.0 (1234370) redis psubscribe cfg.o.enum.*
2023-11-04 10:26:23.799  - silly: homekit-controller.0 (1234370) objectDB connected
2023-11-04 10:26:23.800  - debug: homekit-controller.0 (1234370) Redis States: Use Redis connection: 127.0.0.1:9000
2023-11-04 10:26:23.801  - debug: homekit-controller.0 (1234370) States create System PubSub Client
2023-11-04 10:26:23.802  - debug: homekit-controller.0 (1234370) States create User PubSub Client
2023-11-04 10:26:23.847  - debug: homekit-controller.0 (1234370) States connected to redis: 127.0.0.1:9000
2023-11-04 10:26:23.849  - silly: homekit-controller.0 (1234370) statesDB connected
2023-11-04 10:26:23.872  - debug: homekit-controller.0 (1234370) Plugin sentry Initialize Plugin (enabled=true)
2023-11-04 10:26:23.992  - info:  homekit-controller.0 (1234370) starting. Version 0.5.8 in  /opt/iobroker/node_modules/iobroker.homekit-controller, node: v18.17.1,  js-controller: 5.0.12
2023-11-04 10:26:24.010  - silly:  homekit-controller.0 (1234370) States system redis pmessage  system.adapter.homekit-controller.0.logLevel/system.adapter.homekit-controller.0.logLevel:{"val":"silly","ack":true,"ts":1699089983999,"q":0,"from":"system.adapter.homekit-controller.0","lc":1699089158114}
2023-11-04 10:26:24.050  - debug: homekit-controller.0 (1234370) Init 1 known devices without discovery ...
2023-11-04 10:26:24.051  - debug: homekit-controller.0 (1234370) Init IP-D0:EA:D3:70:E7:F7 as known device
2023-11-04 10:26:24.053  - info:  homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7  (Presence-Sensor-FP2-BCEA) found without pairing data but available for  pairing: Create basic objects
2023-11-04 10:26:24.055  - debug:  homekit-controller.0 (1234370) Service:  {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":50596,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-04 10:26:24.443  - debug: homekit-controller.0 (1234370) Discovered IP device up: D0:EA:D3:70:E7:F7/Presence-Sensor-FP2-BCEA
2023-11-04 10:26:24.443  - debug: homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7 Discovery device update, unchanged config-number, ignore
2023-11-04 10:26:24.444  - debug:  homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7 Device Discovery  Update - reinitialize device (config changed=false):  {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":50596,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-04 10:26:24.444  - info:  homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7  (Presence-Sensor-FP2-BCEA) found without pairing data but available for  pairing: Create basic objects
2023-11-04 10:26:24.445  - debug:  homekit-controller.0 (1234370) Service:  {"name":"Presence-Sensor-FP2-BCEA","address":"192.168.1.35","port":50596,"c#":2,"ff":2,"id":"D0:EA:D3:70:E7:F7","md":"PS-S02D","pv":"1.1","s#":1,"sf":1,"ci":10,"availableToPair":true}
2023-11-04 10:26:24.455  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connectionType:{"val":"IP","ack":true,"ts":1699089984454,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918010}
2023-11-04 10:26:24.456  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connectionType changed: IP (ack = true)
2023-11-04 10:26:24.499  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.id:{"val":"D0:EA:D3:70:E7:F7","ack":true,"ts":1699089984498,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918012}
2023-11-04 10:26:24.501  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.id changed: D0:EA:D3:70:E7:F7 (ack = true)
2023-11-04 10:26:24.551  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.address:{"val":"192.168.1.35","ack":true,"ts":1699089984550,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918013}
2023-11-04 10:26:24.553  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.address changed: 192.168.1.35 (ack = true)
2023-11-04 10:26:24.603  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connected:{"val":false,"ack":true,"ts":1699089984602,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918015}
2023-11-04 10:26:24.604  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.connected changed: false (ack = true)
2023-11-04 10:26:24.656  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.isPaired:{"val":false,"ack":true,"ts":1699089984654,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699088918017}
2023-11-04 10:26:24.657  - debug: homekit-controller.0 (1234370) state homekit-controller.0.IP-D0:EA:D3:70:E7:F7.admin.isPaired changed: false (ack = true)
2023-11-04 10:26:24.708  - silly:  homekit-controller.0 (1234370) States user redis pmessage  homekit-controller.0.*/homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.lastDiscovered:{"val":1699089984445,"ack":true,"ts":1699089984706,"q":0,"from":"system.adapter.homekit-controller.0","user":"system.user.admin","lc":1699089984706}
2023-11-04 10:26:24.709  - debug:  homekit-controller.0 (1234370) state  homekit-controller.0.IP-D0:EA:D3:70:E7:F7.info.lastDiscovered changed:  1699089984445 (ack = true)
2023-11-04 10:26:57.710  - silly:  homekit-controller.0 (1234370) States system redis pmessage  io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":129,"ack":false,"time":1699090017710},"_id":24048480}
2023-11-04 10:26:57.711  - debug:  homekit-controller.0 (1234370) Message getDiscoveredDevices received:  {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":129,"ack":false,"time":1699090017710},"_id":24048480})
2023-11-04 10:26:57.711  - debug:  homekit-controller.0 (1234370) Response to Command  getDiscoveredDevices:  {"success":true,"error":false,"devices":[{"id":"IP-D0:EA:D3:70:E7:F7","serviceType":"IP","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Presence-Sensor-FP2-BCEA","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2023-11-04 10:26:57.711  - silly:  homekit-controller.0 (1234370) sendTo "getDiscoveredDevices" to  system.adapter.admin.0 from system.adapter.homekit-controller.0
2023-11-04 10:27:00.455  - silly:  homekit-controller.0 (1234370) States system redis pmessage  io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":130,"ack":false,"time":1699090020455},"_id":24048481}
2023-11-04 10:27:00.456  - debug:  homekit-controller.0 (1234370) Message getDiscoveredDevices received:  {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":130,"ack":false,"time":1699090020455},"_id":24048481})
2023-11-04 10:27:00.456  - debug:  homekit-controller.0 (1234370) Response to Command  getDiscoveredDevices:  {"success":true,"error":false,"devices":[{"id":"IP-D0:EA:D3:70:E7:F7","serviceType":"IP","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Presence-Sensor-FP2-BCEA","discoveredCategory":"Sensor","pairedWithThisInstance":false}]}
2023-11-04 10:27:00.456  - silly:  homekit-controller.0 (1234370) sendTo "getDiscoveredDevices" to  system.adapter.admin.0 from system.adapter.homekit-controller.0
2023-11-04 10:27:09.291  - silly:  homekit-controller.0 (1234370) States system redis pmessage  io.messagebox.system.adapter.homekit-controller.0/io.messagebox.system.adapter.homekit-controller.0:{"command":"pairDevice","message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"id":131,"ack":false,"time":1699090029290},"_id":24048482}
2023-11-04 10:27:09.291  - debug:  homekit-controller.0 (1234370) Message pairDevice received:  {"command":"pairDevice","message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"IP-D0:EA:D3:70:E7:F7","pin":"980-72-531"},"id":131,"ack":false,"time":1699090029290},"_id":24048482})
2023-11-04 10:27:09.291  - info: homekit-controller.0 (1234370) Use PairMethod 0 to pair IP-D0:EA:D3:70:E7:F7
2023-11-04 10:27:09.291  - debug: homekit-controller.0 (1234370) IP-D0:EA:D3:70:E7:F7 Start Homekit Device Client initialization on 192.168.1.35:50596

Versions:

• Adapter version: v0.5.8
• JS-Controller version: 5.0.12
• Node version: v18.17.1
• Operating system: debian 10

Additional context
A few Minutes after the Pairing attempt the fp2 has its led blinking blue, signaling loss of connection from the hub. The Aqara app has a notification saying "network abnormal", but reaches the device just fine. The notification disappears after clicking on the "try again" text inside that notification.

Optionen IP oder BT?

Hi,

v0.3.0
im Optionen bei auswällen von "Über IP entdeken" oder "Über Bluetooth entdeken"
beide Hacken sind gegenseitig veriegelt.

bin mir nicht ganz sicher aber finde solte sich nicht so verhalten.

JS-Controller version: <3.3.18>
Node version: <v12.22.7>
NPM: 6.14.15
Operating system: Pi4 /8GB/x64

fehlende Ausgänge im Adapter. (Missing outputs in the adapter.)

Describe the bug
bei eine Dreifache Steckenleiste ist nur eine Kanal schaltbar.

homekit-controller.0.IP-61:xx:xx:xx:xx:F3.1.outlet.on

ich konnte nach (einmaligen anlernen und wieder löschen aus "Home App") Beschreibung Gärete anlernen.
Doch es ist nur eine von drei Kanälle schaltbar.

Koogeek-O1EU-B51EA9

Screenshots & Logfiles

Versions:

• Adapter version: <v0.1.0>
• JS-Controller version: <3.3.18>
• Node version: <v12.22.7>
• Operating system: Pi4 /8GB/x64

Instance GUI vanished since adapter v059

I was running a long time on v057.
I then decided to update to the latest 059 but noticed that the instance GUI does not appear anymore.

No "options", "devices" or device list.

The last version I can see all options is 058.

Thanks

Connection to host lost

Hi
after some days the instance lose the connection to the host.

Log:

homekit-controller.0	2021-12-17 03:16:06.626	info	Device IP-xxxxxx data polling failed: connect EHOSTUNREACH 10.2.2.45:5001

After a restart of the instance everything is running well.

New device can't connect

I'm not able to pair a second device with the homekit controller
I see the device but if i click on pairing and fill in the code the following error appear:

I tried several devices and I have the same problem with all of them.

Protocol:

homekit-controller.0	2022-04-20 08:31:48.780	debug	Response to Command pairDevice: {"success":false,"error":"Cannot pair with device IP-XX because of error undefined (undefined): connect ECONNREFUSED 10.2.2.131:43982"}
homekit-controller.0	2022-04-20 08:31:48.770	debug	IP-XX Start Homekit Device Client initialization on 10.2.2.131:43982
homekit-controller.0	2022-04-20 08:31:48.770	info	Use PairMethod 1 to pair IP-XX
homekit-controller.0	2022-04-20 08:31:48.769	debug	Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"IP-XX","pin":"XX"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"IP-XX","pin":"XX"},"id":33,"ack":false,"time":1650443508767},"_id":9807354})

Versions:

• Adapter version: <0.43>
• JS-Controller version: <4.0.21>
• Node version: <14.19.0>
• Operating system: <proxmox/ubuntu>

Issue pairing Eve Room

Hi,

I was trying out the adapter and have issues with pairing a device "Eve Room" which is basically a sensor for temperature, humidity and air quality.

during pairing I get the following error:
Cannot retrieve BLE PairMethod for device BLE-10:14:83:0F:34:0E because of error undefined: Unknown Connection Identifier (0x2)

Log entries as follows:

2021-12-21 22:07:23.085 - debug: homekit-controller.0 (11562) Message getDiscoveredDevices received: {"command":"getDiscoveredDevices","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":105,"ack":false,"time":1640120843080},"_id":68764550})

2021-12-21 22:07:23.088 - debug: homekit-controller.0 (11562) Response to Command getDiscoveredDevices: {"success":true,"error":false,"devices":[{"id":"BLE-10:14:83:0F:34:0E","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":true,"discoveredName":"Eve","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"BLE-72:69:3D:60:39:7F","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Energy 0520","discoveredCategory":"Outlet","pairedWithThisInstance":false},{"id":"BLE-91:9F:C9:00:2B:1E","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Room 2C80","discoveredCategory":"Sensor","pairedWithThisInstance":false},{"id":"IP-2F:A8:68:B9:5C:B1","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Philips hue - 4F80E5","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-E9:83:16:52:3D:CF","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 58A4","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"BLE-20:A0:E2:CF:2B:C3","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve Thermo 6DF0","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"BLE-0E:BE:84:3F:F9:EF","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve","discoveredCategory":"Thermostat","pairedWithThisInstance":false},{"id":"IP-C0:8C:37:E7:0E:58","serviceType":"IP","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"IOBroker 0E43","discoveredCategory":"Bridge","pairedWithThisInstance":false},{"id":"BLE-45:B3:A5:77:B1:D1","serviceType":"BLE","connected":false,"discovered":true,"availableToPair":false,"discoveredName":"Eve","discoveredCategory":"Thermostat","pairedWithThisInstance":false}]}

2021-12-21 22:07:23.091 - debug: homekit-controller.0 (11562) sendTo "getDiscoveredDevices" to system.adapter.admin.0 from system.adapter.homekit-controller.0

2021-12-21 22:07:40.878 - debug: homekit-controller.0 (11562) Message pairDevice received: {"command":"pairDevice","message":{"deviceId":"BLE-10:14:83:0F:34:0E","pin":"70377015"},"from":"system.adapter.admin.0","callback":{"message":{"deviceId":"BLE-10:14:83:0F:34:0E","pin":"70377015"},"id":106,"ack":false,"time":1640120860875},"_id":68764551})

2021-12-21 22:08:17.328 - debug: homekit-controller.0 (11562) Response to Command pairDevice: {"success":false,"error":"Cannot retrieve BLE PairMethod for device BLE-10:14:83:0F:34:0E because of error undefined: Unknown Connection Identifier (0x2)"}

2021-12-21 22:12:58.314 - debug: homekit-controller.0 (11562) Service: {"name":"Eve Room F636","CoID":76,"TY":6,"AIL":49,"SF":1,"DeviceID":"10:14:83:0f:34:0e","ACID":10,"GSN":2,"CN":2,"CV":2,"c#":2,"id":"10:14:83:0f:34:0e","ci":10,"availableToPair":true}

Let me know if any more data is required!

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/Apollon77/ioBroker.homekit-controller

• [E142] logo is too big. It mast be less or equal than 512x512
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.homekit-controller"
• [E802] No topics found in the repository. Please go to "https://github.com/Apollon77/ioBroker.homekit-controller", press the settings button beside the about title and add some topics.

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Aqara FP2 Proxmox no pairing

Describe the bug
Got my Aqara FP2 and conected it to my homenetwork. I also find it as an device in the homekit-controller. There is the eye symbol at discovered but no button to connect as I saw in tutorial videos. I connected the device on my iphone and deleted the device in the home app.

Screenshots & Logfiles
IP-A2:4C:4B:FA:66:02 (Presence-Sensor-FP2-4207) found without known pairing data and already paired: ignoring

Versions:

• Adapter version: 0.5.8
• JS-Controller version: 4.0.24
• Node version: 18.17.0
• Operating system: Debian Bullseye in Proxmox LXC

Additional context
iobroker is running in a LXC on Proxmox

Connect Ikea Dirigera pairing failed

Hello Apollon77,
i try to connect my Dirigera with Homekit Controller. When i try to pair with the password, i get this message:

Cannot pair with device IP-FD:88:2B:84:EA:D4 because of error undefined (undefined): connect ECONNREFUSED 192.168.178.84:8000

Did someone connected the Dirigera Hub with Homekit Controller?

Thank you very much and have a nice day!
Greetings
Sascha

Instanz is terminating itself

Describe the bug
Because of many error during the start the instanz stop running.

To Reproduce
Steps to reproduce the behavior:

1. Run Instanz
2. See error

Expected behavior
Running normal

Screenshots & Logfiles
`

2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: Error: undefined is not a valid state value
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at Array.forEach ()
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[0]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: Error: undefined is not a valid state value
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at Array.forEach ()
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: Error: undefined is not a valid state value
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at Array.forEach ()
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-09-20 06:43:35.544 - error: host.Iobroker-prod Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: Error: undefined is not a valid state value
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at Array.forEach ()
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: Error: undefined is not a valid state value
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at Array.forEach ()
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-09-20 06:43:35.545 - error: host.Iobroker-prod instance system.adapter.homekit-controller.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

`

`

2023-09-20 06:43:35.002 - error: homekit-controller.0 (45777) undefined is not a valid state value

2023-09-20 06:43:35.006 - error: homekit-controller.0 (45777) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-09-20 06:43:35.006 - error: homekit-controller.0 (45777) unhandled promise rejection: undefined is not a valid state value
2023-09-20 06:43:35.006 - error: homekit-controller.0 (45777) Error: undefined is not a valid state value

`

Versions:

• Adapter version: <v0.5.8>
• JS-Controller version: <5.0.12>
• Node version: <18.17.1>
• Operating system:

Connection to Homekit Hub is unstable, if polling interval is set to low device gets timeout and cannot reconnect

When using a Homekit like bridge, like 1-Home or other integrations handling multiple devices, the connection is dropped frequently depending on setting of the polling interval.

Example:

Polling every 30 second, stability for 30 minutes than we get a timeout
Polling every 120 second, stability for 1 hour than we get a time out
Polling every 180 seconds, adapter is stable for several hours but at a certain moment also gets a connection time out.

In most cases the connection is picked up again automatically, but after a while (like 10 automated reconnects, it's keeps failing by timeout with error message:

Device  xxxx data polling failed (48): Timeout
Device  xxxx had too many errors, reinitialize connection
xxxx Device initialization already in progress ... ignore call

21:15:50 : adapter got disconnected
22:40:30 : Reboot of adapter did restore the connection as it did not recover by itself

debug log of 5 minutes before up to 5 minutes after send to developer in private message du to content of information

I send 2 debug logs today, the behavior above is that last log and below the step I did for the first one :

12.17 = adapter start
12.18 = set value to all lights (53) with delay of 100ms between each call
awaiting polling of 180sec

12.22 = Values of lights are correct after polling (were incorrect before but ack true)
12.28 = adapter reboo
12.29 = set value to all lights (53) with delay of 100ms between each call lights did not respond
12.31 = polling, values are incorrect
12.31 = set value on a shutter, execution successfully
12.32 = set value on a shutter, execution successfully
12.33 = set value on 1 light, execution successfully
12.34.07 = Polling, values incorrect (not reflecting reality
Adapter reboot, afteer reboot values ar incorrect (see relation to issue #182
12.40 = set value to all lights (53) with delay of 100ms between each call lights did not respond

Please not, al actions are executed with setting usePersistentCOnnections = false
When I set the option to true and set all 50 lights in one go.... nothing gets executed and the connected bridge even looks o hangup (needed reboot of the device to get proper behavior again)

CANT UPDTAE FROM 0.5.8 to 0.5.9

Hello,

i have tried to update via the Webgui, and it run into an error.
Then I have tried to updat eit via ssh, but again error.

Here is the Log from th eupdate. For me its a mess of data.
Maybe somone can find the issue?

HOMEKIT_LOG.txt

Thank you so much
BR
KOAL

Bluetooth Schnittstelle auswählbar machen

Ich setze den Adapter in der Version 0.5.10 ein. Da auf dem Raspi auch der BLE läuft (auf hci0) sollte der HomeKit-controller auf der Schnittstelle hci1 laufen.

Edit:
Der ioBroker läuft als Slave auf einen Raspi mit Debian 12 bookworm und node 18.

Aqara FP2 throws errors in log

Describe the bug
But it seems to work fine. I am still testing it.

homekit-controller.0
	2023-04-30 10:47:24.454	info	Device Aqara-FP2 data polling failed (3): Timeout
homekit-controller.0
	2023-04-30 10:44:54.452	info	Device Aqara-FP2 data polling failed (2): Timeout
homekit-controller.0
	2023-04-30 10:44:23.031	warn	Aqara-FP2 Could not initialize device: TimeoutError: at Object.<anonymous> (/opt/iobroker/node_modules/@esm2cjs/p-queue/build/esm/index.js:16:22) at Module._compile (node:internal/modules/cjs/loader:1196:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10) at Module.load (node:internal/modules/cjs/loader:1074:32) at Function.Module._load (node:internal/modules/cjs/loader:909:12) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:43:35) at Module._compile (node:internal/modules/cjs/loader:1196:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
homekit-controller.0
	2023-04-30 10:42:24.450	info	Device Aqara-FP2 data polling failed (1): Timeout
homekit-controller.0
	2023-04-30 10:41:55.239	info	State value to set for "homekit-controller.0.Aqara-FP2.1.sensor-occupancy-2688.occupancy-detected" has to be type "number" but received type "boolean"
homekit-controller.0
	2023-04-30 10:40:35.950	info	State value to set for "homekit-controller.0.Aqara-FP2.1.sensor-occupancy-2688.occupancy-detected" has to be type "number" but received type "boolean"
homekit-controller.0
	2023-04-30 10:39:22.538	info	State value to set for "homekit-controller.0.Aqara-FP2.1.sensor-occupancy-2688.occupancy-detected" has to be type "number" but received type "boolean"
homekit-controller.0
	2023-04-30 10:39:22.185	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:39:22.185	info	Device Aqara-FP2 data polling failed (47): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:38:45.066	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:38:45.025	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:38:45.025	info	Device Aqara-FP2 data polling failed (46): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:38:14.848	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:38:14.830	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:38:14.830	info	Device Aqara-FP2 data polling failed (45): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:37:44.714	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:37:44.707	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:37:44.707	info	Device Aqara-FP2 data polling failed (44): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:37:14.406	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:37:14.396	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:37:14.396	info	Device Aqara-FP2 data polling failed (43): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:36:44.102	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:36:44.090	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:36:44.090	info	Device Aqara-FP2 data polling failed (42): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:36:13.913	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:36:13.713	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:36:13.713	info	Device Aqara-FP2 data polling failed (41): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:35:43.487	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:35:43.467	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:35:43.467	info	Device Aqara-FP2 data polling failed (40): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:35:13.414	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:35:13.363	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:35:13.363	info	Device Aqara-FP2 data polling failed (39): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:34:43.110	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:34:43.066	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:34:43.066	info	Device Aqara-FP2 data polling failed (38): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:34:12.758	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:34:12.744	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:34:12.744	info	Device Aqara-FP2 data polling failed (37): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:33:42.448	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:33:42.431	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:33:42.430	info	Device Aqara-FP2 data polling failed (36): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:33:12.137	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:33:12.121	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:33:12.120	info	Device Aqara-FP2 data polling failed (35): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:32:42.057	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:32:42.018	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:32:42.017	info	Device Aqara-FP2 data polling failed (34): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:32:11.759	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:32:11.713	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:32:11.713	info	Device Aqara-FP2 data polling failed (33): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:31:41.578	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:31:41.542	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:31:41.541	info	Device Aqara-FP2 data polling failed (32): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:31:11.407	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:31:11.391	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:31:11.390	info	Device Aqara-FP2 data polling failed (31): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:30:41.096	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:30:41.082	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:30:41.081	info	Device Aqara-FP2 data polling failed (30): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:30:10.957	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:30:10.943	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:30:10.943	info	Device Aqara-FP2 data polling failed (29): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:29:40.779	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:29:40.768	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:29:40.768	info	Device Aqara-FP2 data polling failed (28): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:29:10.567	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:29:10.555	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:29:10.555	info	Device Aqara-FP2 data polling failed (27): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:28:40.363	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:28:40.349	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:28:40.349	info	Device Aqara-FP2 data polling failed (26): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:28:09.902	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:28:09.885	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:28:09.885	info	Device Aqara-FP2 data polling failed (25): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:27:39.760	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:27:39.740	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:27:39.740	info	Device Aqara-FP2 data polling failed (24): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:27:09.435	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:27:09.419	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:27:09.419	info	Device Aqara-FP2 data polling failed (23): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:26:39.248	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:26:39.235	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:26:39.235	info	Device Aqara-FP2 data polling failed (22): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:25:53.555	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:25:53.539	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:25:53.539	info	Device Aqara-FP2 data polling failed (21): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:25:22.469	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:25:22.448	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:25:22.447	info	Device Aqara-FP2 data polling failed (20): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:24:52.318	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:24:52.300	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:24:52.300	info	Device Aqara-FP2 data polling failed (19): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:24:22.222	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:24:22.197	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:24:22.197	info	Device Aqara-FP2 data polling failed (18): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:23:51.898	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:23:51.886	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:23:51.886	info	Device Aqara-FP2 data polling failed (17): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:23:21.585	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:23:21.575	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:23:21.575	info	Device Aqara-FP2 data polling failed (16): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:22:51.341	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:22:51.298	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:22:51.298	info	Device Aqara-FP2 data polling failed (15): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:22:18.030	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:22:17.988	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:22:17.987	info	Device Aqara-FP2 data polling failed (14): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:21:47.694	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:21:47.674	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:21:47.674	info	Device Aqara-FP2 data polling failed (13): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:21:17.378	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:21:17.366	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:21:17.366	info	Device Aqara-FP2 data polling failed (12): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:20:46.042	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:20:46.028	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:20:46.028	info	Device Aqara-FP2 data polling failed (11): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:20:15.739	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:20:15.717	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:20:15.717	info	Device Aqara-FP2 data polling failed (10): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:19:45.429	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:19:45.406	warn	Device Aqara-FP2 had too many errors, reinitialize connection
homekit-controller.0
	2023-04-30 10:19:45.406	info	Device Aqara-FP2 data polling failed (9): connect ECONNREFUSED 192.168.178.142:54355
homekit-controller.0
	2023-04-30 10:19:15.257	warn	Aqara-FP2 Could not initialize device: connect ECONNREFUSED 192.168.178.142:54355 Error: connect ECONNREFUSED 192.168.178.142:54355 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
homekit-controller.0
	2023-04-30 10:19:15.243	warn	Device Aqara-FP2 had too many errors, reinitialize connection

RAM issue - increasing > 4GB / already discussed on Test Alpha Homekit-Controller

The RAM used by the Adapter is constantly increasing (>4 GB) while the adapter is running. After a restart of the Adapter the RAM is resetted to 0 and then increasing again.

The values at the system Datapoints memRss and both heap are showing different values than the osx system activity board.

This Topic was already discussed with @Apollon77 at the Test Alpha Homekit-Controller Forum - here

Workaround - restarting the adapter daily via restart schedule

JS-Controller version - 4.0.24
Node.js v16.17.0
NPM 8.15.0
macOS 10.14.6 Mojave

Any help is appreciated - regards

Only polling new values if adapter is restarted

Hey,

first, thank you for developing this adapter!

I use it with the new IKEA Dirigera and it's working.
Only problem is, that the values are only updated, if I restart des instance of the adapter ?
Is this a known issue ?
Do I have to configure something different maybe ?

Regards and thank you for all the work,
Ronald

Adapter restart loop

Hallo Ingo,

Mein Iobroker läuft im stable-Modus. Seit knapp 1 Jahr habe ich deinen Adapter zur Anbindung des Aqara-Hubs M3 bis dato problemlos und zuverlässig im Einsatz.

Seit dem Update des JS-Adapters auf 7.1.4 und dem notwendigen Update auf Nodejs 18.x häufen sich die Fehler im Homekit-Controller-Adapter. Immer wieder stoppt der Iobroker-Host den Adapter und gibt mir folgende Fehlermeldung:

—————————————————

2023-10-03 21:26:06.296 - error: homekit-controller.0 (13906) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

2023-10-03 21:26:06.298 - error: homekit-controller.0 (13906) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:06.368 - error: homekit-controller.0 (13906) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.368 - error: homekit-controller.0 (13906) undefined is not a valid state value
2023-10-03 21:26:06.374 - error: homekit-controller.0 (13906) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:06.374 - error: homekit-controller.0 (13906) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:06.375 - error: homekit-controller.0 (13906) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.375 - error: homekit-controller.0 (13906) undefined is not a valid state value
2023-10-03 21:26:06.376 - error: homekit-controller.0 (13906) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:06.376 - error: homekit-controller.0 (13906) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:06.377 - error: homekit-controller.0 (13906) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.377 - error: homekit-controller.0 (13906) undefined is not a valid state value
2023-10-03 21:26:06.378 - error: homekit-controller.0 (13906) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:06.378 - error: homekit-controller.0 (13906) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:06.379 - error: homekit-controller.0 (13906) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.379 - error: homekit-controller.0 (13906) undefined is not a valid state value
2023-10-03 21:26:06.387 - warn: homekit-controller.0 (13906) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-03 21:26:06.955 - error: host.iobroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: Error: undefined is not a valid state value
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at Array.forEach ()
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: Error: undefined is not a valid state value
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at Array.forEach ()
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: Error: undefined is not a valid state value
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at Array.forEach ()
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[4]: Error: undefined is not a valid state value
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[4]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[4]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:06.956 - error: host.iobroker Caught by controller[4]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:06.957 - error: host.iobroker Caught by controller[4]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:06.957 - error: host.iobroker Caught by controller[4]: at Array.forEach ()
2023-10-03 21:26:06.957 - error: host.iobroker Caught by controller[4]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:06.957 - error: host.iobroker Caught by controller[4]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:06.957 - error: host.iobroker Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:06.957 - error: host.iobroker instance system.adapter.homekit-controller.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-03 21:26:15.088 - error: homekit-controller.0 (13921) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:15.089 - error: homekit-controller.0 (13921) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:15.158 - error: homekit-controller.0 (13921) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.158 - error: homekit-controller.0 (13921) undefined is not a valid state value
2023-10-03 21:26:15.164 - error: homekit-controller.0 (13921) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:15.164 - error: homekit-controller.0 (13921) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:15.165 - error: homekit-controller.0 (13921) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.165 - error: homekit-controller.0 (13921) undefined is not a valid state value
2023-10-03 21:26:15.167 - error: homekit-controller.0 (13921) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:15.167 - error: homekit-controller.0 (13921) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:15.168 - error: homekit-controller.0 (13921) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.168 - error: homekit-controller.0 (13921) undefined is not a valid state value
2023-10-03 21:26:15.169 - error: homekit-controller.0 (13921) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:15.169 - error: homekit-controller.0 (13921) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:15.170 - error: homekit-controller.0 (13921) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.170 - error: homekit-controller.0 (13921) undefined is not a valid state value
2023-10-03 21:26:15.182 - warn: homekit-controller.0 (13921) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: Error: undefined is not a valid state value
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at Array.forEach ()
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: Error: undefined is not a valid state value
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at Array.forEach ()
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: Error: undefined is not a valid state value
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at Array.forEach ()
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.765 - error: host.iobroker Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: Error: undefined is not a valid state value
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at Array.forEach ()
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:15.766 - error: host.iobroker Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:15.766 - error: host.iobroker instance system.adapter.homekit-controller.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-03 21:26:24.129 - error: homekit-controller.0 (13936) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:24.131 - error: homekit-controller.0 (13936) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:24.198 - error: homekit-controller.0 (13936) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.199 - error: homekit-controller.0 (13936) undefined is not a valid state value
2023-10-03 21:26:24.205 - error: homekit-controller.0 (13936) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:24.205 - error: homekit-controller.0 (13936) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:24.206 - error: homekit-controller.0 (13936) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.206 - error: homekit-controller.0 (13936) undefined is not a valid state value
2023-10-03 21:26:24.208 - error: homekit-controller.0 (13936) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:24.208 - error: homekit-controller.0 (13936) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:24.209 - error: homekit-controller.0 (13936) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.209 - error: homekit-controller.0 (13936) undefined is not a valid state value
2023-10-03 21:26:24.210 - error: homekit-controller.0 (13936) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2023-10-03 21:26:24.210 - error: homekit-controller.0 (13936) unhandled promise rejection: undefined is not a valid state value
2023-10-03 21:26:24.211 - error: homekit-controller.0 (13936) Error: undefined is not a valid state value
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
at Array.forEach ()
at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.211 - error: homekit-controller.0 (13936) undefined is not a valid state value
2023-10-03 21:26:24.222 - warn: homekit-controller.0 (13936) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: Error: undefined is not a valid state value
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at Array.forEach ()
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: Error: undefined is not a valid state value
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at Array.forEach ()
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: Error: undefined is not a valid state value
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at Array.forEach ()
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[4]: Error: undefined is not a valid state value
2023-10-03 21:26:24.795 - error: host.iobroker Caught by controller[4]: at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/maybeCallback.ts:136:17)
2023-10-03 21:26:24.796 - error: host.iobroker Caught by controller[4]: at HomekitController._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7594:26)
2023-10-03 21:26:24.796 - error: host.iobroker Caught by controller[4]: at HomekitController.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7552:21)
2023-10-03 21:26:24.796 - error: host.iobroker Caught by controller[4]: at /opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:745:26
2023-10-03 21:26:24.796 - error: host.iobroker Caught by controller[4]: at Array.forEach ()
2023-10-03 21:26:24.796 - error: host.iobroker Caught by controller[4]: at HomekitController.setCharacteristicValues (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:734:32)
2023-10-03 21:26:24.796 - error: host.iobroker Caught by controller[4]: at Timeout. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:702:30)
2023-10-03 21:26:24.796 - error: host.iobroker Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-10-03 21:26:24.796 - error: host.iobroker instance system.adapter.homekit-controller.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-10-03 21:26:24.796 - warn: host.iobroker Do not restart adapter system.adapter.homekit-controller.0 because restart loop detected

—————————————————

Kannst du mir helfen herauszufinden, wo ich den Fehler gemacht habe?

Upgrade 0.5.8 to 0.5.9 fails

While trying to upgrade (iob - latest version, latest npm, node, etc) system throws errors.

iobroker npm ERR! code 1npm ERR! path /opt/iobroker/node_modules/@abandonware/noblenpm ERR! command failednpm ERR! command sh -c node-gyp-buildnpm ERR! make: Entering directory '/opt/iobroker/node_modules/@abandonware/noble/build'npm ERR! SOLINK_MODULE(target) Release/obj.target/noble.nodenpm ERR! make: Leaving directory '/opt/iobroker/node_modules/@abandonware/noble/build'npm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using [email protected] ERR! gyp info using [email protected] | linux | x64npm ERR! gyp info find Python using Python version 3.11.6 found at "/usr/bin/python3"npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/@abandonware/noble/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/20.10.0/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/20.10.0',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/20.10.0/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/@abandonware/noble',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! gyp info spawn makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! make: g++: No such file or directorynpm ERR! make: *** [noble.target.mk:22: Release/obj.target/noble.node] Error 127npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: make failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23)npm ERR! gyp ERR! System Linux 6.5.11-4-pvenpm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@abandonware/noblenpm ERR! gyp ERR! node -v v20.10.0npm ERR! gyp ERR! node-gyp -v v10.0.1npm ERR! gyp ERR! not oknpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-09T04_27_07_224Z-debug-0.loghost.brain-iobroker Cannot install [email protected]: 1

iobroker npm ERR! command failednpm ERR! command sh -c node-gyp-buildnpm ERR! make: Entering directory '/opt/iobroker/node_modules/@abandonware/noble/build'npm ERR! SOLINK_MODULE(target) Release/obj.target/noble.nodenpm ERR! make: Leaving directory '/opt/iobroker/node_modules/@abandonware/noble/build'npm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using [email protected] ERR! gyp info using [email protected] | linux | x64npm ERR! gyp info find Python using Python version 3.11.6 found at "/usr/bin/python3"npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',npm ERR! gyp info spawn args 'binding.gyp',npm ERR! gyp info spawn args '-f',npm ERR! gyp info spawn args 'make',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/opt/iobroker/node_modules/@abandonware/noble/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/20.10.0/include/node/common.gypi',npm ERR! gyp info spawn args '-Dlibrary=shared_library',npm ERR! gyp info spawn args '-Dvisibility=default',npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/20.10.0',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/20.10.0/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/@abandonware/noble',npm ERR! gyp info spawn args '-Dnode_engine=v8',npm ERR! gyp info spawn args '--depth=.',npm ERR! gyp info spawn args '--no-parallel',npm ERR! gyp info spawn args '--generator-output',npm ERR! gyp info spawn args 'build',npm ERR! gyp info spawn args '-Goutput_dir=.'npm ERR! gyp info spawn args ]npm ERR! gyp info spawn makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! make: g++: No such file or directorynpm ERR! make: *** [noble.target.mk:22: Release/obj.target/noble.node] Error 127npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: make failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23)npm ERR! gyp ERR! System Linux 6.5.11-4-pvenpm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@abandonware/noblenpm ERR! gyp ERR! node -v v20.10.0npm ERR! gyp ERR! node-gyp -v v10.0.1npm ERR! gyp ERR! not oknpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-09T04_27_07_224Z-debug-0.log

[Adjust logLevel] warn instead of info for "Timeout issues"

Current situation as log if a timeout occurs :

2022-07-04T19:01:38.8490000Z | Information | homekit-controller.0 (262672) xxxx Could not initialize device:  TimeoutError: 

Proposed situation as log if a timeout occurs :

2022-07-04T19:01:38.8490000Z | Warning | homekit-controller.0 (262672) xxxx Could not initialize device:  TimeoutError: 

Could not initialize device: TimeoutError: at Object.<anonymous>

Hi i got a Velux Gateway and got these errors:

homekit-controller.0	2023-06-23 07:49:59.138	warn	Device IP-25:86:3F:E3:A0:97 had too many errors, reinitialize connection
homekit-controller.0	2023-06-23 07:48:17.913	warn	IP-25:86:3F:E3:A0:97 Could not initialize device: TimeoutError: at Object. (/opt/iobroker/node_modules/@esm2cjs/p-queue/build/esm/index.js:16:22) at Module._compile (node:internal/modules/cjs/loader:1196:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10) at Module.load (node:internal/modules/cjs/loader:1074:32) at Function.Module._load (node:internal/modules/cjs/loader:909:12) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at Object. (/opt/iobroker/node_modules/iobroker.homekit-controller/build/main.js:43:35) at Module._compile (node:internal/modules/cjs/loader:1196:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)

When i restart the adapter, these issue is still there but i can control the windows for an couple of hours.

Adapter crashes occasionally

Hi, I've been using the HomeKit Controller Adapter v. 0.4.4 for a few months now without any problems :-)
Unfortunately, the instance crashes occasionally, about once every 1-2 weeks.
After a restart, everything runs normally again.
Here is my log from today.

iobroker.2022-06-05.log

Use real name for device object

Add channels and devices.
And use real name for devices:

Configuration Page empty

Hi,
thx for this adapter.
Version 0.5.8 shows all Entrys in Configuration page.
Version 0.5.9 works with this enabled Entry, but Configuration-Window is empty.
(no add, save, cancel ...)(Aquara FP2 enabled in 0.5.8 works)
nodejs: 18.19.0
npm: 10.2.3
debian bookworm
can you help?

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Seite Instanzeinstellungen bleibt leer

Mit Version 0.5.9 bleibt die Seite mit den Instanzeinstellungen leer.
Nach Downgrade auf 0.5.8 geht's wieder.
Wieder zurück auf die 0.5.9: Seite bleibt leer.
Das Ganze mit verschiedenen Browsern getestet ( Chrome, FF, Edge, Safari)

JS-Controller: 5.0.17
Node.js: v18.19.0
NPM: 10.2.3

Aqara in different subnet not reachable

Hi,

I have ioBroker running with homekit-controller and successfully paired an Aqara (FP2) device with both iobroker and aqara being in the same network "A".

I want to use Aqara at another location "B" with an own network. Both networks A (192.168.178.0/24) and B (192.168.22.0/24) are connected trough a constant VPN tunnel and can communicate among each others. Also both locations A and B have WiFi with the same SSID and password.

The Aqara device successfully connects to the WiFi at location B, it also shows as available and functioning in the Aqara app. ioBroker/homekit-controller can't find it though.

I changed the IP-value [.../info/addess] of the object in ioBroker - which didn't seem to make any difference, connection was still made to the .178.xx IP of network A which was stored after pairing the device. So I hardcoded the new IP address .22.xx of network B in node_modules\iobroker.homekit-controller\build\main.js to try it out, debug log shows that the connection is going out to the correct IP from network B. But - it times out.

So my question is now, whether I am missing something or if what I want to achieve isn't possible at all. I understand this is more of a support request than an issue/bug, but I hope I can get some help or at least a pointer in the right direction here.

Cheers
Michael