pimatic-echo is a pimatic plugin that enables Amazon's echo to control pimatic devices. It does this by simulating Philips Hue lights, which are natively supported by the echo. All network communication happens on the local network, so pimatic doesn't have to be accessible from the internet.
These device classes are supported currently:
- ButtonsDevice (just the first defined button)
- All devices extending from ShutterController (Shutters will go up when switched on and vice versa)
- All lights from pimatic-led-light, pimatic-hue-zll, pimatic-milight-reloaded and pimatic-tradfri
- All thermostats from pimatic-maxcul and pimatic-mythermostat
If you are the developer of a pimatic plugin that defines a device class, that implements switch functionality, just create a feature request.
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 are
- Alexa, 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.
To install the plugin just add the plugin to the config.json of pimatic:
This will fetch the most recent version from npm-registry on the next pimatic start and install the plugin.
After that you tell your Amazon echo to search for your devices or use the web frontend.
For configuration parameters of pimatic-echo and their documentation please see the plugin config schema.
Please note that pimatic-echo will use port 80 by default, as this is needed for the newer echo, so make sure that this port is either free or change it to another free port. If your pimatic instance is using port 80, pimatic-echo will reuse the port.
The configuration of pimatic can be extended by adding an attribute called "echo" on every supported device.
The name setting will change how the device is called when using your voice. This might be helpful if you have multiple devices in different rooms with the same name or if you just want to have a more meaningful name. To work with Alexa these names must be unique. You can also define additional names for your device. For every additional name a new device will be listed in the Alexa app.
To make devices available to Alexa, just set the "active" flag to true. You must manually activate them.
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.
Frequently Asked Questions
Alexa doesn't find any devices. What's wrong?
- Make sure to enable the pairing mode by using the device discovery feature of pimatic found under Settings -> Devices. Then you've got 20 seconds start the device scanning of Alexa.
- By default pimatic-echo uses port 80. So make sure that the port isn't used by another process. Running pimatic on port 80 is fine, as pimatic-echo will reuse the port. You can also change the port in the plugin config.
- If you edit device properties via the web frontend, make sure to restart pimatic afterwards.
- Just try to scan again. Sometimes Alexa needs another try to find all devices.
Do you like this plugin? Then consider a donation to support development.
- #77 add compatibility with node 4 again
- add peerDependencies on package.josn again. Hope this fixes the problem that pimatic doesN#t find the update
- #76 create hash from device name, because device id is the same if using aditionalNames config or button device
- #71 Add pimatic-raspbee support for dim-lights
- create hash from device id so every device keeps its index. Strings as index are not supported. This fixes the issue, that alexa mixes up devices if a device is deleted or moved in pimatic
- move from int for index to string using device id, seems to work, too. This fixes the issue, that alexa mixes up devices if a device is deleted or moved in pimatic
- #72 Encode returned json from hue emulator with iconv-lite using UTF-8 encoding.
- #67 Default port for hue emulator is 80 again, also some changes to the upnp device discovery
- #46 return error response for groups request
- #45 return false if state is null
- maximum number of devices reduced to 49, 50 seems to be too high
- minor improvements
- Add pairing mode using the built in discovery feature of pimatic.
- #38 add Tradfri RGB
- fix issues when mixing echoes of different generations
- reuse port of pimatic if port is equal to piamtic-echo
- bind express server to single ip
- fix echo config migration from blacklist to whitelist
- Add limit of 50 devices since echo seems to have a device limitation (see. https://github.com/bwssytems/ha-bridge/issues/119)
- fix getting state for pimatic-led-light
- dim lights without turning on before
- bugfixes and imporvements
- #8 support changing dimlevel
- add support for trafri devices
- #20 randomizing device discovery responses befor sending them out. This way you can discover more than 16 devices within a few scans with the echo.
- fixed error when switching ButtonsDevice
- #10 additional names for supported devices
- #3 Rename devices
- extend device config schema to get rid of error message
- Copied files from fauxmo dependency into lib folder and removed dependency
- Reuse UDP port 1900 for UPNP
- #5 Exclude specific devices from being available to Alexa.
- minor bugfixes
- initial release