The Virtual Devices App has just been transfered to me by @Arie_Laxed
That means:
It will be updated to SDK3.
Sourcecode will me moved over to BitBucket where a new issue/support-ticket-system wil be started.
I will (try to) work through the current issue list from GitHub, after SDK3 is done.
Now that the sourceode and VD app is in my control, i want to add a feature, based on the AVDâs:
The ability to change a custom device icon after creation.
Any VD with a custom icon that was uploaded while creating the VD, can be altered after creation, just like with the AVDs.
Unfortuantly, this cannot be done with items picked from the default icons during device creation.
I might change this for new VDs in the same way as with AVDs: wether you pick one from the defaults or upload a custom icon, you will be able to change it after creation.
(Possibly) a Integration or Migration tool between AVD and VDâs.
Like @Arie_Laxed says in this Main Topic Post: The VD sourceode is âoutdatedâ and perhaps the VD app should be refreshed. He advices to create several, more specific Apps.
But that has already been done:
The Advanced Virtual Devices from the Device Capabilities App is a fully customisable virtual device, which you can complete configure yourself.
While the VD app is, in itâs core, more focused on Default âAthomâ capabilities and extending those features.
That means that some users with VDs might be better surved with AVDs and vice versa.
And since the AVD (DC App) has the functionalities of the Share Your Device! - Advanced Virtual Devices from Device Capabilities - Apps (SYD) and the The Flow Exchange(r) - Exchange Your Flows with Others! (TFE), there might be some excellent ways the apps can work together, synchronise and/or migrate between them.
Well this is just a start, currently i am starting of with setting up the develop environment, sourcecontrol, stuff like that. Then iâll work on SDK3.
Yes, but I use only some light switches for on/off, thatâs all.
And Iâm in the process of creating these devices with ADC to reduce the number of apps I have.
So you are the perfect testuser?
If it breaks, you convert them?
Nah, you can always switch back to the live version, i didnât change anything about devices or something like that. No migrations to the new version.
Do you mean AVD from DC app? Or is there another VD app?
I am gonna change the topic a bit, This is a reminder message:
This is the Old Topic Post up until i, @Arie_J_Godschalk took over on 26-10-2022.
Important Note:
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,
Arjan
Virtual Devices can simulate anything without using an actual interface. Well⌠of course within the limits that Homey provides.
What is the difference between this app and Advanced Virtual Devices? Basically both do the exact same thing, with the latter of course, having much more customization options. But i like the purple color so much in my advanced flows
Edit: Also this app uses about a third of the memory that Advanced Virtual Devices uses. Makes sense because this one is more lightweight, but you get it haha
This app is extremly lightweight, few hundreds kB in install size and mostly runs wel below 10MB in memory size.
It letâs you create a Virtual Default(!) Class/Type-Of Device.
You can create a device, need to select a class (âotherâ is not an option(!)) and from that class you can select which default Homey capabilities (fields in AVD) you want to have on this VD.
What you now get is in accordance with itâs name: a Virtual Device.
You can pick/upload a custom icon for the device itself during creation.
Very easy to use: absolutly no customisation or settings needed after device creation.
Al(most all) based on default Homey flowcards.
The Advanced Virtual Devices from Device Capabilities
The install size is about average to large, with al itâs default iconâs compressed/zipped in it, with currently 6MB. Memorywise it runs normally between 23MB and 30MB, but depending on your Homey and when you create AVDs or use Share Your Device or The Flow Exchange(r) you can easily get up to 50 or 60 MB of memory.
So for a default VD, the AVD and DC is a big overkill imho.
It letâs you create a Virtual Completly-To-Your-Wishes Device.
You can set the class to any type, including other, making it not visible on certain other apps and software. You can do this after creation.
You can add the same capabilities/fields multiple times.
This means you can have one AVD controlling multiple real device through separate UI controls (like buttons). Take this AVD Template for example: Control 2 dimmable lights as one. It letâs you control two real dimable lights through one AVD, but the AVD actually has a totla of three buttons (not possible with VD).
Or this more extensive Living room example. Here you have 3 neat looking custom-iconed buttons, with custom names and everything. These custom names also show up in flows, making it very readable.
I have actually added a few thing to my Living Room AVD, like the curtains and Sonos. All Living room devices within one(!) AVD. This kind of stuff is not possible with VD.
AVDs can have as many fields as you would like. Except for Homey, browser, javascript, max-number-length, etc., limitations, there are now App limitations to how many fields you can have.
You can add fields like Camera, multiple times, so you can put all cameraâs in one AVD. Much more handy then a lott of devices in on âRoomâ.
You can create your own capabilities (fields), not just pick from the default Homey types.
All default types can be used, but you can also pick a lott of other options or just set every field-option yourself. Create a Tag or insight, give the field a Name or Icon, SHow it or Hide it, Make it pushable or not. A lot can be customised.
You can now even add default lists/pickers and a few default-custom lists. (And you can request to add your own custom picker/lists to the DC app).
You can customise the Device icon but also the Field icons (Buttons, Sensor, etc.) after the creation of the device.
You can pretty much reconfigure your whole AVD after creation!
Being able to create this Control 2 dimmable lights as one AVD is Unique!
There is no other way then AVD to create one virtual device to emulate multiple devices in one.
Being able to create an (A)VD and Share Your Device including flows with another user is Unique!
Even Athom doesnât have a method for this
Being able to import a AVD from someone else and have the flows configured to your own devices is Unique!
As soon as SYD and TFE becomes more well known and people start trusting and using it, this will be a very handy tool for helping others and newcomers!
I know you should create most of your own flows to start understanding it all, but be real, why keep inventing the wheel over and over and over? Why would i need to explain to @fantross HowTo make the AVD and itâs flows, while explaining it will take me longer then creating it (if i want the images i already need to create everything first) then to just give it all to him: The AVD and Flows. And now he doesnât need to really configure much, so less change at a mistake (since else he would need to create everything based on my print-screens and explanation).
So, i really like VD and itâs simplicity.
And i donât think AVDs are gonne surpase it and iâm not sure it should.
VD is very easy to use, very handy for a lot of users.
But VD âonlyâ letâs you âpick a (limited) default Homey Deviceâ.
But:
AVD letâs you create your own device, the way you like it, with all the fields you need and the icons you prefer!
Also, AVD was build out of the need from a user to be able to set a Text on a Device Tile in the Homey/Web App:
From that, AVD (and DC) has grown very fast into a completly Unique App, there is no other App like it.
And yes, it does many things that other Apps do in some way or another, like VD but also like Better Logic: Add fields to an AVD and put the Tag and Insights On, and you have got about hte same thing, only now your variables are grouped together and you can have Image-variables.
But i donât know about any App being able to simulate what AVDâs can do.
Yeah, the skills i have in developing, i lack in design
And DC was never intended to grow like it now has/is, i didnât put the effort in to ask for a design back then.
And for about 1,5 year there were only 150 users, so i guess that was fine.
But since AVD itâs been multipling like crazy, so i might actually need to rethink the design and ask @johan_bendz if he has any good sugestions for the images, icons and color.
