A Node-RED node that represents a virtual smart home device which can be controlled via Amazon Alexa. Requires the 'virtual smart home' skill to be enabled for your Amazon account.
- supports a growing set of device types
- Blinds
- Color Changing Light Bulb
- Contact Sensor
- Dimmable Light Bulb
- Dimmer Switch
- Doorbell Event Source
- Entertainment Device
- Fan
- Garage Door Opener (en-US locale only)
- Lock
- Motion Sensor
- Plug
- Scene
- Switch
- Temperature Sensor
- Thermostat (Single-setpoint)
- Thermostat (Dual-setpoint)
- no separate account needed. Just link your existing Amazon account.
- new virtual devices can simply be dragged onto the Node-RED canvas and will proactively be discovered by Alexa. No need to ask Alexa to discover devices.
- devices removed from the Node-RED canvas will also be removed from Alexa. Orphaned devices can also be manually removed from Alexa via the Node-RED editor.
- changes made to virtual device types and names will immediately be picked up by Alexa.
- local state changes of devices (e.g. thermostat values) get synchronized with Alexa
- secure communication with the IoT cloud through individually provisioned certificates
This node is triggered by Amazon Alexa, either through a voice command or the Alexa app,
resulting in the generation of a msg object that carries the updated device state as its
payload. This msg can be harnessed to perform practical actions, such as controlling
physical devices connected to Home Assistant. For instance, if you say, "Alexa, dim the
kitchen light to 50 percent," the emitted msg object would be as follows:
{
"topic": "home/kitchen/lights",
"metadata": { "foo": "bar"},
"payload": {
"brightness": 50,
"powerState": "ON",
"source": "alexa",
"directive": "SetBrightness",
"name": "kitchen light",
"type": "DIMMABLE_LIGHT_BULB"
}
}The node also accepts inbound messages that can be used to inform Alexa about
local device changes, which will then be reflected in the Alexa app. If the
passthrough option is enabled, this will also trigger an outbound message, just
like when the node gets invoked via Alexa. In this case payload.source is set to device instead of alexa. If the inbound message has a topic attribute, its value will be present in the outbound msg instead of the topic configured in the editor.
Please ensure that your setup does not send too many messages to Alexa. Otherwise you risk getting your account blocked.
The virtual smart home skill is available in the Amazon skill stores in the following locales:
- English (AU)
- English (CA)
- English (GB)
- English (IN)
- English (US)
- French (FR)
- German (DE)
- Italian (IT)
- Portuguese (BR)
- Spanish (ES)
- Search the skill store for the
virtual smart homeskill and enable it. - Complete the account linking process by logging in with your Amazon account credentials.
- Install the
node-red-contrib-virtual-smart-homemodule. - Place a
virtual devicenode onto the canvas and connect it to a debug node. - Double-click on the virtual device node to enter a name and select a device type. Once set up, you can use this name to control the device via Alexa.
- Configure a new
vsh-connectionby clicking the pen icon. (Only needed once for each Amazon account). - Follow the instructions to complete the account linking process. Make sure you use the same Amazon account credentials as above.
- Deploy your Node-RED flow. This will trigger your virtual device to be discovered by Alexa. You should even get a push notification via the Alexa app (if notifications are enabled).
- You should now be able to control your virtual device with your voice, e.g., by saying "Alexa, turn xxx on". Inspect the output of the connected debug node and consult the docs to do something useful.
- Once you remove virtual devices from the canvas (and redeploy your flows), those devices will also be removed from Alexa.
Detailed docs are shipped as part of the Node-RED package and available through the 'help' panel.
Example flows that illustrate the payload structure and voice invocation phrases can be imported from the Node-RED import menu (Import > Examples > node-red-contrib-virtual-smart-home). They can also be found in the examples folder.
I dedicated endless hours to this project and really hope it adds value for you! Nothing is more rewarding to me than your feedback. So if you are a happy user, please
- rate the 'virtual smart home' skill on the Alexa skill store
- rate the 'virtual smart home' Node-RED package
- mention this package in your next blog post / podcast / YouTube
THANK YOU!
New versions of VSH are frequently released and it is generally recommended to always run the latest version. The Changelog is published in the Releases section on GitHub.
-
Q: Which voice commands can I use to control my devices with Alexa?
A: Take a look at the example flows which you can import from the Node-RED import menu (Import > Examples > node-red-contrib-virtual-smart-home).
Here are some of the most often used commands:
- Alexa, switch on / off DEVICE-NAME
- Alexa, set DEVICE-NAME to X percent
- Alexa, set DEVICE-NAME to Warm white / Soft white / Daylight white / Cool white / Red / Crimson / Salmon / Orange / Gold / Yellow / Green / Turquoise / Cyan / Sky blue / Blue / Purple / Magenta / Pink / Lavender
- Alexa, open / close DEVICE-NAME
-
Q: How can I control devices in a specific room?
A: You can create rooms in the Alexa app and assign your devices to them. Create a room which groups together an Alexa device (e.g. Echo) and some virtual lights. You can then control all those lights simply by speaking "Alexa, switch off the light" into the Alexa device.
-
Q: Why do my devices suddenly fail to connect and show up as 'offline'?
A: If your device was not connected to the VSH backend for more than 30 days its certificate will be revoked. You can fix that by deleting the old connection, creating a new one and linking your virtual devices to the new one. All your devices should then get re-discovered by Alexa.
Another reason could be that you are using an outdated version of VSH. Please update to the latest version (e.g using the Node-RED palette manager).
-
Q: Why do some of my devices show up as duplicates in the Alexa app?
A: Your duplicate devices might belong to a vsh-connection that no longer exists. You can delete them manually on the connection page where they probably show up with a shaded background, indicating they belong to another vsh-connection.
-
Q: I deleted a virtual device but Alexa keeps rediscovering it!
A: You probably deleted the device in the Alexa app instead of Node-RED. Open the connection page which lists all known devices and click the trash icon next to the device you want to delete.
-
Q: Why does VSH not work offline?
A: Alexa lives in the cloud. When you ask Alexa to control one of your devices, your voice is sent to Amazon servers for processing. Amazon's servers then try to make sense of what you said and which skill to invoke. If you said "Alexa, dim the kitchen light to fifty percent!", Alexa will realize that 'kitchen light' belongs to the VSH skill and invoke the VSH backend with a 'directive' containing the command that was understood (e.g. 'SetBrightness'). The VSH skill backend then sends a message to your connected virtual device which triggers an outgoing msg object with the device state for you to make use of. This requires your VSH devices to be online.
-
Q: What do you do with my data?
A: The VSH backend only stores metadata about your configured devices needed for VSH to function and your basic profile information provided by Amazon when you enabled the skill. Neither your Amazon password nor your voice prompts or your location is ever shared with VSH. I also have no interest in analyzing your usage patterns although this would technically be possible.
-
Q: Where can I see what data is being sent to / received from the backend?
A: Activate the
Debugoption on the connection page and observe the output logged to stdout. -
Q: Can I run my own backend?
A: Yes! Check out the backend repository and follow the instructions precisely. Keep in mind that it might be cheaper and much easier to keep using the official backend.
-
Q: Is there a way to persist the state of devices across restarts of Node-RED?
A: Yes! The device state is stored as 'context' provided by Node-RED, which is kept in memory by default. You can easily change that by adding this snippet to your Node-RED's settings.js file:
contextStorage: { default: { module: "localfilesystem", }, },
-
Q: In which way is the FREE plan limited?
A: While you can use the FREE plan free of charge for as long as you want, it is currently limited to 7 virtual devices and doesn't support retrieving device state by Alexa, e.g. commands like "Alexa, what's the temperature in the living room" will fail.
-
Q: Why did a paid PRO plan get introduced?
A: With growing popularity of VSH the infrastructure costs also grew significantly. I had to make a decision to either shut VSH down or to introduce a paid plan. For 12 EUR per year, you can deploy up to 200 virtual devices and support further development of VSH. You can upgrade to the "Pro" plan from the Connection dialog within Node-RED.
-
Q: Where can I manage my VSH subscription?
A: Click the 'manage subscription' button on the vsh-connection page in Node-RED or manually log into the Stripe dashboard. This will only work when you already have purchased a subscription.
-
Q: Can you add feature X, please?
A: I'm always eager to hear your ideas! Please file a ticket.
-
Q: Where can I ask a question that hasn't been addressed yet?
A: Check out existing issues on GitHub or file a new ticket.
This package comes without any warranty. Use it, enjoy it, but all at your own risk. If you are satisfied with this project, consider upgrading to the PRO plan or buying me a coffee. Thank you!
The permitted use of the VSH package is limited to human-triggered interactions with Alexa and infrequent synchronizations of device states (e.g. for sensor data, such as thermostat). Any setup that leads to excessive data traffic between the VSH client and its backend is strictly forbidden and will lead to permanent blocking of the user's account.
Devices that have not been online for 30 days will be permanently deleted without prior warning. Their certificates will be invalidated and can no longer be used to connect virtual devices.
Accounts without any activity for 60 days will also be deleted and can no longer be used to control virtual devices.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent