@l0mp1 Fixed. As far as i can tell this issue was just with switches. https://github.com/michbeck100/pimatic-hap/issues/14 fixes it. I will publish a new release once i tested everything a little bit more.
The next release will also bring support for humidity sensors built into temperature sensors
-
Pimatic plugin as Apple Homekit bridge
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 Sounds great, thanks!!
-
@l0mp1 I’ve just released version 0.5.0 with support for humidity sensors. This version also fixes the issue you found. Thanks for this by the way
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 -
Out of the blue hap stopped working for me.
I set it up three days ago by deleting hap-database and resetting all HomeKit settings. It worked for like one day and i set all rooms up but after i slept one night Siri stopped working and Eve displays “Nicht Erreichbar Aktualisiert: vor 2 Tagen” above every device.Stopping Pimatic and starting it with hap-debug mode i get an error:
Any ideas on how to fix it or get more info on what’s wrong?
-
@thymian unfortunately this is something that I couldn’t fix yet because I have no clue where to start. My guess would be that the mdns service that is used to advertise the devices in the network just stops working.
Maybe there are newer versions of the dependencies available.
Apart from that your debug output seems fine. Maybe you have to reset everything again. Sorry for that.
Note that I’ve been using pimatic in daemon mode pretty successfully in the last weeks. Not sure what I changed to fix this, but it runs stable for me. So please try to start pimatic the usual way with
sudo service pimatic startpimatic-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 was having the same brake down yesterday as well. Out of the blue it stopped working. Removing the database, restart and reset the iPhone and it worked again.
The warning message is just a warning not an error as mentioned here:
cups, and other packages, are designed to be cross platform using the mDNSResolver library which is released as free software by Apple.
Avahi, which is not cross platform but is better integrated with Gnome, has built a crude compatibility layer to allow mDNSResolver apps to work with it, but it’s developers have decided to pressure applications using Apple’s API by printing a warning to their user’s logs.
The proper fix is to remove the offending code from Avahi’s warn.c in Ubuntu.
-
Hey guys,
I am running Pimatic (latest) with pilight 5.0, six “elro_hc” and one 1-wire temperature sensor.
The installation of pimatic-hap didn’t work at first but “sudo apt-get update” fixed it and now it’s running really great. The setup of Elgato Eve did also work an I can use Siri on my iPhone to switch the lights on and off. Wonderful work, many thanks to you!
There is only one thing that’s a bit strange: I have 6 devices, Eve reports 8 devices. One device called “Lampe” is registered twice (one is not reachable) and one device is called “LED” which seems to be a clone of an existing device called “LED-Beleuchtung”.
Switching “Lampe” on with Siri works but it also reports an error (I think it tries to switch both at the same time), switching “LED-Beleuchtung” also works.
Does anyone know how to get those 2 “ghost” devices out of my list?
Thanks,
Dominik -
@ras37-pi Just as a note: AppleTV 4 works fine, even via GPRS.
Cheers,
Frank -
@dmnkhhn pimatic-hap will just use the information from the device section of config.json. I’m not sure how the pilight plugin works, but maybe there’s the problem.
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 -
That could be one of the reasons, the pilight plugin hasn’t been updated in a while but at least it works. I was able to hide those two devices in the Eve app and that’s good enough for me.
I have second Pi running pilight v7.0, I haven’t tried installing Pimatic yet but I might give it a try.
-
@dmnkhhn you should consider switching to pimatic completely. I did this myself and find the UI and the community better than with pilight. And all of my devices are supported. If you are missing some devices that just ask
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 -
the Hap-database in the main pimatic directory
-
I’ve had two different Pi both with pilight and Pimatic discovered the second Pi first (via SSDP) and tried to load my test devices. After manually sorting out old and defective devices, pimatic-hap and the Elgato Eve app are running nicely.
Can I control my devices when I’m not connected to my local network? Pimatic itself is externally accessible.
-
@dmnkhhn no you can’t without an ATV as far as I know.
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 -
@l0mp1 @thymian @dynamite I was wondering why the homekit bridge out of the sudden stops to work. Like i said, i find the mdns dependency suspicious but i can’t proof anything.
pimatic-hap is using hap-nodejs which has a the dependency to mdns in version ^2.2.7, which means that this version isn’t fixed.
If the plugin stops working again please try to find out which version of mdns you are using. the latest is 2.2.11. This the version that i’m using since the last update and its running pretty stable 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 said:
@dmnkhhn no you can’t without an ATV as far as I know.
Well yeah, a compatible ATV is required. I totally forgot about mine and once both of them were using the same Apple ID it works like a charm.
I was having some problems lately, too. Some devices were not accessible for no reason and after a short while they were working again as if nothing happend. I couldn’t set a pattern but I’ll report if it happens again.
-
@michbeck100 Sorry read your comment a bit late. Could you tell me how to check the version. Now I recollect the plugin looked like it ran more stable on osmc than on the Raspbian I am running it on now…At this moment I loose the connection quite fast.
-
@dynamite
for mdns version:
bet it isn’t the fastes solution but try:cd /pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/mdns nano package.json
@michbeck100 I currently got 2.2.11 and i didnt change anything since the breakdown of pimatic-hap so it crashed with 2.2.11, too. Bad news i think.
Any ideas on how to investigate further? Guess i will set up everything again now.EDIT:
strange things happening. As i reset HomeKit pref., deleted hap-database folder and removed & reinstalled the plugin i got following message after typing in the code for the pimaitc bridge:
Click to show image.I have then reset HomeKit pref. again, deleted hap-database again and then restarted pimatic and now everything is working fine again.
EDIT 2:
Now i experience even more strange things: Devices seem to vanish. As i set up the Bridge into my home i went through all devices and set them to the correct rooms. I then opened the room-page and the only displayed devices were the two from the plugin “pimatic-led-lights”.
Every other simple switch or presence sensor vanished from the whole app and i cant even see nor configure them in the device section anymore
I installed Insteon+ to see if it’s an Eve bug, but even there i cant find all the other switches. -
I have also got the version 2.2.11 install.
Might there also be a difference when installing the files? In console or deamonized?