Pimatic plugin as Apple Homekit bridge

---

@p4co86 Thats normal and should be no problem according to other sources

Now that i left pimatic running for few minutes the connection to the home kit bridge is lost again, without any error message or warning. So it’s still not as stable as i would like it to be. but i think its a good start.

The way you have mentioned to start it works for me as well

@michbeck100 as mentioned earlier referring to issue 138 the systems start but after switching of the phone and turning on again everything is grayed. Here is the log.
“92.168.178.47] Muting event ‘6.9’ notification for this connection since it originated here. +12ms
EventedHTTPServer [192.168.178.47] HTTP Repsonse is finished +8ms
^[[A^[[B^[[B^[[B^[[B^[[B^[[B^[[B EventedHTTPServer [192.168.178.47] Client connection closed +37s
EventedHTTPServer [192.168.178.47] HTTP connection was closed +19ms
EventedHTTPServer [192.168.178.47] HTTP server was closed +4ms
EventedHTTPServer [192.168.178.47] New connection from client +1m
EventedHTTPServer [192.168.178.47] HTTP server listening on port 54826 +4ms
EventedHTTPServer [192.168.178.47] HTTP request: /pair-verify +30ms
HAPServer [fa:fe:db:e4:36:2c] HAP Request: POST /pair-verify +3ms
HAPServer [fa:fe:db:e4:36:2c] Pair verify step 1/2 +10ms
EventedHTTPServer [192.168.178.47] HTTP Repsonse is finished +65ms
EventedHTTPServer [192.168.178.47] HTTP request: /pair-verify +38ms
HAPServer [fa:fe:db:e4:36:2c] HAP Request: POST /pair-verify +4ms
HAPServer [fa:fe:db:e4:36:2c] Pair verify step 2/2 +6ms
HAPServer [fa:fe:db:e4:36:2c] Client xxxx verification complete +22ms
EventedHTTPServer [192.168.178.47] HTTP Repsonse is finished +10ms
EventedHTTPServer [192.168.178.47] HTTP request: /accessories +34ms
HAPServer [fa:fe:db:e4:36:2c] HAP Request: GET /accessories +3ms
EventedHTTPServer [192.168.178.47] HTTP Repsonse is finished +63ms”

After this stop the server does not respond any more even not after a reload of pimatic

@dynamite You probably have to delete the persist folder before restart. This removes the homekit “cache” from pimatic.

@dynamite Maybe thats the answer to the problem: https://github.com/KhaosT/HAP-NodeJS/issues/138#issuecomment-152822170

I’m seeing

[Pimatic HomeKit Bridge] Error getting value for Characteristic "On": undefined

when using the DEBUG variable. I’m currently trying to find out why its undefined.

@michbeck100 indeed to make it work I have removed the persistence folder… Then start in console mode and I could find it again.

@michbeck100 the issue as mentioned here is exactly the same behavior as we see now. So I think if you can fix this you are on the right track!

The error about getting undefined Characteristics should be gone with the next release .

BTW: Did anyone try the homekit identify feature with Switches, yet? Works best if the switch turns on a light .

Let me know what you think!

Hi had this message in my console run…

07:18:32.431 [pimatic] A uncaught exception occured: Error: Can’t set headers after they are sent.
07:18:32.431 [pimatic]> at ServerResponse.OutgoingMessage.setHeader (http.js:691:11)
07:18:32.431 [pimatic]> at ServerResponse.res.setHeader (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/express/node_modules/connect/lib/patch.js:63:22)
07:18:32.431 [pimatic]> at ServerResponse.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/express/node_modules/connect/lib/patch.js:80:14)
07:18:32.431 [pimatic]> at Array.forEach (native)
07:18:32.431 [pimatic]> at ServerResponse.res.writeHead (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/express/node_modules/connect/lib/patch.js:79:28)
07:18:32.431 [pimatic]> at HAPServer.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/HAPServer.js:672:16)
07:18:32.431 [pimatic]> at Bridge.Accessory._handleGetCharacteristics (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/Accessory.js:471:5)
07:18:32.431 [pimatic]> at HAPServer.EventEmitter.emit (events.js:106:17)
07:18:32.431 [pimatic]> at HAPServer._handleCharacteristics (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/HAPServer.js:659:10)
07:18:32.431 [pimatic]> at HAPServer.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/HAPServer.js:172:39)
07:18:32.431 [pimatic]> at IncomingMessage.EventEmitter.emit (events.js:92:17)
07:18:32.431 [pimatic]> at _stream_readable.js:920:16
07:18:32.431 [pimatic]> at process._tickCallback (node.js:415:13)
07:18:32.431 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
07:18:32.475 [pimatic] shutting pimatic down…
07:18:32.502 [pimatic] Flushing database to disk, please wait…
07:18:32.842 [pimatic] A uncaught exception occured: Error: Can’t set headers after they are sent.
07:18:32.842 [pimatic]> at ServerResponse.OutgoingMessage.setHeader (http.js:691:11)
07:18:32.842 [pimatic]> at ServerResponse.res.setHeader (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/express/node_modules/connect/lib/patch.js:63:22)
07:18:32.842 [pimatic]> at ServerResponse.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/express/node_modules/connect/lib/patch.js:80:14)
07:18:32.842 [pimatic]> at Array.forEach (native)
07:18:32.842 [pimatic]> at ServerResponse.res.writeHead (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/express/node_modules/connect/lib/patch.js:79:28)
07:18:32.842 [pimatic]> at HAPServer.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/HAPServer.js:672:16)
07:18:32.842 [pimatic]> at Bridge.Accessory._handleGetCharacteristics (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/Accessory.js:471:5)
07:18:32.842 [pimatic]> at HAPServer.EventEmitter.emit (events.js:106:17)
07:18:32.842 [pimatic]> at HAPServer._handleCharacteristics (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/HAPServer.js:659:10)
07:18:32.842 [pimatic]> at HAPServer.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/HAPServer.js:172:39)
07:18:32.842 [pimatic]> at IncomingMessage.EventEmitter.emit (events.js:92:17)
07:18:32.842 [pimatic]> at _stream_readable.js:920:16
07:18:32.842 [pimatic]> at process._tickCallback (node.js:415:13)
07:18:32.842 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
07:18:32.882 [pimatic] shutting pimatic down…
07:18:33.024 [pimatic] Flushing database to disk, please wait… Done.
07:18:33.040 [pimatic] exiting…
osmc@osmc:~/pimatic-app$

@michbeck100 The error as posted before looks like an one of. Have not seen it anymore. However EVE reconnects immediately when running pimatic in the console. If I start it daemonized eve is not able to reconnect. Tried this 3 times …

since i start pimatic not as daemon, i get this in my pimatic debug log:
and i have now a persisit folder inside my root folder

debug [pimatic-hap]: pincode is: 031-45-154
09:22:07debug [pimatic-hap]: publishing homekit bridge on port 51826
09:17:18debug [pimatic-hap]: unsupported device type iframeDevice
09:17:18debug [pimatic-hap]: trying to add device Kamera
09:17:18debug [pimatic-hap]: unsupported device type LocationDevice
09:17:18debug [pimatic-hap]: trying to add device Standort Stefan
09:17:17debug [pimatic-hap]: successfully added device Multiroom Switch
09:17:17debug [pimatic-hap]: trying to add device Multiroom Switch
09:17:17debug [pimatic-hap]: unsupported device type DummyPresenceSensor
09:17:17debug [pimatic-hap]: trying to add device Multiroom
09:17:17debug [pimatic-hap]: successfully added device Kodi Datenbank Switch
09:17:17debug [pimatic-hap]: trying to add device Kodi Datenbank Switch
09:17:17debug [pimatic-hap]: unsupported device type DummyPresenceSensor
09:17:17debug [pimatic-hap]: trying to add device Kodi Datenbank
09:17:17debug [pimatic-hap]: successfully added device Computer
09:17:16debug [pimatic-hap]: trying to add device Computer
09:17:16debug [pimatic-hap]: unsupported device type ShellSensor
09:17:16debug [pimatic-hap]: trying to add device Systemzeit
09:17:16debug [pimatic-hap]: unsupported device type VariablesDevice
09:17:16debug [pimatic-hap]: trying to add device Wecker
09:17:16debug [pimatic-hap]: unsupported device type VariablesDevice
09:17:16debug [pimatic-hap]: trying to add device Energie Einsparung
09:17:16debug [pimatic-hap]: successfully added device Kodi Media Center
09:17:16debug [pimatic-hap]: trying to add device Kodi Media Center
09:17:16debug [pimatic-hap]: unsupported device type KodiPlayer
09:17:16debug [pimatic-hap]: trying to add device Kodi Player
09:17:16debug [pimatic-hap]: unsupported device type KodiPlayer
09:17:16debug [pimatic-hap]: trying to add device Kodi Media Player
09:17:15debug [pimatic-hap]: unsupported device type SystemSensor
09:17:15debug [pimatic-hap]: trying to add device System Memory
09:17:15debug [pimatic-hap]: unsupported device type SystemSensor
09:17:15debug [pimatic-hap]: trying to add device System CPU
09:17:15debug [pimatic-hap]: unsupported device type ShellSensor
09:17:15debug [pimatic-hap]: trying to add device System uptime
09:17:15debug [pimatic-hap]: unsupported device type ShellSensor
09:17:15debug [pimatic-hap]: trying to add device Sonne
09:17:14debug [pimatic-hap]: successfully added device Media Center
09:17:14debug [pimatic-hap]: trying to add device Media Center
09:17:14debug [pimatic-hap]: successfully added device Nachttischlampe
09:17:14debug [pimatic-hap]: trying to add device Nachttischlampe
09:17:14debug [pimatic-hap]: successfully added device Kodi Wohnzimmer
09:17:14debug [pimatic-hap]: trying to add device Kodi Wohnzimmer
09:17:14debug [pimatic-hap]: successfully added device Stehlampe
09:17:14debug [pimatic-hap]: trying to add device Stehlampe
09:17:14debug [pimatic-hap]: successfully added device Radio
09:17:14debug [pimatic-hap]: trying to add device Radio
09:17:14debug [pimatic-hap]: successfully added device Weinregal
09:17:14debug [pimatic-hap]: trying to add device Weinregal
09:17:14debug [pimatic-hap]: unsupported device type HomeduinoRFPir
09:17:14debug [pimatic-hap]: trying to add device Balkonfenster
09:17:13debug [pimatic-hap]: unsupported device type HomeduinoRFTemperature
09:17:13debug [pimatic-hap]: trying to add device Küche
09:17:13debug [pimatic-hap]: unsupported device type HomeduinoRFTemperature
09:17:13debug [pimatic-hap]: trying to add device Schlaftemperatur
09:17:13debug [pimatic-hap]: unsupported device type HomeduinoRFTemperature
09:17:13debug [pimatic-hap]: trying to add device Wohntemperatur
09:17:13debug [pimatic-hap]: successfully added device NAS Server
09:17:13debug [pimatic-hap]: trying to add device NAS Server
09:17:13debug [pimatic-hap]: unsupported device type VariablesDevice
09:17:13debug [pimatic-hap]: trying to add device Heizung Laufzeit
09:17:12debug [pimatic-hap]: unsupported device type Timer
09:17:12debug [pimatic-hap]: trying to add device Heizung Timer
09:17:12debug [pimatic-hap]: unsupported device type PingPresence
09:17:12debug [pimatic-hap]: trying to add device Media Center Wohnzimmer
09:17:12debug [pimatic-hap]: unsupported device type DummyHeatingThermostat
09:17:12debug [pimatic-hap]: trying to add device Thermostat
09:17:12debug [pimatic-hap]: successfully added device comming home
09:17:12debug [pimatic-hap]: trying to add device comming home
09:17:12debug [pimatic-hap]: unsupported device type ButtonsDevice
09:17:12debug [pimatic-hap]: trying to add device Raspberry Reboot
09:17:11debug [pimatic-hap]: unsupported device type ButtonsDevice
09:17:11debug [pimatic-hap]: trying to add device Restart Service
09:17:11debug [pimatic-hap]: unsupported device type OpenWeatherForecastDevice
09:17:11debug [pimatic-hap]: trying to add device Morgen
09:17:11debug [pimatic-hap]: unsupported device type OpenWeatherDevice
09:17:11debug [pimatic-hap]: trying to add device Heute
09:17:11debug [pimatic-hap]: unsupported device type DummyPresenceSensor
09:17:11debug [pimatic-hap]: trying to add device Nachtabsenkung
09:17:11debug [pimatic-hap]: unsupported device type VariablesDevice
09:17:11debug [pimatic-hap]: trying to add device Aktuelles Ambiente
09:17:11debug [pimatic-hap]: successfully added device Heizung
09:17:10debug [pimatic-hap]: trying to add device Heizung
09:17:10debug [pimatic-hap]: successfully added device Heizung Freigabe
09:17:10debug [pimatic-hap]: trying to add device Heizung Freigabe
09:17:10debug [pimatic-hap]: unsupported device type ButtonsDevice
09:17:10debug [pimatic-hap]: trying to add device Ambiente
09:17:10debug [pimatic-hap]: unsupported device type VariablesDevice
09:17:10debug [pimatic-hap]: trying to add device Wohntemperatur Trend
09:17:10debug [pimatic-hap]: unsupported device type PingPresence
09:17:10debug [pimatic-hap]: trying to add device Cris Handy
09:17:10debug [pimatic-hap]: unsupported device type PingPresence
09:17:10debug [pimatic-hap]: trying to add device Stefan Handy
09:17:10debug [pimatic-hap]: unsupported device type PingPresence
09:17:10debug [pimatic-hap]: trying to add device Mein NAS
09:17:10debug [pimatic-hap]: unsupported device type PingPresence
09:17:10debug [pimatic-hap]: trying to add device Media Center
09:17:10debug [pimatic-hap]: unsupported device type PingPresence
09:17:10debug [pimatic-hap]: trying to add device Router
09:17:09debug [pimatic-hap]: unsupported device type PingPresence
09:17:09debug [pimatic-hap]: trying to add device Mein Computer

@p4co86 These are the debug messages for pimatic-hap. They will be removed once everything is stable, but for now you can see which devices pimatic-hap is trying to add to the homekit bridge and after that it reports if that was sucessful.

In your example you can see that e.g. DummyPresenceSensors are not supported yet.

BTW: Even if this plugin will be feature complete one day doesn’t mean that all types of devices that pimatic knows will be supported. This is because homekit doesn’t support these.

ok, but i still cannot connect to it. when i delete the persist folder i can also not connect.
then i have to start pimatic again and after that i have a new persist folder, but cant still connect to the bridge.

@p4co86 all devices that are not supported won’t show up in any homekit app, because they are not advertised. As is said these are just debug messages, not error messages. If you want to disable debug messages at all you must change the config.json of pimatic.
The persist folder is created by pimatic-hap on every start, if it not exists. This contains some sort of a Database that is used to identify the connected iOS devices.

I’ve released v0.1.0 a few minutes ago. This release works pretty stable now. It was running the whole last night and i could connect this morning without any problem.

Problem was that pimatic-hap didn’t report the state of the devices. So homekit didn’t know if a switch is on or off. Apparently it didn’t like that and stopped working .

Note: You still have to start pimatic manually, not as a daemon. Haven’t figured out yet what the problems is with that.

i believe this topic is one of the hottest topics since month full steam ahead!

@dk00000 said:

this topic is one of the hottest topics since month

absolutely! even though I do not have an ios device I like the idea and appreciate all of your commitments

we’re having a very nice pimatic community here! big thx to all of our users and contributors! keep it up!

Great for my its working for one day now with pimatic as a daemon.

no errors everything is fine