michbeck100 / pimatic-echo Goto Github PK

View Code? Open in Web Editor NEW

17.0 17.0 10.0 672 KB

Pimatic plugin that integrates Amazons smart home skill

License: GNU General Public License v3.0

CoffeeScript 100.00%

pimatic-echo's People

Contributors

Stargazers

Watchers

Forkers

thexperiments frotzamuta danielluecke treban froehlyeisvogel heiko1988 hannemann maxwinterstein smarthomeagentur fbeek microgenios

pimatic-echo's Issues

Feature request: rename devices and group them?

i think in some cases its useful to rename devices to a other name as the device name within pimatic and group them by seperate id

"devices": [
  {
    "id": "switch",
    "class": "DummySwitch",
    "name": "Workroom Switch",
    "echo": {
      "name": "Light",
      "room": "Workroom"
    }
  }
]

so alexa could handle something like:
"alexa, turn [name] in the [room] on"
or
"alexa, turn all in the [room] on"
or
"alexa, turn in the [room] the [name] on"

How to have switches not as lights?

Hallo Michael @michbeck100
This is more a question but an issue. Not sure how else to ask:
Is it possible to classify a switch not as a light?
My use case: I have an Espresso machine connected to a WiFi socket. I can control that via Alexa.
But when I tell her „all lights on“, she also switches on the espresso machine, what I do not want.
Any way?
Remark: I only have the switches connected via hue emulation. Would that differ if they are connected via WeMo emulation? If so, how would I do this, Alexa shows only the hue devices...
Thanks!
Roger

Button Device does not respond

Hello, I upgraded to version 0.4.2 today. Unfortunately my button device does not work anymore. In Alexa App appears “Device does not respond”. In version 0.4.1 it worked great.

Crash on Dimmlevel 100%

Every Dimm to 100% or MAX Crashes Pimatic with error:
"Fatal AssertionError: 0 <= level <= 100"
Port for Echo is 81 but I don´t think this causes it.

Edit: Also Crashes on set dimmlevel to Zero.

Feature request: Support Thermostat-Devices

a nice feature would be to control max. or other thermostat devices by
"Alexa, set Heating control in Livingroom to 21 degrees"
"Alexa, turn Heating control in Livingroom to eco mode"
"Alexa, turn Heating control in Livingroom off"

cant see any device in alexa

I have scanned my network several times but cant see any devices. i have set the logging to debug but i have no log entrys from the plugin.

regards

pimatic crashes after update to 0.4.1

Hi, after updating to version 0.4.1 pimatic crashed:

[pimatic] Invalid config of pimatic-echo: Missing property "address,mac"

13:33:04.283 [pimatic] An uncaught exception occurred: Error: listen EADDRINUSE :::12002
13:33:04.283 [pimatic]>    at Object.exports._errnoException (util.js:907:11)
13:33:04.283 [pimatic]>    at exports._exceptionWithHostPort (util.js:930:20)
13:33:04.283 [pimatic]>    at Server._listen2 (net.js:1253:14)
13:33:04.283 [pimatic]>    at listen (net.js:1289:10)
13:33:04.283 [pimatic]>    at Server.listen (net.js:1385:5)
13:33:04.283 [pimatic]>    at EventEmitter.listen (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/application.js:618:24)
13:33:04.283 [pimatic]>    at /home/pi/pimatic-app/node_modules/pimatic-echo/lib/wemo.coffee:140:18
13:33:04.283 [pimatic]>    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/lodash/lodash.js:4944:15
13:33:04.283 [pimatic]>    at baseForOwn (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/lodash/lodash.js:3001:24)
13:33:04.283 [pimatic]>    at Function.forOwn (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/lodash/lodash.js:13002:24)
13:33:04.283 [pimatic]>    at Wemo.start (/home/pi/pimatic-app/node_modules/pimatic-echo/lib/wemo.coffee:139:9)
13:33:04.283 [pimatic]>    at EchoPlugin._startEmulator (/home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:143:13)
13:33:04.283 [pimatic]>    at Framework.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:57:10)
13:33:04.283 [pimatic]>    at Framework.g (events.js:260:16)
13:33:04.283 [pimatic]>    at emitOne (events.js:82:20)
13:33:04.283 [pimatic]>    at Framework.emit (events.js:169:7)
13:33:04.283 [pimatic]>    at /home/pi/pimatic-app/node_modules/pimatic/lib/framework.coffee:948:12
13:33:04.283 [pimatic]>    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
13:33:04.283 [pimatic]>    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31)
13:33:04.283 [pimatic]>    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
13:33:04.283 [pimatic]>    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
13:33:04.283 [pimatic]>    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
13:33:04.283 [pimatic]>    at Promise._fulfill (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:638:18)
13:33:04.283 [pimatic]>    at Promise._resolveCallback (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:432:57)
13:33:04.283 [pimatic]>    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:524:17)
13:33:04.283 [pimatic]>    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
13:33:04.283 [pimatic]>    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
13:33:04.283 [pimatic]>    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
13:33:04.283 [pimatic]>    at Promise._fulfill (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:638:18)
13:33:04.283 [pimatic]>    at PromiseArray._resolve (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise_array.js:126:19)
13:33:04.283 [pimatic]>    at PromiseArray._promiseFulfilled (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise_array.js:144:14)
13:33:04.283 [pimatic]>    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:574:26)
13:33:04.283 [pimatic]>    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
13:33:04.283 [pimatic]>    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
13:33:04.283 [pimatic]>    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16)
13:33:04.283 [pimatic]>    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
13:33:04.283 [pimatic]>    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
13:33:04.283 [pimatic]>    at processImmediate [as _immediateCallback] (timers.js:396:17)
13:33:04.283 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
13:33:04.297 [pimatic] exiting...

Also adding the address and mac property doesn't help. Would be nice, if these were added automatically.

Error: group 0 not supported

Hi,

habe mein altes Problem behoben bekommen, habe wie gesagt Port 80 freigemacht.

Danach konnte ich Geräte finden und schalten. jetzt habe ich weitere Geräte hinzugefügt, pimatic neugestartet und bekomme jetzt in der Konsole folgenden Fehler.

Error: group 0 not supported
    at /home/pi/pimatic-app/node_modules/pimatic-echo/lib/hue.coffee:271:15
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:281:22
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:354:14)
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:365:14)
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:410:3)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:129:11
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at jsonParser (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/lib/types/json.js:109:7)
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at jsonParser (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/lib/types/json.js:109:7)
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at expressInit (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/middleware/init.js:40:5)
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at query (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/middleware/query.js:45:5)
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at Function.handle (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:174:3)
    at EventEmitter.handle (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/application.js:174:10)
    at Server.app (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/express.js:39:9)
    at emitTwo (events.js:87:13)
    at Server.emit (events.js:172:7)
    at HTTPParser.parserOnIncoming [as onIncoming] (_http_server.js:536:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:103:23)

echo finds the pimatic devices no longer

Hello,

I use 4 Echo (2. generation) with pimatic (latest version), the pimatic plugin (0.5.2), some yeelight, homeduino and TP-Link smartplug devices. Since some days the echos no longer find new devices but the older ones still worked. After I noticed that I restarted the pimatic-pi but the problem was still there. Even a reinstall of the echo-plugin and deleting all old devices brought no success. Now the Echos find my devices anymore (discover devices was activated).

There are no errors in the log and i can access the api under /api//lights/.

Did I miss something? I would be glad about help.

baddle

Please enable COCSwitch

Hi,

thanks for the great plugin!
I'd like to request enabling coc plugin based devices (COCSwitch).

Thanks. Kay.

since echo 0.4.7 - no device found

since the version 0.4.7 i cant find any device in alexa :(

pimatic-echo crashes PS4

See the follwoing thread for details. Presumably it is caused by the UPnP messaging.

https://forum.pimatic.org/topic/2926/pimatic-echo-crashes-ps4

Fix device limit

It seems that there is a limit for the devices that echo supports. One option would be to create multiple upnp listeners.

Request: Support for ShellSwitches

Hey,

its possible that you can add support for ShellSwitches? Now the will work but you cant exclude them by the WebGUI. i can i manually add the exclude to the Config?

Thank you!

Set second names for buttons

At the moment it's not possible to set alternate names for multiple button devices.

https://photos.app.goo.gl/zMJgX9X0STWxJjUJ3

adding timer

it would be great to set a timer device :)

echo plus support?

Hello all,

i have not been successful to find pimatic devices with the new Echo Plus. Do not have another echo, so I cannot check if the workaround mentioned before to find pimatic with an older echo works.
I am happy to provide protocols, etc. to help implementation.
thanks!
Roger

PS: really interesting would be also to control the devices paired to the echo plus. but that is another topic :-D

z-way z-wave devices no longer work with the echo

After the last updates I completely deleted all devices from echo/alexa and added them again. I now cant dim or switch my z-way devices anymore.

"Alexa, dim fancy light to 10%" --> "Sorry, fancy light does not support this"
"Alexa turn on fancy light" --> "Sorry fancy light doesn't answer"

Dummy switches seem to work fine.
Can't see any error messages in the log.

Echo 0.5.1 - Echo Options in Devices are Missing - Alexa says "Devices not response"

Hi,

installed the Update but now all Devices will not work anymore... the "echo" options in the Devices are gone.. and get from every device the Error:

error [pimatic]: Invalid config of device "kuche-firetv": Property "echo" is not a valid property
18:49:01error [pimatic]: Invalid config of device "tradfri_scene_131074": Property "echo" is not a valid property
18:49:01error [pimatic]: Invalid config of device "tradfri_scene_131073": Property "echo" is not a valid property
18:49:01error [pimatic]: Invalid config of device "tradfri_scene_131075": Property "echo" is not a valid property

I reseached for Devices, Alexa says "the Device will not response".

Extend hue protocol

The implementation of the hue protocol is very limited. Alexa/echo works fine but other devices (in my case a harmony hub) do not work.
I know that the main intention of this plugin is to make devices available to echo, but I think an extension to other products would not harm.

I tested a bit and I think the main problem currently is, that there is no possibility to register new users.
This project may help to implement the missing parts: https://github.com/peterkaminski/kingfish
New users are requested by calling the url
[ip]:[port]/api/[something]
and the response should look like this (the name may differ ;)):

[
    {
        "success": {
            "username": "6e4bcbc7bc5843b88d876012b6868dfb"
        }
    }
]

All following requests to the "bridge" will look like
[ip]:[port]/api/6e4bcbc7bc5843b88d876012b6868dfb/...

Maybe it would also make sense to create it as a new plugin "hue-sim" or something similar.

Kind regards,
Daniel

multiple word for one device

i wold be great to define multiple words for one device because the naming in pimatic and whats alexa understands is not the same.

"zbox" needs to be renamed to "z box".
alexa dont understand "eck lampen". for alexa its "deckenlampen" :D

Add HomematicHeatingThermostat

Hi,

would be nice to control Homematic HeatingThermostats from Pimatic Homegear Plugin :)

Thanks for your nice plugin, thanks for your work !

Make start port for WeMo emulator configurable

Echo 2nd gen can not operate devices

Hi,
after change the port of the plugin to 80 the Echo 2nd gen. is able to discover activated devices from pimaitc. Unfortunatelly it can't be operated/switched.

Here the log content:

07:33:40.670 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
Unhandled rejection Error: Expected variable sonnensensor.temp_high to have a numeric value.
    at /home/pi/pimatic-app/node_modules/pimatic/lib/variables-ast-builder.coffee:111:17
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:396:17)
07:33:50.775 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:34:00.826 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:34:10.872 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:34:20.920 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:34:30.969 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:34:41.031 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:34:51.086 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:35:01.150 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:35:02.924 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:04.554 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:08.210 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:11.205 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:35:12.940 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:17.699 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:21.276 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:35:22.766 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:27.799 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:31.330 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:35:32.848 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:37.878 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:41.390 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:35:42.907 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:47.949 [pimatic-echo] debug: Request to /socket.io/?username=xxx&EIO=3&password=123&transport=polling
07:35:51.438 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:36:01.482 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:36:11.527 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:36:21.587 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:36:31.641 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:36:41.703 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:36:51.752 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:37:01.805 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:37:11.862 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:37:21.910 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:37:31.956 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:37:42.012 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:37:52.061 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:38:02.114 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:38:12.165 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:38:22.380 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:38:32.426 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:38:42.489 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:38:52.538 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:39:02.590 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:39:12.638 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:39:22.686 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:39:22.776 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01
07:39:22.798 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01
07:39:24.981 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01
07:39:25.007 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01/state
07:39:25.009 [pimatic-echo] debug: Payload: {"on":true}
07:39:25.012 [pimatic-echo] debug: changing state for Saugron Ladung: {"on":true}
SyntaxError: Unexpected token o
    at Object.parse (native)
    at Object.devices.(anonymous function).changeState (/home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:73:32)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:291:27
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:281:22
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:354:14)
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:365:14)
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:365:14)
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:410:3)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:248:11
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/lib/read.js:130:5
    at invokeCallback (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:224:16)
    at done (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:213:7)
    at IncomingMessage.onEnd (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:273:7)
    at emitNone (events.js:67:13)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:923:12)
    at nextTickCallbackWith2Args (node.js:511:9)
    at process._tickCallback (node.js:425:17)
07:39:32.734 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:39:42.796 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:39:52.856 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:39:54.825 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01
07:39:54.840 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01
07:39:55.500 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01
07:39:55.515 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights/01/state
07:39:55.518 [pimatic-echo] debug: Payload: {"on":true}
07:39:55.520 [pimatic-echo] debug: changing state for Saugron Ladung: {"on":true}
SyntaxError: Unexpected token o
    at Object.parse (native)
    at Object.devices.(anonymous function).changeState (/home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:73:32)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:291:27
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:281:22
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:354:14)
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:365:14)
    at param (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:365:14)
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:410:3)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/echo.coffee:248:11
    at Layer.handle [as handle_request] (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:317:13)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:335:12)
    at next (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/express/lib/router/index.js:275:10)
    at /home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/lib/read.js:130:5
    at invokeCallback (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:224:16)
    at done (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:213:7)
    at IncomingMessage.onEnd (/home/pi/pimatic-app/node_modules/pimatic-echo/node_modules/body-parser/node_modules/raw-body/index.js:273:7)
    at emitNone (events.js:67:13)
    at IncomingMessage.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:923:12)
    at nextTickCallbackWith2Args (node.js:511:9)
    at process._tickCallback (node.js:425:17)
07:40:02.903 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:40:12.946 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:40:23.002 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:40:33.206 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:40:43.264 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights
07:40:53.313 [pimatic-echo] debug: Request to /api/83b7780291a6ceffbe0bd049104df/lights

Any idea what went wrong here?

Feature request: control color of led-lights

it will be nice to control the color of led-light and milight-reloaded devices like "alexa. set the color of kitchen leds to yellow"

Feature request: get better response as "okay"

it would be also nice if alexa could be give back a better response what she really did.
for now only "okay" responses...

example:
command: "alexa, turn Livingroom Light on"
response: "okay, i've turned on the Light in the livingroom" or
"okay, i've turned Livingroom Light on"

command: "alexa, set the livingroom heating to 23 degrees"
response: "okay, i've set the Livingroom temperature to 23 degrees"

problem with echo plugin if I use IP adress for one of my alexas

If I use an ip address of the network interface to use for one of my alexas, than I cannot start pimatic (see attached error log). As far as I understood - if I use more than one alexa - I have to use an ip address if I want to discover new devices (with the alexa with this specified IP Address) - if I don't specify an ip address in the plugin - I can start pimatic without problems - is this a bug?
pimatic-daemon.log

Property "ipAddress" is not a valid property

Hi,

since the last update i get the following Error by every Reboot from Pimaitc:

error [pimatic]: Invalid config of pimatic-echo: Property "ipAddress" is not a valid property

Config:
{
"ipAddress": "192.168.178.20",
"plugin": "echo",
"active": true
},

have you Removed the Config "ipAddress" ?

Add blacklist for IP addresses

This feature adds a blacklist for IP addresses, so one can make sure that some devices in the network are filtered when requesting ssdp discovery

Guest wifi fritzbox

At the moment the guest wifi switch from the fritzbox plugin is shown as dimmable device in alexa

Devices don't show up despite the protocol seems to be working

I have no luck getting my device to show up in the Alexa app for my Echo Dot.
I already tried the debug command from issue #7 and if I start a device discovery the following happens, but no device shows up. Is there anything else I can try?

  ssdp-server << server got: M-SEARCH * HTTP/1.1
  ssdp-server HOST: 239.255.255.250:1900
  ssdp-server MAN: "ssdp:discover"
  ssdp-server MX: 15
  ssdp-server ST: urn:schemas-upnp-org:device:basic:1
  ssdp-server
  ssdp-server  from 192.168.10.101:50000 +54s
  ssdp-server >> sending response string:  HTTP/1.1 200 OK
CACHE-CONTROL: max-age=86400
DATE: 2016-10-29
EXT:
LOCATION: http://192.168.10.136:12001/8c08a4ea-41da-498f-801b-2bbb9f1ad66d/setup.xml
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 146
SERVER: Unspecified, UPnP/1.0, Unspecified
ST: urn:Belkin:device:**
USN: uuid:Socket-1_0-8c08a4ea-41da-498f-801b-2bbb9f1ad66d::urn:Belkin:device:**

 +1ms
  ssdp-server >> sending response string:  HTTP/1.1 200 OK
CACHE-CONTROL: max-age=86400
DATE: 2016-10-29
EXT:
LOCATION: http://192.168.10.136:12002/e3056b7e-e519-4740-8d8b-341939351f09/setup.xml
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 146
SERVER: Unspecified, UPnP/1.0, Unspecified
ST: urn:Belkin:device:**
USN: uuid:Socket-1_0-e3056b7e-e519-4740-8d8b-341939351f09::urn:Belkin:device:**

 +1ms
  ssdp-server >> sending response string:  HTTP/1.1 200 OK
CACHE-CONTROL: max-age=86400
DATE: 2016-10-29
EXT:
LOCATION: http://192.168.10.136:12003/a936362d-b4d8-4182-88b9-64d0da0a1e77/setup.xml
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 146
SERVER: Unspecified, UPnP/1.0, Unspecified
ST: urn:Belkin:device:**
USN: uuid:Socket-1_0-a936362d-b4d8-4182-88b9-64d0da0a1e77::urn:Belkin:device:**

 +1ms
  ssdp-server >> sending response string:  HTTP/1.1 200 OK
CACHE-CONTROL: max-age=86400
DATE: 2016-10-29
EXT:
LOCATION: http://192.168.10.136:12004/76ed42d2-129d-4543-8704-b4b54208041b/setup.xml
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 146
SERVER: Unspecified, UPnP/1.0, Unspecified
ST: urn:Belkin:device:**
USN: uuid:Socket-1_0-76ed42d2-129d-4543-8704-b4b54208041b::urn:Belkin:device:**

 +0ms
  ssdp-server sending device response. +1ms
  ssdp-server >> sent response ssdp discovery response +1ms
  ssdp-server sending device response. +0ms
  ssdp-server >> sent response ssdp discovery response +1ms
  ssdp-server sending device response. +0ms
  ssdp-server >> sent response ssdp discovery response +1ms
  ssdp-server sending device response. +0ms
  ssdp-server >> sent response ssdp discovery response +1ms
  ssdp-server complete sending all responses.  Success +0ms

(after that it repeats itself)

Request support for "Milight Reloaded" Devices

Hi,

the Devices from the Plugin "milight reloaded" will not discovered in Alexa. All other Devices works fine.

Config of the Device:
{
"ip": "192.168.1.81",
"echo": {
"additionalNames": [],
"active": true
},
"id": "test",
"name": "test",
"class": "MilightFullColorZone",
"zoneId": 1
}

The Device has no Switch just one Silder for Color and one Silder for Dimming (0 - 100%)

The Problem is the other Milight Plugin (works fine) but dont support the new Devices from Milight.

If you need something more, let me know.

Greetings Milcho

Add TradfriRGB

Template is 'tradfridimmer-rgb'

duplicated names

I have the following problem.

I use the same display name for several devices. e. g."wohnzimmer".

This means that alexa has duplicated names and can no longer switch some devices.

is it possible to set the default name for alexa in the device settings independent of the display name?

https://www.pic-upload.de/view-34292803/pimatic.png.html

pimatic-shellswitch doesnt work

Hello,

the shellswitch devices are not recognized from Echo. They even dont get the echo configuration on device configuration.

After last update WakeOnLAN Device, Shellswitches and homeduino reports erors, Alexa App Groups cant loaded, Alex switches what see want

Hey since,

the last update i get a lot of erros, with the other Version "WakeOnLAN Device, Shellswitches and homeduino" works fine with alexa, now i must in the config and set all switches to "true" agian, and i get now a lot of errors.

In the Alexa App loads my groups anymore and if say to alexa see should activat a group see is switches not the correct things....

error [pimatic]: Invalid config of device "hombot": Property "echo" is not a valid property
20:33:58error [pimatic]: Invalid config of device "service-z-way-server": Property "echo" is not a valid property
20:33:57error [pimatic]: Invalid config of device "switch_brennen_c": Property "echo" is not a valid property
20:33:57error [pimatic]: Invalid config of device "switch_brennen_b": Property "echo" is not a valid property
20:33:57error [pimatic]: Invalid config of device "switch_brennen_a": Property "echo" is not a valid property
20:33:57error [pimatic]: Invalid config of device "Wohnzimmer_decken_lampe": Property "echo" is not a valid property
20:33:57error [pimatic]: Invalid config of device "telegram-bot": Property "echo" is not a valid property
20:33:56error [pimatic]: Invalid config of device "Switch": Property "echo" is not a valid property
20:33:56error [pimatic]: Invalid config of device "Schlafzimmer_switch_2": Property "echo" is not a valid property
20:33:56error [pimatic]: Invalid config of device "Schlafzimmer_switch_1": Property "echo" is not a valid property
20:33:56error [pimatic]: Invalid config of device "wol_2": Property "echo" is not a valid property
20:33:56error [pimatic]: Invalid config of device "wol_1": Property "echo" is not a valid property
20:33:56error [pimatic]: Invalid config of device "Wohnzimmer_Switch_3": Property "echo" is not a valid property
20:33:55error [pimatic]: Invalid config of device "Wohnzimmer_switch_1": Property "echo" is not a valid property
20:33:55error [pimatic]: Invalid config of device "Wohnzimmer_switch_2": Property "echo" is not a valid property

Feature Request: Get Temperature from Pimatic

Hey Michi, great work with this Plugin.
Maybe you would find some Time to implement ask Alexa for temperature of Pimatic Sensors :)

No devices found with my alexa after discovering for new devices

I wanted to discover for new devices with my alexa - but no devices were found. I started to discover devices within pimatic and soon afterward with alexa. I also already removed all existing devices within alexa and reinstalled the echo plugin in pimatic. I'm using more than one echo dots 2nd generation (3) and use more raspis - with the other ones everything works fine - but not with this one I use.

Can you see something what's wrong with the log file and config I sent?

pimatic-daemon.log

config.txt

Feature request: ex- or include device

it would be nice to ex- or include devices that some devices are not recognized by alexa.

"devices": [
  {
    "id": "switch",
    "class": "DummySwitch",
    "name": "Switch",
    "echo": {
       "include": true
    }
  }
]

show only wanted devices

It would be great if the plugin defaults only lists "echo enabled" devices.

At the moment i have to usw a Blacklist.

Support changing dimlevel

Currently just switching is supported. With emulating a hue bridge like https://github.com/bwssytems/ha-bridge it's also possible to dim lights.

Hue-ZLL not working

Hi,
I cant configure huezlltemplight in pimatic-hue inside of the web gui.
If I configure it in the config is says:
Invalid config of device "deckenlampe-lukas": Property "echo" is not a valid property
Alexa can find the device. But I can't control anything. She says "The device does not support this feature".

In the API are some variables missing.

state
on	null
bri	0
alert	"none"
reachable	true
type	"Dimmable light"
name	"Deckenlampe"
modelid	"LWB007"
manufacturername	"pimatic"
uniqueid	"00:17:88:5E:D3:01-01"
swversion	"66009461"

I guess thats not correct.

Hope you can help.

Pimatic echo 0.4.8 milight ibox2

Hi,
i have upgrade pimatic -echo from 0.4.7 to 0.4.8


From Pimatic Start:
info [pimatic-echo]: started hue emulator on port 9876
12:54:32info [pimatic-echo]: Starting pimatic-echo...
....
.....
error [pimatic]: Invalid config of device "led-band-zone-4": Property "echo" is not a valid property

My Pimatic echo config
    {
      "plugin": "echo",
      "active": true,
      "comfyTemp": 23,
      "ecoTemp": 17,
      "debug": true,
      "trace": true,
      "address": "192.168.0.38",
      "port": 9876
    },

The plugin has always worked very well so far.
only after the update I get the error message.

I have the problem with the milight led lamps and controller for led.
with the bridge ibox2 and in v6 work all normaly

i have the Amazon Echo Dot (2. Generation)

what I already tried:

without ip and mac adress and with ip and mac adress
delete plugin and reinstall
Pimatic Restart

If you need further information please let me know

Greeting Heiko

hue-port crashes pimatic

The hue-port ist actually set to 80.
In you have a webserver installed,
Then pimatic crashes as startup...

I had to deaktivate the plugin or change the port manually...
But for the second way alexa doesn‘t notice any device

Feature request: ask for devices and get data back (Q/A)

include a question/answer response to get som data back was also great,

HomeduinoRFTemperature device
question "alexa, how warm is it in the workroom?"
answer: "the temperature of workroom was 22 comma 8 degrees"

switch devices:
question "alexa, was the state of livingroom on?"
answer: "yes, livingroom was on"

thermostat devices:
question "alexa, how was the state in livingroom heating?"
answer: "the livingroom heating was set to 22 degrees and in eco mode"

presence devices?

michbeck100 / pimatic-echo Goto Github PK

pimatic-echo's People

Contributors

Stargazers

Watchers

Forkers

pimatic-echo's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs