# \[APP\]\[Pro\] HomeKit Controller voor Homey (NL) **URL:** \ **Category:** Apps\ **Tags:** webapp, homey-pro, community-app\ **Created:** [October 27, 2023, 9:17pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007 "2023-10-27T21:17:43Z")\ **Posts on this page:** 20\ **Page:** 24
**Author:** ![Bazeloth](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bazeloth/32/79224_2.png) [@Bazeloth](https://community.homey.app/u/Bazeloth)\ **Post date:** [December 11, 2024, 4:18pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/473 "2024-12-11T16:18:21Z")
En deel 2: ```auto 2024-12-11T16:03:39.799Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:03:36.681Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:03:36.679Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:03:36.678Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:03:26.760Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion2 2 Occupancy Zone 2 {"aid":1,"iid":2698,"value":0} 2024-12-11T16:03:25.642Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion0 0 Occupancy Zone 0 {"aid":1,"iid":2690,"value":0} 2024-12-11T16:03:09.797Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:03:09.796Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:03:09.754Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:03:09.751Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:03:06.621Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:03:06.621Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:03:06.621Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:02:39.722Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:02:39.722Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:02:39.704Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:02:39.703Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:02:36.578Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:02:36.578Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:02:36.577Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:02:36.244Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion2 2 Occupancy Zone 2 {"aid":1,"iid":2698,"value":1} 2024-12-11T16:02:36.242Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar measure_luminance null No name {"aid":1,"iid":2674,"value":5} 2024-12-11T16:02:35.239Z [log] [ManagerDrivers] [Driver:hapIP] [Device:5837430a-9e86-4588-aa23-87353af0545d] processEventChar alarm_motion0 0 Occupancy Zone 0 {"aid":1,"iid":2690,"value":1} 2024-12-11T16:02:09.676Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:02:09.675Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:02:09.656Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:02:09.655Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:02:06.537Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:02:06.537Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:02:06.536Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:01:39.632Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:01:39.632Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:01:39.578Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:01:39.575Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:01:36.487Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:01:36.486Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:01:36.486Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:01:09.580Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:01:09.580Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:01:09.529Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:01:09.527Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:01:06.413Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:01:06.413Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:01:06.413Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:00:39.473Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:00:39.473Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:00:39.448Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:00:39.447Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:00:36.329Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:00:36.329Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:00:36.329Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T16:00:09.458Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T16:00:09.458Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T16:00:09.403Z [log] Socket close 192.168.68.69 63545 2024-12-11T16:00:09.399Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T16:00:06.271Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T16:00:06.271Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T16:00:06.270Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:59:39.349Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:59:39.349Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:59:39.320Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:59:39.319Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:59:36.199Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:59:36.199Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:59:36.197Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:59:09.269Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:59:09.268Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:59:09.240Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:59:09.239Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:59:06.123Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:59:06.123Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:59:06.122Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:58:39.222Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:58:39.222Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:58:39.193Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:58:39.191Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:58:36.050Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:58:36.049Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:58:36.048Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:58:09.167Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:58:09.166Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:58:09.113Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:58:09.111Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:58:06.008Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:58:06.008Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:58:06.008Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:57:39.116Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:57:39.116Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:57:39.066Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:57:39.063Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:57:35.955Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:57:35.954Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:57:35.954Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:57:09.069Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:57:09.069Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:57:09.017Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:57:09.015Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:57:05.875Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:57:05.875Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:57:05.874Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:56:38.992Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:56:38.991Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:56:38.938Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:56:38.935Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:56:35.833Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:56:35.832Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:56:35.832Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:56:08.915Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:56:08.915Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:56:08.888Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:56:08.887Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:56:05.780Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:56:05.780Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:56:05.780Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:55:38.869Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:55:38.869Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:55:38.840Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:55:38.839Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:55:35.718Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:55:35.718Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:55:35.717Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:55:08.819Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:55:08.819Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:55:08.792Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:55:08.791Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:55:05.650Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:55:05.647Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:55:05.645Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:54:38.743Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:54:38.742Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:54:38.712Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:54:38.711Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:54:35.594Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:54:35.593Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:54:35.592Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:54:08.683Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:54:08.683Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:54:08.633Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:54:08.631Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:54:05.519Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:54:05.518Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:54:05.518Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:53:38.635Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:53:38.635Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:53:38.586Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:53:38.583Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:53:35.458Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:53:35.457Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:53:35.457Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:53:08.555Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:53:08.554Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:53:08.506Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:53:08.503Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:53:05.386Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:53:05.385Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:53:05.385Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:52:38.497Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:52:38.497Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:52:38.457Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:52:38.455Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:52:35.319Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:52:35.318Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:52:35.317Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:52:08.404Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:52:08.404Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:52:08.376Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:52:08.375Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:52:05.249Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:52:05.248Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:52:05.247Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:51:38.350Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:51:38.349Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:51:38.297Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:51:38.295Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:51:35.212Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:51:35.212Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:51:35.211Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:51:08.279Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:51:08.279Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:51:08.248Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:51:08.247Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:51:05.162Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:51:05.161Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection 2024-12-11T15:51:05.161Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.NOCONNECTION Presence-Sensor-FP2-835D 2024-12-11T15:50:38.279Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-968B._hap._tcp.local 65020 2024-12-11T15:50:38.279Z [err] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D error from getAccessories, Error: connect EHOSTUNREACH 192.168.68.69:63545, => Waiting on UP 2024-12-11T15:50:38.233Z [log] Socket close 192.168.68.69 63545 2024-12-11T15:50:38.231Z [err] Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545 2024-12-11T15:50:35.102Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] Presence-Sensor-FP2-835D setupConnection for 92:9A:0A:4B:48:D6 on 192.168.68.69:63545, existing client true 2024-12-11T15:50:35.101Z [log] [ManagerDrivers] [Driver:hapIP] [Device:1ec19066-9288-4605-a5b0-143315186acf] checkConnectionState.requestNewConnections Presence-Sensor-FP2-835D request new Connection ``` ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [December 11, 2024, 4:51pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/474 "2024-12-11T16:51:12Z")
Sensor met IP .68.69 is onbereikbaar > [@Bazeloth](#): > > `Socket error 192.168.68.69 63545 connect EHOSTUNREACH 192.168.68.69:63545` ---
**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\ **Post date:** [December 11, 2024, 5:03pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/475 "2024-12-11T17:03:36Z")
de app is continue met 835D bezig om die bereikbaar te maken, power cycle die eens… ---
**Author:** ![Bazeloth](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/bazeloth/32/79224_2.png) [@Bazeloth](https://community.homey.app/u/Bazeloth)\ **Post date:** [December 11, 2024, 7:36pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/476 "2024-12-11T19:36:20Z")
Thanks. “Did you try turning it off and on again?”. Classic, maar het heeft geholpen. ---
**Author:** ![Remco\_95](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/remco_95/32/121246_2.png) [@Remco\_95](https://community.homey.app/u/Remco_95)\ **Post date:** [December 18, 2024, 11:34am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/477 "2024-12-18T11:34:34Z")
Wie kan mij helpen met het volgende?; Ik heb een Aqara deurbel die goed werkt nu met HomeKit, maar nu wil ik deze graag toevoegen aan Homey. Het zou top zijn als ik bijvoorbeeld het geluid kan laten afspelen via Sonos. Helaas lukt het toevoegen niet via de Homey-Aqara app. Ergens las ik dat er een omweg zou zijn met HomeKit controller, maar hij ziet ‘m niet wanneer ik de deurbel zoek. Nog redelijk nieuw met Homey, dus iemand in wat makkelijke taal/stappen een oplossing? Alvast bedankt! ---
**Author:** ![MichZ](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michz/32/16621_2.png) [@MichZ](https://community.homey.app/u/MichZ)\ **Post date:** [December 19, 2024, 7:21am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/478 "2024-12-19T07:21:38Z")
Ik denk dat je hem eerst moet verwijderen uit de homekit pagina in de Aqara app. Daarna zal je hem waarschijnlijk kunnen koppelen aan de homekit controller app van Homey. ---
**Author:** ![Remco\_95](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/remco_95/32/121246_2.png) [@Remco\_95](https://community.homey.app/u/Remco_95)\ **Post date:** [December 20, 2024, 9:01am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/480 "2024-12-20T09:01:11Z")
Bedankt, ik ga het proberen! ---
**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\ **Post date:** [December 20, 2024, 8:01pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/481 "2024-12-20T20:01:14Z")
Een homekit device kan maar 1 Controller hebben. Als device bv via iOS wordt toegevoegd in Aqara komt die automatisch in home app van Apple. Daar moet je hem eerst verwijderen. ---
**Author:** ![Remco\_95](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/remco_95/32/121246_2.png) [@Remco\_95](https://community.homey.app/u/Remco_95)\ **Post date:** [December 23, 2024, 1:05pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/482 "2024-12-23T13:05:36Z")
Even puzzelen maar het werkt inderdaad! Live beeld is enkel te zien in de app van Aqara, maar ik begreep dat daar voor geen enkele camera nu ondersteuning is in Homey(?). Hier mee al blij! Thnx voor de hulp. ---
**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\ **Post date:** [December 23, 2024, 2:20pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/483 "2024-12-23T14:20:04Z")
> [@Remco\_95](#): > > maar ik begreep dat daar voor geen enkele camera nu ondersteuning is in Homey(?) Dat is correct ---
**Author:** ![Benvo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/benvo/32/79462_2.png) [@Benvo](https://community.homey.app/u/Benvo)\ **Post date:** [December 27, 2024, 7:41pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/484 "2024-12-27T19:41:47Z")
@Martin_Verbeek Wanneer ik een Aqara camera toevoegt aan Homey via HomeKit Controller verliest de camera dan de mogelijkheid om beelden op te slaan in ICloud? ---
**Author:** ![Benvo](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/benvo/32/79462_2.png) [@Benvo](https://community.homey.app/u/Benvo)\ **Post date:** [December 28, 2024, 2:29pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/485 "2024-12-28T14:29:10Z")
Hoi Matthew, Weet jij toevallig of je de mogelijkheid tot video opnames in iCloud opslaan verliest zodra je de Aqara camera’s koppels met de HomeKit controller app? ---
**Author:** ![JB96](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jb96/32/78856_2.png) [@JB96](https://community.homey.app/u/JB96)\ **Post date:** [January 15, 2025, 11:50am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/486 "2025-01-15T11:50:08Z")
Ik heb de G4 gekoppeld met IFTTT ertussen. Werkt goed! ---
**Author:** ![AHU](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ahu/32/35686_2.png) [@AHU](https://community.homey.app/u/AHU)\ **Post date:** [January 18, 2025, 11:20pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/487 "2025-01-18T23:20:14Z")
Ik heb 3 Aqara FP2 sensoren. 2 waren reeds een tijdje werkend op FW 2.7.x. Prima. De derde was net nieuw, was werkend op een oudere Firmware (ergens voor de 2.7.x.) Deze iets te ondoordacht geüpdatet naar FW 3.0.0. Het MAC adres was hierdoor ook veranderd ( WAAROM gebeurt dat??) dus de IP reservering moest weer worden aangepast. Doorgevoerd… Krijgt het juiste IP, dat is allemaal goed, werkt ook in de Aqara app. Lang verhaal kort: Deze met FW wordt niet meer in de Homey HC app herkend. Morgen nog maar eens helemaal resetten, kijken of het de oplossing is. Wees dus gewaarschuwd! ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [January 19, 2025, 3:54am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/488 "2025-01-19T03:54:10Z")
> [@AHU](#): > > Het MAC adres was hierdoor ook veranderd ( WAAROM gebeurt dat??) In dit geval OMDAT: > [@Aqara FP2, mmWave presence detection on WiFi](https://community.homey.app/t/aqara-fp2-mmwave-presence-detection-on-wifi/76955/469): > > From what I’m [reading](https://www.reddit.com/r/Aqara/comments/1c2l372/comment/kzso4q6/), the reason for the change is that the MAC prefix was changed from a range belonging to Xiaomi to a range belonging to Lumi/Aqara. > [@AHU](#): > > Deze met FW wordt niet meer in de Homey HC app herkend. > Wees dus gewaarschuwd! Voor? Is het niet gewoon een beter idee om de HC app ontwikkelaar Martin even op een vriendelijke manier op de hoogte te brengen van je bevindingen? 🤷‍♂️ ---
**Author:** ![AHU](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ahu/32/35686_2.png) [@AHU](https://community.homey.app/u/AHU)\ **Post date:** [January 19, 2025, 12:51pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/489 "2025-01-19T12:51:03Z")
Ik was niet op de hoogte van de wijziging van MAC adres om deze reden, dat had wel bij de releasenotes mogen staan denk ik zo. Ik mag aannemen dat de fabrikant wel weet wat hij doet en mag? Goed om te weten wat de reden is. Bij een volgende FW update zal het dus niet meer wijzigen, mag ik aannemen. Dank voor de info. Wie denkt dat ik de ontwikkelaar niet dankbaar ben? Ik ben de ontwikkelaar van de HC app zeker dankbaar voor zijn werk, laat dat duidelijk zijn, knap werk! Ik wilde alleen laten weten dat ik de ervaring heb dat bij de update naar 1.3.0.xx (ik heb de firmware versies eerder onjuist vermeld, maar denk wel dat de meesten onder ons wel weten welke versies bedoeld werden) voor mij de FP2 niet meer herkend wordt. Ik zal hem eerst nog naar Factory default brengen voor een derde poging. Het is via tekst niet helemaal goed overgekomen. ---
**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\ **Post date:** [January 20, 2025, 9:08pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/490 "2025-01-20T21:08:31Z")
Toen ik de app ontwikkelde had ik het briljante idee dat de MAC als ID in Homey te gebruiken 😳. De FP2 veranderd dus zijn MAC als hij gereset wordt. En dan raak je dus de connectie kwijt tussen Homey en de FP2. Ben bezig die verbinding op een andere manier te leggen zonder de bestaande devices in de problemen komen. Enige manier op DIT moment om FP2 die gereset is te verwijderen uit Homey en opnieuw te pairen Dit geldt alleen voor een totale reset van de FP2, dus niet voor de 10s netwerk instellingen reset😅 ---
**Author:** ![AHU](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ahu/32/35686_2.png) [@AHU](https://community.homey.app/u/AHU)\ **Post date:** [January 20, 2025, 9:45pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/491 "2025-01-20T21:45:50Z")
Ik heb gisteren de FP2 uit Homey verwijderd, geheel naar fabrieksinstellingen gebracht en blijkt FW 1.3.x geen probleem. En dat is mooi. Dank voor de uitleg. ---
**Author:** ![Mathias\_Deloof](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/mathias_deloof/32/79343_2.png) [@Mathias\_Deloof](https://community.homey.app/u/Mathias_Deloof)\ **Post date:** [March 6, 2025, 11:05am UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/492 "2025-03-06T11:05:01Z")
Vraagje over HomeKit Controller app: Ik kwam onlangs de Eve Flare tegen, wat me wel een interessant leek. Deze is enkel te koppelen met HomeKit. Als ik het goed begrijp kan ik via deze app deze lamp wel koppelen aan Homey? Alvast bedankt voor het antwoord :)! ---
**Author:** ![Martin\_Verbeek](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_verbeek/32/10641_2.png) [@Martin\_Verbeek](https://community.homey.app/u/Martin_Verbeek)\ **Post date:** [March 6, 2025, 4:57pm UTC](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007/493 "2025-03-06T16:57:00Z")
Als het Homekit via WiFi is en je hebt een 8 cijferige pair code, dan zou het moeten werken. EDIT… ik kijk net even en dit ziet eruit als een lamp met Thread, dat werkt dus weer niet… [Previous page](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007.md?page=23) [Next page](https://community.homey.app/t/app-pro-homekit-controller-voor-homey-nl/93007.md?page=25)