@tehmilcho said in [pimatic-echo] Release 0.5.0:
@michbeck100 For me the 0.5.1 Update broke everything. i have open a Post on Github.
Same for me. 0.5.0 fixed my last issues and 0.5.1 breaks anything again.
[pimatic-echo] Release 0.5.0
@tehmilcho said in [pimatic-echo] Release 0.5.0:
@michbeck100 For me the 0.5.1 Update broke everything. i have open a Post on Github.
Same for me. 0.5.0 fixed my last issues and 0.5.1 breaks anything again.
pimatic-google-calendar | pimatic-wmi | pimatic-snmp | pimatic-wakeonlan |
Like my work? Then consider a donation
Follow me: www.thorstenreichelt.de
@thost96 sorry for that. See https://github.com/michbeck100/pimatic-echo/issues/44 for a workaround until i fix this.
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 if you want and if you say me how i can install a update without the automatic of pimatic… i can be your Acceptance Test User… than can we find such errors before the big bang.
@tehmilcho I think i will start publishing beta releases every time.
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 didn’t have any errors when restarting after installing 0.5.1
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 found the error, bug is fixed and 0.5.2 was released. If you want to keep your devices without scanning again please use the existing echoUsers file from / and copy it to …/pimatic-app/echo-database/. Otherwise you need to rescan
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 If you can’t find the file you can find the “username” if you turn on debug mode and try to switch a device. pimatic-echo will then output this log message:
21:04:08.908 [pimatic-echo] debug: Pairing is disabled and user bSwiKWm0BIabajVpqb8GW7Fxc4Tl8IRHJg1Awxdm was not found
In this case the username is bSwiKWm0BIabajVpqb8GW7Fxc4Tl8IRHJg1Awxdm. Then you just need to
pi@raspbian ~/pimatic-app/echo-database $ echo bSwiKWm0BIabajVpqb8GW7Fxc4Tl8IRHJg1Awxdm > echoUsers
then restart pimatic and your devices work again. Just tried this on my own system.
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
Is there a way to do it in the other direction? Can i control to the Echo Plus Bridge connected Lamps with pimatic?
@manuelw no not that I know of
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
@manuelw has you tried if the Phillips Hue Plugin can connect to the Echo Plus? Because there must be same kind Software on the Echo Plus as on the Phillips Hue Bridge to handle the devices. The Echo Plus is in the theory a Phillips Hue bridge with a Amazon echo as one Device.
I searched a little bit but i only found guys that have the same question …i think there is at the moment no API for the ZigBee hub or Amazon is hiding this information.
See example here
https://forums.developer.amazon.com/questions/95222/api-to-access-the-integrated-hub-in-the-echo-plus.html
@tehmilcho said in [pimatic-echo] Release 0.5.0:
The Echo Plus is in the theory a Phillips Hue bridge with a Amazon echo as one Device
The Philips hue bridge can be controlled by pimatic because Philips implemented a REST api to control all the hue devices. This is what pimatic-echo tries to copy and why Alexa thinks these devices are Philips hue lights. But i don’t think that Amazon implemented this, too. Why should they. Everyone who wants to control their hue lights can buy a Philips hue 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
@manuelw said in [pimatic-echo] Release 0.5.0:
Can i control to the Echo Plus Bridge connected Lamps with pimatic?
You can try if http://[IP of echo plus]/description.xml shows some output.
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 get no answer from the Echo
@michbeck100 the trick with switching a device while in discovery doesn’t work for me.
I get the following in the log when I try to switch:
18:12:17.420 [pimatic-echo] warn: device with id 01 not found
doesn’t matter which device I try to switch.
@thex has you researched the Devices after the update to 0.5.2? This Warn mines that alexa dont know this device… or has a old device thats not in the pimatic
No I understood that this is not necessary with the fix @michbeck100 implemented.
@michbeck100 said in [pimatic-echo] Release 0.5.0:
@thex Waiting is over, just released version 0.5.1. If you start the discovery mode in pimatic and ask alexa to switch a device, the the user should be added automatically and a new file in echo-database should be created.
@thex 0.5.1 wars bugi and with 0.5.2 is needed to rescan
Get
npm WARN engine pimatic-echo@0.5.2: wanted: {“node”:">4.4",“npm”:">2.15"} (current: {“node”:“4.8.3”,“npm”:“2.15.12”})
pimatic-echo@0.5.2
during update process.
Whats the problem?
Thanks
@dk00000 Nope this should be no Problem!
Is anyone here using just the new echoes with pimatic-echo? It seems that discovery doesn’t work (anymore). I was quite sure that it did work when i tested the last time, but it seems that something changed since then.
See https://github.com/openhab/openhab2-addons/issues/2881 and https://github.com/bwssytems/ha-bridge/issues/810
I can confirm that it doesn’t work for me either.
So if you have a working setup don’t remove the devices. I will do my very best to not break this with an pimatic-echo update. The echo dot and echo 1st gen work without 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