@michbeck100 @t1m0 … Problem solved … i supported him via Chat.
-
Amazon Echo / Alexa
-
@tehmilcho said in Amazon Echo / Alexa:
@michbeck100 @t1m0 … Problem solved … i supported him via Chat.
THANKS!!!
-
Hi,
I have a Problem with the new Echo discovering devices. It says, “no devices found”.
This is my Debug log:
19:46:33.100 [pimatic] info: Loading plugin: “pimatic-echo” (0.3.1)
19:46:33.807 [pimatic-cron] info: the time is: Thu Nov 02 2017 19:46:33 GMT+0100 (CET)
19:46:34.012 [pimatic-sunrise] info: Your location is set to lat: 37.371794, long: -122.03476
19:46:34.080 [pimatic-hap] info: Starting homekit bridge
19:46:34.107 [pimatic-echo] info: Starting pimatic-echo…
19:46:34.110 [pimatic-echo] debug: Using ip address: null
19:46:34.297 [pimatic] error: Invalid config of device “lampe_stollenwand_rechts”: Property “echo” is not a valid property
19:46:34.712 [pimatic] info: New device “dummy”…
19:46:34.725 [pimatic-hap] debug: successfully added device dummy
19:46:34.726 [pimatic-echo] debug: successfully added device dummy
19:46:35.251 [pimatic-hap] debug: publishing homekit bridge on port 51826
19:46:35.253 [pimatic-hap] debug: pincode is: 031-45-154
19:46:35.403 [pimatic-echo] debug: udp server listening on port 1900
19:46:35.405 [pimatic-echo] info: started hue emulator on port 9876“lampe_stollenwand_rechts” is a ShellSwitch - which seems to be not supported - but at least the dummySwitch should be recognized.
From my point of view strange is “19:46:34.110 [pimatic-echo] debug: Using ip address: null”
Can someone give me a hint how to proceed or what I m missing?
-
@lue49 See the Details of the Plugin, in the last updates there some changes…
“Please make sure that pimatic-echo is placed at the top of the plugins configuration. This helps avoiding misleading error messages, that the echo configuration is unsupported and also enables the configuration via web ui.”
https://github.com/michbeck100/pimatic-echo/
Also the “IP” option in the Plugin is not needed anymore so this line can be out. It just should be look like this:
{ "plugin": "echo" }
When you put the Plugin as frist plugin that will be loaded make sure you have set your Device to “active” by default all devices will be “inactive” so Alexa cant find them because there is a limit by ~50 Devices that Alexa can Handle from a single source!
-
@tehmilcho Hi, unfortunately, this didnt help. What I tried meanwhile (I received a Philips Hue Bridge today as well - will they work in parallel in the same network with Echo?) is placing the “Pimatic Hue Bridge” on port 80, as the original hue bridge does - but this didnt help as well.
For sure, the dummy device is available. Accessing the Pimatic Plugin via URL Get on:
http://192.168.178.72:9876/api/:userid/lights
delivers
{ "01": { "state": { "on": true, "bri": 0, "hue": 0, "sat": 0, "effect": "none", "ct": 0, "alert": "none", "reachable": true }, "type": "Dimmable light", "name": "Lampe Flur unten", "modelid": "LWB004", "manufacturername": "Philips", "uniqueid": "00:17:88:5E:D3:01-01", "swversion": "66012040" }, "02": { "state": { "on": true, "bri": 0, "hue": 0, "sat": 0, "effect": "none", "ct": 0, "alert": "none", "reachable": true }, "type": "Dimmable light", "name": "Lampe Flur", "modelid": "LWB004", "manufacturername": "Philips", "uniqueid": "00:17:88:5E:D3:02-02", "swversion": "66012040" }, "03": { "state": { "on": false, "bri": 0, "hue": 0, "sat": 0, "effect": "none", "ct": 0, "alert": "none", "reachable": true }, "type": "Dimmable light", "name": "dummy", "modelid": "LWB004", "manufacturername": "Philips", "uniqueid": "00:17:88:5E:D3:03-03", "swversion": "66012040" }, "04": { "state": { "on": false, "bri": 0, "hue": 0, "sat": 0, "effect": "none", "ct": 0, "alert": "none", "reachable": true }, "type": "Dimmable light", "name": "Dummy Schalter", "modelid": "LWB004", "manufacturername": "Philips", "uniqueid": "00:17:88:5E:D3:04-04", "swversion": "66012040" } }
On top I tried to run pimatic from command line like mentioned in https://github.com/michbeck100/pimatic-echo/issues/7
Strange: I dont get any debug messages like
ssdp-server using ip address: 192.168.1.13 +0ms ssdp-server binding to port 1900 for ssdp discovery +16ms
If I trace the udp traffic with iptables the echo seems to send upd traffic (ECHO is on ip 192.168.178.39)
Nov 2 22:29:00 raspberrypi kernel: [ 936.663537] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:81:6e:3a:40:00:04:11:a5:67 SRC=192.168.178.39 DST=239.255.255.250 LEN=129 TOS=0x00 PREC=0x00 TTL=4 ID=28218 DF PROTO=UDP SPT=50000 DPT=1900 LEN=109 Nov 2 22:29:00 raspberrypi kernel: [ 936.672004] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:7a:6e:3b:40:00:04:11:a5:6d SRC=192.168.178.39 DST=239.255.255.250 LEN=122 TOS=0x00 PREC=0x00 TTL=4 ID=28219 DF PROTO=UDP SPT=50000 DPT=1900 LEN=102 Nov 2 22:29:01 raspberrypi kernel: [ 937.176182] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:81:6e:50:40:00:04:11:a5:51 SRC=192.168.178.39 DST=239.255.255.250 LEN=129 TOS=0x00 PREC=0x00 TTL=4 ID=28240 DF PROTO=UDP SPT=50000 DPT=1900 LEN=109 Nov 2 22:29:01 raspberrypi kernel: [ 937.177889] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:7a:6e:51:40:00:04:11:a5:57 SRC=192.168.178.39 DST=239.255.255.250 LEN=122 TOS=0x00 PREC=0x00 TTL=4 ID=28241 DF PROTO=UDP SPT=50000 DPT=1900 LEN=102 Nov 2 22:29:01 raspberrypi kernel: [ 937.676088] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:81:6e:6e:40:00:04:11:a5:33 SRC=192.168.178.39 DST=239.255.255.250 LEN=129 TOS=0x00 PREC=0x00 TTL=4 ID=28270 DF PROTO=UDP SPT=50000 DPT=1900 LEN=109 Nov 2 22:29:01 raspberrypi kernel: [ 937.695785] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:7a:6e:6f:40:00:04:11:a5:39 SRC=192.168.178.39 DST=239.255.255.250 LEN=122 TOS=0x00 PREC=0x00 TTL=4 ID=28271 DF PROTO=UDP SPT=50000 DPT=1900 LEN=102 Nov 2 22:29:02 raspberrypi kernel: [ 938.180100] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:81:6e:70:40:00:04:11:a5:31 SRC=192.168.178.39 DST=239.255.255.250 LEN=129 TOS=0x00 PREC=0x00 TTL=4 ID=28272 DF PROTO=UDP SPT=50000 DPT=1900 LEN=109 Nov 2 22:29:02 raspberrypi kernel: [ 938.197211] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:7a:6e:71:40:00:04:11:a5:37 SRC=192.168.178.39 DST=239.255.255.250 LEN=122 TOS=0x00 PREC=0x00 TTL=4 ID=28273 DF PROTO=UDP SPT=50000 DPT=1900 LEN=102 Nov 2 22:29:02 raspberrypi kernel: [ 938.687568] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:81:6e:80:40:00:04:11:a5:21 SRC=192.168.178.39 DST=239.255.255.250 LEN=129 TOS=0x00 PREC=0x00 TTL=4 ID=28288 DF PROTO=UDP SPT=50000 DPT=1900 LEN=109 Nov 2 22:29:02 raspberrypi kernel: [ 938.696731] IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:38:f7:3d:69:6f:d2:08:00:45:00:00:7a:6e:81:40:00:04:11:a5:27 SRC=192.168.178.39 DST=239.255.255.250 LEN=122 TOS=0x00 PREC=0x00 TTL=4 ID=28289 DF PROTO=UDP SPT=50000 DPT=1900 LEN=102
any idea?
-
Ok, I m getting closer to the problem.
From my point of view, the plugin is not compatible with the echo 2 - at least starting from new.
I had to adopt the upd discovery part, after that the echo 2 is trying to get a user from the bridge. I added that functionality - then finally the echo identified new devices. But there is still a hand full of exception thrown while trying to switch.
I m not used to work with open source projects. Can someone give me a short hand on how to contribute here or how to hand over the gathered information and adopted code?
-
@lue49 When you say echo 2 you mean the new echo, is sold since this week? Since i don’t have one of these, yet, i can’t say if something changed on the udp discovery part.
Would be good if you could describe what parts you changed.Easiest way would be to create a fork of pimatic-echo on github and just push your changes. Once you’re finished you can create a pull request and i will review the changes and integrate them.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 -
Hello together,
i use Zwave Razberry from Zwave.me. There is a skill for that and i can controll my devices via zwave Smart Home UI to Pimatic.
You must activate and install APP via Smart Home UI. Install Alexa Skill. Important for Login is your ID! You must enter your ID/loginname otherwise it doesn’t work.
You must create an http device at Smart Home UI as followed:
Important: Checkmark for update value on action.
Thereafter you may need reboot Smart Home UI. Alexa sometimes doesn’t finding new devices.
Thats all… Another solution for Pimatic.
-
@michbeck100 Yes, I m talking about the new echo 2.
Actually a lot changes. And I cant see any hint on version / compatability the echo is sending, so propably this plugin has to be branched / taged for support of the new echo. What I identified up to now:
. UDP discover changed ( at least according to the code)
. Echo now tries to first register a user (only once per bridge as I can see for now)
. the set JSON parameter differ (still have to investigate)I ll start working on this now (got some time now and over the weekend). As soon as I have something running, I ll try to paste the code on github.
-
@michbeck100 Work is first of all done. Works fine at my site for now.
Doku change required:
. http://pimatic/api is called by the echo 2 to receive a userId. A static ID is handed over
. the hueType needs to be set for switches (non dimmers). Else the echo would throw brightness events when switching lights on which will result in an error notified via voice by alexa
. Port 80 has to be used (maybe by some investigation, the description.xml could include a hint for echo to not use port 80)Changes
. removed debug log for using ip address
. added multiple debug messages
. added a Hue DeviceType attribute for echo config to differ between dimmer and switch
. changed the expected ST attribute in the UDP discovery from ‘urn:schemas-upnp-org:device:basic:1’ to ‘upnp:rootdevice’
. added support for retrieving API userId
. added support for SwitchBased Hue deviceType (‘On/Off plug-in unit’)Fixes
. changed analysis of message for changing device states
. removed empty services the description.xml -
So today I tested the integration with my echo, first impressions: Lights work (although appear as dimmable when they are not)
But unfortunately my DummyThermostats don’t work
Am I missing something?
{ "comfyTemp": 19, "ecoTemp": 17, "guiShowValvePosition": true, "guiShowPresetControl": false, "guiShowTemperatureInput": true, "id": "termostato-habitacion", "name": "Termostato Habitacion", "class": "DummyHeatingThermostat", "guiShowModeControl": false, "echo": { "additionalNames": [], "active": true } },
-
@mat1990dj what does not work? Have you read the complete info on https://pimatic.org/plugins/pimatic-echo/?
-
The two thermostats I have are detected as dimmable light bulbs on alexa instead of thermostats, is that the expected behaviour?
-
@mat1990dj yep thats correct! All devices over the plugin will be detected as dimmable lights because its not a alexa skill. And alexa will only control lights without a alexa skill. Please read the plugin info, there will you see that you musst say “alexa dim Device to 25%” to set your heating to 25c°. This works fine.
"Commands
The supported commands for Alexa are very limited, due to the fact that pimatic-echo doesn’t implement an Alexa smart home skill. Instead it supports switching on/off and dimming. Soe the commands areAlexa, turn on living room
Alexa, switch off living room
Alexa, dim living room to 50 percent
Alexa, turn on Thermostat
These commands also apply to thermostats. Switching a thermostat off will set the temperature to the configured ecoTemp. Switching on will use the comfyTemp. Setting a dimlevel will set the temperature to this value" -
There will ba an official Alexa smart home skill for pimatic. Please be patient. Until then every supported device looks like dimmable lights.
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 in Amazon Echo / Alexa:
There will ba an official Alexa smart home skill for pimatic. Please be patient. Until then every supported device looks like dimmable lights.
Cool! Did you have an ETA?
-
@swen said in Amazon Echo / Alexa:
Cool! Did you have an ETA?
Don’t be too excited, i’m planning to release this skill with in-skill payments, because it needs resources hosted on Amazon’s AWS platform, for which i get charged, too. This will be roundabout 6-12 € per year. Unfortunately in-skill payments aren’t rolled out for germany, yet.
But there might be a beta phase before .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 would be Beta-Testing if you want, i can transfer you the the ~15euro via Paypal if you want.
-
@tehmilcho I’ll keep that in mind
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 -
Hm, hope you will have much luck with that. I don’t go this way. There are many other ways for free. Next thing is that Pimatic will be update in the future that users stay, cause of NodeJS 8.0 core…