This app is no longer updated. It works how it works.
My last update was 15 months ago and facing reality: Homey is developing much quicker than I can keep up. With the new release of Homey Bridge and support for TypeScript, it makes sense to start from scratch and create a new Virtual Devices v2 app that follows the latest standards.
That won’t be me, though. I have different interests. Perhaps in the future…, but no, don’t wait for that.
Feel free to take the name, the ideas and even parts of the code. In fact I would like that very much.
I can advice to create several apps:
1 App for pure Virtual Devices, supporting only the capabilities provided by Athom
1 App for sensors, with the freedom to combine multiple (sensor-)capabilities into 1 app
1 App for modes, maybe give the multi-mode a new try
Specific apps for specific request. E.g. Garage doors, Swimming pools, etc.
Thanks for all the compliments, questions, and help.
With kind regards,
Virtual Devices can simulate anything without using an actual interface. Well… of course within the limits that Homey provides.
Hi New user here. Just added the VD app, great, good job.
Also made a small donation for your effort.
I have a question if you can answer, i saw somewhere that somebody said they added there own icons to your app and loaded it onto the Homey. I get how to load the app onto Homey, but how do I add icons to the VD file?
Thanks Arjan, had a reply from Homey support and they said it is the Virtual Device App issue, not a Homey issue.
Any chance of fixing this, I find the Virtual devices great, but need them to be functional via Alexa for voice control. Happy to make a donation so you can buy one to test with, or I can order one and send it to you.
Done some more investigation myself.
So it seems that on/off plugs and lights virtual devices will work and are displayed within Alexa Smart Home Homey skill. But other VD devices such as TV, Blinds, Buttons, Virtual Modes or Multi Modes, do not.
You are right, this seems to be Homey related, as we have added Somfy RTS blinds to Homey and these do not show within Alexa either.
I’ll get in contact with Homey again and find out why or how you can add functionality for, Especially for AV (tv and receiver) and Blind support with Alexa. Blind (window coverings) support is essential for us.
Thanks Arie for you quick response.
ps if you havent tried using an Amazon Alexa you really should. A couple of these thoughout a home are amazing for voice control, intercom solution and mulitroom music control (Spotify premium account needed)
As far as I can determine Alexa does not support covers (curtains, blinds, etc). It has no class for developers to use. Until Amazon add that class Alexa can not support covers from any manufacturers. I use Tahoma and link that into Alexa but it only exposes scenes and not devices. So I have created Alexa routines for each window to call the scenes that operate the cover. E.g. a routine called “open bedroom blind” that calls the open bedroom blind scene and the same for close and then repeat for each cover.
Hi Arjan, can you make the capabilities of the sensor device setable?
I use virtual sensors to show variables from Homey-scripts in Insights. Right now I need a token/tag and a flow to get the value stored in the sensor.
I’d like to minimize the use of flows and tags to relieve my heavily overloaded Homey .
This only works for the ‘Sfeer Binnen’ device when the sun sets.
But in the morning, when the multimode is set to ‘Sunrise’ it turns ON ‘Sfeer Buiten’!?
I have no flow that does anything with ‘Sfeer Buiten’ when the mode changes to ‘Sunrise’.
I do have another flow to turn off another light at sunrise, this doesn’t work either.
All very weird stuff
I just noticed something strange in the Android (preview)-app: