Pimatic plugin as Apple Homekit bridge

---

Hi,

thanks a lot for this plugin. I am using pimatic with the home kit plugin together with z-way and homeduino to control power sockets from Intertechno, ZWave on a Raspberry Pi. What log have you got the error messages from? I was trying to find if I have the same. I occasionally have the following error in the log (from pimatic gui):

error [pimatic]: A uncaught exception occured: Error: listen EADDRINUSE at errnoException (net.js:901:11) at Server._listen2 (net.js:1039:14) at listen (net.js:1061:10) at Server.listen (net.js:1127:5) at new EventedHTTPServerConnection (/home/pi/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/util/eventedhttp.js:125:20) at EventedHTTPServer._onConnection (/home/pi/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/util/eventedhttp.js:79:20) at Server.EventEmitter.emit (events.js:95:17) at TCP.onconnection (net.js:1180:8) This is most probably a bug in pimatic or in a module, please report it!

Cheers,
Frank

@michbeck100 Hi, Ok thanks for the remark. I will do a clean install this evening and see again!

@ras37-pi The messages come from pimatic-daemon.log in the pimatic root directory.

@michbeck100 Just to inform you: After having some trobles before, I’m using version 0.2.2. (self installed via plugin statement) and a fresh pimatic update to the actual release since 4 days in my pre-production. And up right now - all errors disappeared.
before this EVE has had always disconnects after shutting down the mobile.
And very interesting: before there has been produced different /persistent folders on my pi (see my post before). With the new version, only /persist on root exists. Maybe this was also a reason for the errors.

So I moved today to production… Keeping my fingers crossed. Nevethelesse: Siri has some strange behaviours: ‘Esszimmer’ and ‘Kaminzimmer’ are well recognized. Wohnzimmer: she doesn’t like and is always searching for a contact with the surname ‘Zimmer’ )) funny…

@ras37-pi I’ve had the same errors. they disappeared with afresh install of the actual pimatic and pimatic-hap version (seee my post below)

@fennsen I found it hard to find the right names for accessories, too. What helps is defining the according rooms and assigning the accessories to them. Then you can say “Schalte das Wohnzimmer aus” (Switch off Wohnzimmer).

I just released version 0.3.0 which should includes some bugfixes and also an update to the most recent version of hap-nodejs.
My tests were successful, please let me know about yours!

Run in daeomon mode or? Is it more stable now?

@michbeck100 Thanks! Of course I did this… because I’m always switching groups in a clustered room. Mostly I’m using a Variable (1/0) to trigger groups of switches. let’s say ‘Lights Standard’. PIMATIC then switches based on a changed attribute rule. Therefore I can say ,Siri, switch Lights Standard off" without using the scenes in EVE. Theese ‘scenes’ are therefore programmed in PIMATIC rules and therefore also always actual in PIMATIC (if you do this with EVE… PIMATIC doesn’t become aware of the state change of the group-trigger Variables)

But “Schalte das Wohnzimmer ein” (switch Living Room on) mostly works… "“Schalte das Wohnzimmer aus” (switch Living Room off) mostly NOT )

@sweebee I’m running this totally normal in daemon mode. the hub—trick didn’t worked with me

@sweebee Still in non-daemon mode, it couldn’t find the problem yet.
@fennsen which version of node are you using? v0.10 or v0.12?

@michbeck100 v0.10

@michbeck100 ok, I tried the 0.3.0 update and I have now clew whats going wrong: but when starting EVE the switch (power) devices didn’t get updated any more automaticly (with the actual state or when initiated change on pimatic side). Only temperature sensors are updated with actual values.
I’ve made a roll-back to last pimatic-hap release which worked for me until today)

@fennsen back to work after roll-back to last release: everything works flawless. from my pimatic debug log entrys I can only see that under 0.3.0. there have been distribution messages without device names.
Under the last release it works as expected:

debug [pimatic-hap]: returning current temperature: 22
23:26:45debug [pimatic-hap]: returning current temperature: 23.2
23:26:45debug [pimatic-hap]: returning current temperature: 23.1
23:23:33debug [pimatic-hap]: pincode is: 031-45-154
23:23:33debug [pimatic-hap]: publishing homekit bridge on port 51826
23:21:29debug [pimatic-hap]: successfully added device OSPi Cam switch
23:21:29debug [pimatic-hap]: trying to add device OSPi Cam switch
23:21:29debug [pimatic-hap]: successfully added device Kamera Aussen Eingang
23:21:29debug [pimatic-hap]: trying to add device Kamera Aussen Eingang
23:21:29debug [pimatic-hap]: successfully added device Kamera Aussen Parkplatz
23:21:29debug [pimatic-hap]: trying to add device Kamera Aussen Parkplatz
23:21:29debug [pimatic-hap]: successfully added device Temperatur Garten
23:21:29debug [pimatic-hap]: trying to add device Temperatur Garten

@fennsen Thanks for your tests. It seems I’ve added some bugs to the last release
I fixed one of them already, which is probably causing the problems you are describing. Furthermore i fixed some possible endless loops, that can occur if devices don’t check if their state changes from 1 to 1 (or in other words: the state doesn’t change). I think this has been discussed before where switches where going on and off all the time.

@michbeck100 You’re welcome. And I really appreciate your efforts to develope this great plugin and approach which extends the usage of pimatic (and 1. the WAF & 2. the stunning eyes of our home-guests by using Siri to play with szenes…) in an extraordinary way keep on please! The good thing is: my dog didn’t checked out yet that there’s now a way to execute a rule by Siri: ‘IFdog bells twice THEN fill up the food feeding dish to upper level’

@fennsen Thanks for the kudos

BTW: I’ve released a bugfix release (v.0.3.1) Hope this fixes your errors. I also updated the dependency to hap-nodejs. So it might be worth to test if the plugin works whenb pimatic is started in daemon-mode (aka the default mode).

Please report everyone if there any errors. Would be good if the issue tracker on gihub gets used

@michbeck100 I am now installing a fresh install and will try the deamonized mode…let us see!
Unfortunately deamonized still no find after starting with the script it is found again!

Hello,
i’m running hap demonized.
I got the following error:

• error [pimatic]: A uncaught exception occured: Error: dns service error: unknown at Advertisement.on_service_registered (/home/pi/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/mdns/lib/advertisement.js:42:24) at SocketWatcher.MDNSService.self.watcher.callback (/home/pi/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/mdns/lib/mdns_service.js:18:40) This is most probably a bug in pimatic or in a module, please report it!

I had just made a new home in the homekit-app (delete persist-folder, delete old home, restart pimatic, made new home)
I could use the new home for 2 minutes, then the massage came and nothing is working until now.
i just restart pimatic 7 times, with the script it won’t start.
Just gone to the point
root@raspberrypi:/home/pi/pimatic-app# bash pimatic.sh
root@raspberrypi:/home/pi/pimatic-app# nohup: redirecting stderr to stdout

I have also done the steps
sudo killall node
ps -ax | grep pimatic
sudo kill -9 'pid'

Mit freundlichen Grüßen
Chris

@chris We’ve had this error before. Please read this complete thread carefully. Actually this wasn’t an issue anymore.
And make sure you are using the most recent versions of pimatic and pimatic-hap