Oh, i read the thread.
But i didn’t found a solution for this.
Excuse me.
Pimatic plugin as Apple Homekit bridge
Oh, i read the thread.
But i didn’t found a solution for this.
Excuse me.
@chris Sorry, i don’t know what the problem might be. I did a fresh install on my dev raspi and everything works fine. Maybe a reboot of your system helps? Could be that the mdns service has hickups.
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
@sweetpi I finally did some research regarding the daemon mode in pimatic. It seems that this has to do with the used node version. I did an update to node v0.12.6 and started pimatic in daemon mode. I left it running since yesterday and it was still up and working this morning.
The used dependency hap-nodejs is known to require node >= 0.12.x. It seems that this is true if pimatic runs in daemon mode.
Now my question is: Does pimatic work with node 0.12.x? I know that there is a discussion about compatibility to node v4 (https://github.com/pimatic/pimatic/issues/719), but i don’t know the status for 0.12.x.
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
Everyone who wants to give it a try:
$ wget http://node-arm.herokuapp.com/node_archive_armhf.deb
$ sudo dpkg -i node_archive_armhf.deb
$ node -v
This will install node 0.12.6. I did remove the old node installation before. Not sure if this is necessary, though.
After everything is installed you should be able to start pimatic in daemon mode.
CAUTION: Since i don’t use every plugin out there and therefor didn’t test them, this could break your installation!
But as far as I know, most of the “standard” plugins will run just fine.
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 said:
Since i don’t use every plugin out there and therefor didn’t test them, this could break your installation!
Exactly, several plugins have not been ported/adapted to node v0.12 and later. As far as I know the goal is to get this completed for the pimatic release 0.9.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
It seems that using a newer version of node doesn’t help. I tried the same on another raspberry pi, no luck.
Now I have to investigate further. Maybe one solution will be to write a new init script, that does the daemonization by itself. I find it strange anyway that pimatic creates a daemon of itself.
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’m still running this on node v0.10.x and normal pimatic daemon mode since last week without any problems.
But I’ve had to restart pimatic today and then I got a disconnect from pimatic-hap.
I investigated, that this happenend when I tried to use Siri directly after the pimatic restart.
The issue seems still to be the different persist folders (see my posts before):
In my working configuration, only the persist folder in the ROOT directory ( /persist) of the pi exists. I’ve had deleted all other persist folders, also this one appeared in /usr/local/pimatic-app
As soon as I tried to use Siri without FIRST open Eve and let them both synchronize, the pimatic-hap (or homekit?) creates an additional (redundant) persist folder in /home/pi … and nothing worked any more.
So I deleted the /home/pi/persist folder completly again (but let the /persist folder in ROOT untouched), restarted pimatic, then FIRST opened Eve (all devices got updated). After this procedure, pimatic-hap (or homekit?) doesn’t create this additional persist folder in /home/pi anymore - and it worked again.
Hope it helps for you…
@fennsen said:
Hope it helps for you…
I hope that, too . I’ll see if i can find the problem. Thanks for your investigation!
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
@fennsen How come that you have multiple persist folders anyway? If i follow the normal install procedure on http://pimatic.org/guide/getting-started/installation/ the only persist folder that gets created is in /home/pi/pimatic-app/.
There is something different to your installation…
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 have no idea this installation is 2 years old and has growing…
@fennsen Thats fine. I made a change that ensures that the directory is always at the root directory of pimatic. With the next release this directory will be called “hap-database”. Maybe this fixes the daemon mode, too. I did test this change on my production raspi, which never worked in daemon mode, but with this change it does since a few days.
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
@All Please try the newly released version 0.3.4 in daemon mode. Would be great if some people provide feedback if its working now. At least for me it seems to be working now.
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 sorry to report that but still not ok with the latest version and pimatic in a daemon mode…
pimatic rocks!
@Yves911 if you don’t mind, you could try to install a second pimatic instance completely from scratch. Of course when the original instance is not running. Then see if that works. To start pimatic in daemon mode just type
node node_modules/pimatic/pimatic.js start
Update: I just installed piratic-hap on another raspberry pi and it’s working again in daemon mode, so i have no clue at the moment what the problem could be.
Are the other Apple users also facing the same problems?
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
I am going to update this afternoon and let you know! I have updated the pimatic hap to the latest version and it works now in deamon mode!
@michbeck100 no luck with the new install !y iphone don’t want to communicate with pimatic-hap anymore (can’t see the device)
pimatic rocks!
I needed to remove the pimatic device in homekit. Then after adding it again, I could use it again with the eve application.
Cheers,
Frank
@ras37-pi said:
I needed to remove the pimatic device in homekit. The after adding it again, I could use it again with the eve application.
Cheers,
Frank
Thanks Frank, i removed/added it again and now it works.
@michbeck100, i didn’t restarted pimatic before doing what Frank suggested and it start working immediately (that could mean that the daemoned mode is working fine)
pimatic rocks!
@michbeck100 I ust wanted to let you now I tried all your suggestions and none of them worked, but since your last update the error message disappeared and it works like a charm. Thanks for your work!
@michbeck100 said:
@newschooler said:
error [pimatic]: A uncaught exception occured: Error: dns service error: unknown at Advertisement.on_service_registered
Are your running pimatic on OS X? There are several issues reporting this error in HAP-NodeJS:
https://github.com/KhaosT/HAP-NodeJS/issues/84
https://github.com/KhaosT/HAP-NodeJS/issues/47On of them also has kind of a fix included. Maybe that fixes your errors, too?
Or you could try https://github.com/agnat/node_mdns/issues/70
And other posts are saying updating raspbian helps. So try
sudo apt-get update sudo apt-get upgrade
Another fix could be https://github.com/agnat/node_mdns/issues/104#issuecomment-62977485
Please report back if anything of this helps.
“Cloud Data Sync in Progress” EVE app error
Solved by Resetting the network setting of the iPhone.
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!
Solved for the time being due a normal pimatic update (pimatic-homeduino) and it started working again!
https://github.com/michbeck100/pimatic-hap/issues/10