Did some initial testing last night, truly freestyle
Need to figure out from other chat how to create " Advanced Virtual Devices"-template as did not find how-to do device-copy-paste easily (as newbee every corner takes its toll )
I have no clue what you mean here.
However, when you create a new virtual device, there is an option to create a field that reflects the value of a field of another device. And you can use a formula how this value is converted in the value you want.
Maybe that is what you want?
Could we have a heating controller device where we can have modes such as Away, Home and Night? Similar to virtual device - home alarm except different text. It would make it very easy to select from the Homey app, and the user does not have to consider temperatures as they would be preset in flows. Thanks.
I think itâs best to move over to the Advanced Virtual Device for this one. There several picker lists, and you can even request your own custom list
The list youâd like is already present by the way:
Indeed, the VD app only creates default Homey devices, very easy in use, very simple, but low customisation.
However, for more advanced customization. Ise the Advanced Virtual Devices from the Device Capabilities app.
Those are way more complex, advanced and customisable.
I use virtual device (alarm state) to control my alarm flow.
This morning, with the server issue, I wasnât able to control this device. Others virtual devices (buttons, counters, âŠ) worked well, but alarm state, no possibility to change this state.
Do you know why?
Another thing: I could control this state with my specific flow (using a z-wave remote that change this state). But not directly in the app. This was the only virtual device didnât worked.
I have a virtual sensor device for the main power meter in my house. The virtual device has three capabilities: âpowerâ, âpower meterâ and âvoltageâ. These values are updated from MQTT messages in a flow, and it works just fine.
I recently migrated from a Homey 2019 to a 2023, and all of this migrated fine, and kept working on the new Homey.
The Insights for this virtual device has four graphs: âEnergyâ, âPowerâ, âPower usageâ and âVoltageâ. On the old Homey (i.e before the migration) the âPowerâ and âPower usageâ was exactly the same. However, after the migration I can see that âPowerâ has now become a static value, while âPower usageâ still varies according to the actual power used in the house (i.e the values sent to the VD in my flow). Hereâs a snapshot of how this now looks:
Hi. Been using the Modes for a year or so. But suddenly the modes started switching status after the Homey restarts. After removing and adding new Modes all switch on after restart, also tries to deactivate all flows connected. What might be the problem? Could this be connected to me switching WIFI connection on my Homey?
Well, nothing is changed in the app itself.
So either the value is changed through flows, or homey has a bug in it?
Im not sure, i personally cannot simulate this issue.
Hmm, that could be it, but why havenât they mentioned this in their changelog if so?
I just checked, and the âPowerâ Insight is indeed stuck at whatever value it had on my old Homey before the migration also for other devices.
The next question then becomes why hasnât it been removed altogether? Leaving it as a static value isnât a good idea. I really donât want to see completely useless insights.