[APP][Pro] HomeKit Controller - for a better Homey

Looks like a different issue, nothing significant was changed in that part of code. If available, can you goto the app log and PM me the log of that event?

1.3.17 with 12.2.0 support is now live.

Would it be possible to get sleep/awake status from PF2-sensor? I have changed the PF2 to ā€œsleep monitorā€ in Aqara app but only get status on presence in Homey.

1 Like

Need to test if that is possible

2 Likes

No info is provided via FP2 homekit to support that.

1 Like

Hey. i just bought an Aqara FP2 but i can’t connect it to my Homey Pro via Homekit. I’ve tried connecting it to the Aqara Home app as well but that won’t help. In some tries i seem to get communication with the sensor judging by the log;

undefined2024-11-21T08:07:42.540Z [log] [MyApp] cpu warning
2024-11-21T08:07:32.812Z [log] [ManagerDrivers] [Driver:hapIP] hapIP driver has been initialized 2024-11-21T08:07:32.811Z [log] [ManagerDrivers] [Driver:hapIP] discoveredHapBonjour devices Ready start browsing your network
2024-11-21T08:07:32.808Z [log] [ManagerDrivers] [Driver:hapIP] discoverDevicesBonjour
2024-11-21T08:07:32.547Z [log] [MyApp] Homekit Controller 1.3.18 has been initialized
2024-11-21T08:07:32.546Z [log] capturing stderr
2024-11-21T08:07:32.546Z [log] capturing stdout
2024-11-21T08:07:31.558Z [log] [MyApp] app unload called
2024-11-21T08:05:46.643Z [log] [ManagerDrivers] [Driver:hapIP] Bonjour Down Presence-Sensor-FP2-3B15._hap._tcp.local

Any ideas how to solve it?

The app crashes very frequently for me after latest update. Diagnostic report: 8f73cb29-6793-4c1c-9b66-5b630da2b8de

can you explain a bit more, i have 1 crash and your diagnostic in 3000 installs with this version :wink:

I thought you would easily see the details in the diagnostics file; Whenever I add either a smart plug from DoHome, or remove it, restart both Homey Pro and the app, and add a smart plug from Athom, the app starts to crash every 5 minutes to 15 minutes or so.

Whatever HomeKit smart plug in other words. Which is so odd to me considering it’s the simplest device.

The only log item I can recognise as relevant to the crashing is a high cpu warning, which is shown as at 100% in the app performance section of the developer tools (just above 0% usually).

I’m on the latest (non-beta) firmware for the Homey Pro early 2023 and latest HomeKit Controller app.

Side note: I do also have some HomeKit air purifiers added as devices via the HC app, and they lose connection or just won’t be controlled from Homey, but those are complex and probably non-standard HomeKit devices, so I haven’t made any bug reports for them. I’ve never had any issues similar to this with HomeKit, home.app or Home Assistant’s HomeKit integration.

Do you already have the device added or is that impossible? If it is added goto device and settings then pm me JSON field of both the doHome and the purifier.

Hi @Martin_Verbeek, I’ve just added an RA Pulse 2 Hub and have been able to add the window shade devices, however when trying to operate the new devices I’m getting errors for the bridge device.

Have I miss configured something or missing a step to get this working correctly?

I’ve pasted a copy of the log entries for the error below.

undefined2024-11-28T10:43:06.138Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] Front Gate._hap._tcp.local 80
2024-11-28T10:43:06.138Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] LG webOS TV E215._hap._tcp.local 38651
2024-11-28T10:43:06.138Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] RA-Pulse-1012467._hap._tcp.local 80
2024-11-28T10:43:06.138Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] Garage._hap._tcp.local 80
2024-11-28T10:43:06.137Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] Aqara-Hub-E1-8202._hap._tcp.local 42889
2024-11-28T10:43:06.137Z [err] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] RA-Pulse-1012467 error from writeCharacteristic.setCharacteristics, Error: Accessory received an invalid value in a write request., => Waiting on UP
2024-11-28T10:43:06.122Z [err] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] Office (Left) ValueUpdate Error: Accessory received an invalid value in a write request.
    at /app/drivers/hapIP/device.js:438:10
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-11-28T10:43:06.120Z [err] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] RA-Pulse-1012467 writeCharacteristic Error { '12.9': 10000 } {"aid":12,"iid":9,"status":-70410}
2024-11-28T10:43:06.084Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] writeCharacteristic { '12.9': 10000 }
2024-11-28T10:43:06.081Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] {
  iid: 9,
  value: 0,
  type: '0000007C-0000-1000-8000-0026BB765291',
  perms: [ 'pr', 'pw', 'ev' ],
  ev: false,
  format: 'uint8',
  minValue: 0,
  maxValue: 100,
  minStep: 1,
  unit: 'percentage',
  capability: 'windowcoverings_set',
  lastUpdated: 1732790471550
}
2024-11-28T10:43:03.047Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] RA-Pulse-1012467 writeCharacteristic success {
  characteristics: [ { aid: [BigNumber], iid: [BigNumber], value: 0 } ]
} windowcoverings_set 0 0
2024-11-28T10:43:02.984Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] writeCharacteristic { '12.9': 0 }
2024-11-28T10:43:02.982Z [log] [ManagerDrivers] [Driver:hapIP] [Device:ac758b8c-e604-4407-8b6e-5d05bdd73ce6] {
  iid: 9,
  value: 0,
  type: '0000007C-0000-1000-8000-0026BB765291',
  perms: [ 'pr', 'pw', 'ev' ],
  ev: false,
  format: 'uint8',
  minValue: 0,
  maxValue: 100,
  minStep: 1,
  unit: 'percentage',
  capability: 'windowcoverings_set',
  lastUpdated: 1732790471550
}

I’ve been able to isolate the issue to just when trying to use ā€œOpenā€ for a device, either via a card or the device controls. The shades will open correctly if I use the position function and set the value to 100%.

how do you operate the device when you get the error? Can you turn on debug in the device settings and recreate the issue and pm me the log?

I am trying to pair one of my FP2’s with Homey Pro. I follow the instructions, when I get to the screen I enter the PIN and it gives me an error ā€œOnpair No Service Found For Deviceā€ I can try diffrent pin code with the same results. Some one that has an ideer?

I receved help from Martin and get it to work. ā€œCan you restart the app and wait a few minutes and then retry the pairingā€¦ā€

I just get the message ā€œTimeout after 30000msā€ when trying to add my homebridge running on docker. I’ve restarted app etc without any luck. Any tips?

Don’t you need to do something special with networking and docker? Looks like it cannot reach the address…

Well obviously I had an update gone wrong but now fixed. Now I instead get ā€connection refused. Power cycle and try again…… ā€

I’ve been at it on and off for 2 weeks now, and today I was able to install the Aqara FP2 presence sensor in Homey Pro 2023. This is what worked for me (mainly got it to work from this topic: Can you connect aqara presence sensor FP2 to homey? - #22 by Greg_Warren). I found that if i tried to pair the device and it was unsuccessfull, it won’t allow a succesfull pairing later from that point on, hence below process:

  • remove the sensor from aqara app
  • restart the homekit app in hp23
  • Greg mentioned he had to turn off mobile internet.
  • reinstall the presence sensor to aqara app.
  • sensor shows up for pairing through the homekit app.
  • enter the correct pin on the back of the device. I mistook a 0 for an 8 :joy:
  • it should now pair with hp23.

Now, first pairing did fail for me, not because of the wrong pin. 2nd try was successfull.

Hi all

I’m trying hard to add my FP2 sensor to Homey but without any luck. The HomeKit Controller app just doesn’t see the sensor.

What I did (a couple of times):

  • remove and re-install the HomeKit Controller app (version 1.3.18)
  • remove the sensor from aqara app
  • Reset the sensor by holding down the button for 10 seconds, until the light starts flashing
  • restart the homekit app in hp23
  • on phone, turn off mobile internet.
  • reinstall the presence sensor to aqara app.
  • Remove it from apple home, since I use an iPhone - strange thing: I cannot find the sensor in my apple home app, but if I try to add it again it says it is already present and I can remove it.
  • power off the sensor
  • start adding a device for the homey HomeKit controller app.
  • power on the sensor, wait for the light to blink
  • Press ā€œinstallā€ on the app

The result: only the Tado bridge is found as device. I already have that device in homey so don’t want to add that again…

Any help is appreciated.

Kind regards,
Paul