Well, I am currently working on dynamic lists in AVD, so users can add lists/dropdowns which they can edit themselves.
For Home/Away/Asleep and Automatic/manual I could also add two prefilled lists.
We then also could create a default AVD for those lists and add them to the AVD templates.
Then I think we would have wat people want? Or am I missing something?
You are using the Virtual Device app I think?
Do you know Advanced Virtual Devices from the Device Capabilities app?
Is that correct, @Sanu ? I think what you’re looking for is the ability to create your own custom lists, have multiple lists per device, and add multiple virtual devices. I don’t think you’re interested in predefined or fixed lists—you’d like everything to be fully customizable.
That is precisely what I am working on 
I am using Virtual Devices, I have also used Device Capabilities, but I want something real simple to add and customize, I was never a fan of the template stuff.
Yes please 
Version 2.9.1 is currently in testing and has already been submitted for review as the next stable release.
This version greatly expands the Activities feature. Activities such as showering can now be detected and shown with useful details, including the duration, water usage in litres, and gas consumption.
You can also configure activity detection, adjust inactivity settings, and view the activity history directly in the widget.
Is it possible to change the main mode names?
At the moment, it isn’t possible to modify the main modes. However, you can create your own custom sub-modes.
I do get the feeling that this is something quite a few people would like to have. I’d like to take some time to properly think it through before deciding whether to implement it. My main goal with this app has always been to keep things as automatic as possible, so users don’t have to create lots of flows or configure lots of things themselves. I want to make sure any changes still fit that philosophy before adding them.
Maybe allow local language versions at least?
Version 3.0.0 is now available as a test release. 
This update is based on feedback and ideas from a few users, and I tried to add more flexibility while keeping the original purpose of Mode Switch in mind.
The biggest addition is the new Mode & Switch device. You can now create your own mode lists, main modes and submodes, while still using the automatic features that Mode Switch is designed for.
I also decided not to create a separate generic device app. There’s already a great app available for that, so I preferred to keep expanding Mode Switch around its original idea instead.
Another new feature is that the built-in main modes can now be renamed. The internal IDs stay exactly the same, so existing flows and automations continue to work without any changes. Only the displayed names are customized.
The Mode widget has also been updated. You can now select which Mode & Switch controller and which mode list to display, including any custom submodes you’ve created.
I hope this update gives more flexibility while keeping the app focused on what it was originally built for.
@Sanu @Paal_Aamaas would you both be willing to try the Mode Switch 3.0.0 test version?
I’m curious to hear whether the new features help with what you were looking for. If you have a chance to test it, I’d really appreciate your feedback.
Thanks! 
Hi
I have installed the test version and replaced the Mode Controller device I had with multiple Mode & Switch devices.
So far it seems good, I have multiple devices to control functions such as heating, roller shutters, heating and sensors.
Is it possible to edit a list after creating a new mode device?
Using Settings - Apps - Mode Switch - Configure, makes sense if you are using Mode Controller device, but maybe not Mode & Switch device. Maybe you could have different menues depending on this if needed?
Thanks for testing the test version!
If you open the device settings and go to Maintenance, you can reconfigure the device at any time, even after it has already been added.
Also, once you’ve added one or more Mode & Switch devices, a separate tab for those device(s) will appear in the app settings.
Hopefully this helps you further customize the device
Spot on! This solves a lot of complexity and can remove a lot of advances flows.
Thanks for the instructions where to find the settings, I see I can modify the lists there yes
I have been doing some more testing. A few things - when I select the Mode & Switch device in Homey Pro app on my mobile, there is nothing listed under flows referenced. When I replaced a previous Virtual Device it in two of my flows, it still lists that Virtual Device and not the Mode & Switch device.
Also, in Homey Developer Tools, the modes are listed as mode_1, mode_2 and so on, not the actual names. This means I have to take extra care when using those values in for example SharpTools dashboard (displayed on a tablet) where I use the values to display glow on the tile for this device (thing).
Regarding the “Actions for this device enabled” under configuration, I think for me the value of this depends on how I’m using the multi-mode device. For example for enabling or disabling motion sensors it works fine, but for other types it may not be as useful, for example heaters would have different temperature, and in my home I have different temperatures on the different heaters too depending on which rooms are in use when I’m home or away, or even working from home. In this situation I use advanced flows to control the temperature for the different scenarios and heaters, and just using the multi-mode device to show status. Same with roller shutters, as an example.
Thanks a lot for taking the time to test everything and for the detailed feedback!
I did some testing myself after reading your message. I can confirm that Advanced Flows are currently not shown under the Flows referenced section for the Mode & Switch device. However, after testing a few other apps, I noticed the same behaviour there as well. Because of that, I suspect this is actually a issue in the Homey mobile app rather than something specific to my app.
Regarding the mode names in Developer Tools: this is an intentional design choice. Internally, the modes use fixed IDs such as mode_1, mode_2, etc. The reason is that these IDs must remain stable. If the internal IDs changed when a user renamed a mode, all existing automations, flows, and integrations would immediately break. By keeping the IDs fixed and only allowing the display names to change, everything continues to work even if users rename their modes later. This is the same approach I use for the main modes in the Mode Controller, where the names can be customized while the underlying IDs remain unchanged.
Your comments about Actions for this device enabled also make perfect sense. I designed that feature mainly for users who want simple automation without creating many flows. For more advanced scenarios, like different heating temperatures per room or complex shutter logic, Advanced Flows are definitely the better solution. In those cases, the Mode & Switch device works well as a central status indicator while the actual logic stays inside your flows.
Thanks again for all your testing and suggestions. Feedback like this really helps improve the app!
I can see it depends on the device app whether or not it is displaying referenced flows in the homey pro app. I’m not sure if this is a limitation or design in the homey pro app or the app(integration), I just see that there is a difference and it would be useful that Mode Switch devices also displays referenced flows. For example it is displayed correctly when using Virtual Devices, Philips Hue, Somfy (Tahoma), Miele and many more. But not for Mode Switch or . I would say it would be interesting to dig into why there is a difference. I am guessing that if I create a support ticket to Athom they will refer me to the app developers…
If I later add or remove modes, how will I know which id belongs to the name/string? I don’t see this in the interface? Could the interface be adjusted so that I see both my name/string and the id?
Thanks!
Could you try create a brand new Advanced Flow with one of the devices that already shows referenced Advanced flows correctly (for example a Philips Hue or Virtual Device) and then check whether the new Advanced flow immediately appears under Referenced Flows for that device.
That’s exactly what I tested as well.
I created a brand new Advanced Flow with a device that normally shows referenced flows, and the Referenced Flows list was not updated. The new Advanced Flow simply didn’t appear.
I also tested replacing a device in an existing Advanced Flow. The original device continued to show that Advanced Flow under Referenced Flows, while the newly added device did not get the reference at all.
This actually matches what you mentioned earlier:
“When I replaced a previous Virtual Device in two of my flows, it still lists that Virtual Device and not the Mode & Switch device.”
So it seems the references themselves are not being synchronized correctly. That makes me think this is handled by Homey rather than something an app developer can control.
“If I later add or remove modes, how will I know which id belongs to the name/string? I don’t see this in the interface? Could the interface be adjusted so that I see both my name/string and the id?”
I’ll have a look at that after my holiday. I think it makes sense to expose the IDs somewhere, but I’d like to do it in a subtle way since I don’t expect most users will ever need them.
Hi
I created a new advanced flow using an existing Virtual Device, and the referenced flow did not immediately appear in referenced flows in the Homey Pro mobile app. If I did using Philips Hue, then yes it appeared immediately. I also tried for Miele and Somfy (Tahoma) devices, they show immediately. It seems to me that there is a difference based on device / app. The question would then be, what is the difference, why isn’t Virtual Devices and Mode Switch updated immediately in referenced flows but the others I tested are?
Yeah it would be nice with an easier way to see the mode id. The reason why I need it is because I use them outside Homey Pro - I’m using them in SharpTools dashboard, to display the mode on tiles in dashboard on tablet. I could of course find out by setting a mode active and then looking in Homey Pro Developer. If tooltip is supported, maybe that is a subtle way?
