@dynamite I am using a small shell script:
#!/bin/sh
nohup sudo DEBUG=HAPServer,EventedHTTPServer,Accessory node node_modules/pimatic/pimatic.js > pimatic-daemon.log &
Pimatic plugin as Apple Homekit bridge
@dynamite I am using a small shell script:
#!/bin/sh
nohup sudo DEBUG=HAPServer,EventedHTTPServer,Accessory node node_modules/pimatic/pimatic.js > pimatic-daemon.log &
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
@michbeck100 yes pimatic is daemonized. Later last evening it worked again, but this morning eve/siri couldn’t find the devices anymore.
@sweebee see my post about the shell script. for now this is currently the only way to get this to work reliable.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
it stops here?
root@raspberrypi:/home/pi/pimatic-app# bash pimatic.sh
root@raspberrypi:/home/pi/pimatic-app# nohup: redirecting stderr to stdout
@sweebee that’s correct. After that you will see that mode is running in the background and your pimatic instance should be up and running
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
when i try to connect i get the following.
Tue, 10 Nov 2015 20:51:12 GMT Accessory [Pimatic HomeKit Bridge] Creating new AccessoryInfo for our HAP server
Tue, 10 Nov 2015 20:51:12 GMT Accessory [Pimatic HomeKit Bridge] Creating new IdentifierCache
Tue, 10 Nov 2015 20:51:13 GMT EventedHTTPServer Server listening on port 51826
[90m21:51:16.409[39m[32m [pimatic-mobile-frontend][39m[90m [39mpacking static assets
[90m21:51:19.387[39m[32m [pimatic-mobile-frontend][39m[90m [39mpacking static assets finished
[90m21:51:19.401[39m[32m [pimatic-mobile-frontend][39m[90m [39mrendering html
[90m21:51:21.613[39m[32m [pimatic-homeduino][39m[90m [39mConnected to homeduino device.
[90m21:51:26.703[39m[32m [pimatic-mobile-frontend][39m[90m [39mrendering html finished
[90m21:51:26.739[39m[32m [pimatic][39m[90m [39mListening for HTTPS-request on port 443...
[90m21:51:26.742[39m[32m [pimatic][39m[90m [39mListening for HTTP-request on port 80...
Tue, 10 Nov 2015 20:59:39 GMT EventedHTTPServer [192.168.0.4] New connection from client
Tue, 10 Nov 2015 20:59:39 GMT EventedHTTPServer [192.168.0.4] HTTP server listening on port 54826
Tue, 10 Nov 2015 20:59:39 GMT EventedHTTPServer [192.168.0.4] HTTP request: /pair-setup
Tue, 10 Nov 2015 20:59:39 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: POST /pair-setup
Tue, 10 Nov 2015 20:59:39 GMT HAPServer [fa:fe:db:e4:36:2c] Pair step 1/5
Tue, 10 Nov 2015 20:59:39 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 20:59:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /pair-setup
Tue, 10 Nov 2015 20:59:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: POST /pair-setup
Tue, 10 Nov 2015 20:59:45 GMT HAPServer [fa:fe:db:e4:36:2c] Pair step 2/5
Tue, 10 Nov 2015 20:59:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 20:59:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /pair-setup
Tue, 10 Nov 2015 20:59:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: POST /pair-setup
Tue, 10 Nov 2015 20:59:45 GMT HAPServer [fa:fe:db:e4:36:2c] Pair step 3/5
Tue, 10 Nov 2015 20:59:45 GMT HAPServer [fa:fe:db:e4:36:2c] Pair step 4/5
Tue, 10 Nov 2015 20:59:45 GMT HAPServer [fa:fe:db:e4:36:2c] Pair step 5/5
Tue, 10 Nov 2015 20:59:45 GMT Accessory [Pimatic HomeKit Bridge] Paired with client 701C1673-3198-496B-BEB6-8F11C76C5035
Tue, 10 Nov 2015 20:59:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 20:59:45 GMT EventedHTTPServer [192.168.0.4] Client connection closed
Tue, 10 Nov 2015 20:59:45 GMT EventedHTTPServer [192.168.0.4] HTTP connection was closed
Tue, 10 Nov 2015 20:59:45 GMT EventedHTTPServer [192.168.0.4] HTTP server was closed
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] New connection from client
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP server listening on port 54826
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] New connection from client
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP server listening on port 54827
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] Client connection closed
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP request: /pair-verify
Tue, 10 Nov 2015 21:00:44 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: POST /pair-verify
Tue, 10 Nov 2015 21:00:44 GMT HAPServer [fa:fe:db:e4:36:2c] Pair verify step 1/2
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP connection was closed
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP server was closed
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP request: /pair-verify
Tue, 10 Nov 2015 21:00:44 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: POST /pair-verify
Tue, 10 Nov 2015 21:00:44 GMT HAPServer [fa:fe:db:e4:36:2c] Pair verify step 2/2
Tue, 10 Nov 2015 21:00:44 GMT HAPServer [fa:fe:db:e4:36:2c] Client 701C1673-3198-496B-BEB6-8F11C76C5035 verification complete
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP request: /accessories
Tue, 10 Nov 2015 21:00:44 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: GET /accessories
Tue, 10 Nov 2015 21:00:44 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":3,"iid":9,"ev":true},{"aid":3,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":6,"iid":9,"ev":true},{"aid":6,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":9,"iid":9,"ev":true},{"aid":9,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":12,"iid":9,"ev":true},{"aid":12,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":15,"iid":9,"ev":true},{"aid":15,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":18,"iid":9,"ev":true},{"aid":18,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":21,"iid":9,"ev":true},{"aid":21,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":24,"iid":9,"ev":true},{"aid":24,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":27,"iid":9,"ev":true},{"aid":27,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP request: /characteristics
Tue, 10 Nov 2015 21:00:45 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {"characteristics":[{"aid":28,"iid":9,"ev":true},{"aid":28,"iid":10,"ev":true}]}
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Current State" for events
Tue, 10 Nov 2015 21:00:45 GMT Accessory [Pimatic HomeKit Bridge] Registering Characteristic "Lock Target State" for events
Tue, 10 Nov 2015 21:00:45 GMT EventedHTTPServer [192.168.0.4] HTTP Repsonse is finished
Tue, 10 Nov 2015 21:01:12 GMT EventedHTTPServer [192.168.0.4] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
after type in the key i can not connect
i cannot see any device on my iphone.
Thanks, works fine now. Will there be support for buttons?
And how do I restart / stop pimatic now?
Pimatic.js stop doesn’t work.
@p4co86 Form my point of view this log output is normal and expected. The pairing seems to be successful, too. HAPServer [fa:fe:db:e4:36:2c] Pair step x/5 is showing this. As i don’t see any errors i can’t really help.
Try to delete the persist folder and reset the homekit config on your ios device. This helps most the time if nothing else helps.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
sudo killall node
This will stop all processes that are started with nodejs. Be aware that this kills also all other nodejs processes that are running on your pi. I don’t have anything else so for its fine.
ps -ax | grep pimatic
should show the process including process id (pid). Use the pid with
sudo kill -9 'pid'
This will just stop a single process. After that you can start pimatic again using the shell script.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
@michbeck100 Doesn’t this ‘kill’ the process hardly without shutting down the service controlled and syncing the database before?? means: is data flushed correctly to sqllite database?
@michbeck100 Thanks. Just got home, but hap doesn’t work anymore. So doesn’t matter if not daemonized? Devices are unreachable.
@fennsen pimatic catches the kill event before and flushing to database is still done. Just look at the log file while killing and you’ll see.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
@sweebee for me it was really stable when not started in daemon mode. Did you see any exceptions in the log file? Note that the log file gets overridden when restarted using the shell script.
Apart from that, this plugin is like one week old, so please don’t expect it to be rock solid and stable.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
last messages today:
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] New connection from client
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] HTTP server listening on port 54826
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] HTTP request: /pair-verify
Wed, 11 Nov 2015 17:29:01 GMT HAPServer [ad:42:c8:99:59:b2] HAP Request: POST /pair-verify
Wed, 11 Nov 2015 17:29:01 GMT HAPServer [ad:42:c8:99:59:b2] Pair verify step 1/2
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] HTTP Repsonse is finished
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] HTTP request: /pair-verify
Wed, 11 Nov 2015 17:29:01 GMT HAPServer [ad:42:c8:99:59:b2] HAP Request: POST /pair-verify
Wed, 11 Nov 2015 17:29:01 GMT HAPServer [ad:42:c8:99:59:b2] Pair verify step 2/2
Wed, 11 Nov 2015 17:29:01 GMT HAPServer [ad:42:c8:99:59:b2] Client AB16CF01-18CA-4E1C-857A-686746F1C6D6 verification complete
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] HTTP Repsonse is finished
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] HTTP request: /accessories
Wed, 11 Nov 2015 17:29:01 GMT HAPServer [ad:42:c8:99:59:b2] HAP Request: GET /accessories
Wed, 11 Nov 2015 17:29:01 GMT EventedHTTPServer [192.168.1.11] HTTP Repsonse is finished
and sometimes
Wed, 11 Nov 2015 23:27:09 GMT EventedHTTPServer [192.168.1.11] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Don’t know what this is?
@sweebee These are all normal messages from the underlying HomeKit protocol implementation (HAP-NodeJS).
The documentation of HAP-NodeJS says about the keepalive:
// so iOS is very reluctant to actually disconnect HAP connections (as in, sending a FIN packet).
// For instance, if you turn off wifi on your phone, it will not close the connection, instead
// it will leave it open and hope that it’s still valid when it returns to the network. And Node,
// by itself, does not ever “discover” that the connection has been closed behind it, until a
// potentially very long system-level socket timeout (like, days). To work around this, we have
// invented a manual “keepalive” mechanism where we send “empty” events perodicially, such that
// when Node attempts to write to the socket, it discovers that it’s been disconnected after
// an additional one-minute timeout (this timeout appears to be hardcoded).
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
@michbeck100 I don’t know if it is related to this plugin. I am now running the latest version and some strange behaviour occurs. If I am switching a lamp, it keeps going on and off. Same for dimming it keeps fluctuating between Original value and new value. I can upload the log file… Does it has anything to do with a resonance between the update of both the “controls” so that pimatic gets contradictionairy signals from IPhone and pimatic user interface? The only way to stop is restart pimatic. It happens both deamonized as "scripted"
Here is a part of the log file:
Fri, 13 Nov 2015 19:35:14 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:48}]}
Fri, 13 Nov 2015 19:35:15 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:16 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:0}]}
Fri, 13 Nov 2015 19:35:16 GMT EventedHTTPServer [192.168.178.47] HTTP request: /characteristics
Fri, 13 Nov 2015 19:35:16 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Fri, 13 Nov 2015 19:35:16 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {“characteristics”:[{“aid”:2,“iid”:9,“value”:0}]}
Fri, 13 Nov 2015 19:35:16 GMT Accessory [Pimatic HomeKit Bridge] Setting Characteristic “On” to value 0
Fri, 13 Nov 2015 19:35:16 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:53}]}
Fri, 13 Nov 2015 19:35:17 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:18 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:49}]}
Fri, 13 Nov 2015 19:35:18 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:19 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:53}]}
Fri, 13 Nov 2015 19:35:20 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:0}]}
Fri, 13 Nov 2015 19:35:21 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:21 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:48}]}
Fri, 13 Nov 2015 19:35:22 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:23 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:0}]}
Fri, 13 Nov 2015 19:35:23 GMT EventedHTTPServer [192.168.178.47] HTTP Repsonse is finished
Fri, 13 Nov 2015 19:35:23 GMT EventedHTTPServer [192.168.178.47] Writing pending HTTP event data
Fri, 13 Nov 2015 19:35:23 GMT EventedHTTPServer [192.168.178.47] Muting event ‘2.9’ notification for this connection since it originated here.
Fri, 13 Nov 2015 19:35:24 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:53}]}
Fri, 13 Nov 2015 19:35:25 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:26 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:49}]}
Fri, 13 Nov 2015 19:35:26 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:27 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:53}]}
Fri, 13 Nov 2015 19:35:28 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:0}]}
Fri, 13 Nov 2015 19:35:28 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:29 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:48}]}
Fri, 13 Nov 2015 19:35:29 GMT EventedHTTPServer [192.168.178.47] HTTP request: /characteristics
Fri, 13 Nov 2015 19:35:29 GMT HAPServer [fa:fe:db:e4:36:2c] HAP Request: PUT /characteristics
Fri, 13 Nov 2015 19:35:29 GMT Accessory [Pimatic HomeKit Bridge] Processing characteristic set: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:29 GMT Accessory [Pimatic HomeKit Bridge] Setting Characteristic “Brightness” to value 47
Fri, 13 Nov 2015 19:35:30 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:47}]}
Fri, 13 Nov 2015 19:35:30 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:0}]}
Fri, 13 Nov 2015 19:35:31 GMT EventedHTTPServer [192.168.178.47] Sending HTTP event ‘2.10’ with data: {“characteristics”:[{“aid”:2,“iid”:10,“value”:53}]}
@dynamite my guess would be that there’s an endless loop between between HomeKit and my plugin. One advantage of this plugin is that it keeps HomeKit informed of the state of a device changes. Currently when HomeKit changes the state itself, it will still be notified of this, too, which is not necessary and might lead to this behavior. I’ll try to reproduce this error.
Btw: which version are you using? The latest release or the latest git version? Because nobody else reported of these problems. Could be that nobody is using the plugin yet, but I hope that’s not the case
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten
@michbeck100 As far as I recollect I am using the lastest git version 0.2.2. But I will verify this evening. I had the same idea about the cause as mentioned in your last reply. Maybe the processor load is also an influence as it does not happen all the time. It could be that if pimatic response is to slow it could happen. That is something I can test tonight by trying with a heavy CPU load.
@dynamite There’s a difference between the release version 0.2.2 and the HEAD version on github. Especially in handling state changes. If you just installed pimatic-hap using the default install method by adding it to config.json, then you are using version 0.2.2.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten