You mean the firmware update broke native Homey virtual devices as well?
The same error appears with advanced virtual device as well
Yes, the exact same for me after the latest update of Homey.
You guys should report to homey.app/support about getting the same error with virtual devices of 2 different apps and those from experiments.
2 Likes
Yes Peter, It broke both my Virtual Devices app buttons and Homey native virtual device buttons. Fault appeared via firmware 12.3.0 a week ago. Making a new virtual devices for a replaceces does not solve the problem. Neither booting Homey.
I have for example an advanced flow where a virtual button is one starter and several physical devices too. All connected with “Any” card. Every physical device (buttons, movement detector etc.) starts the flow fine but virtual device will return such error. Randomly, but just rarely, virtual device may work without issue.
Reported
I have exactly the same problem. When I press long on the virtual device, a button appears. If I press that, everythijg works as expected. But not if I press the tile like I normally would. @Raita_Kallio did you hear enything yet from your report?
So, I did some testing, the error only effects the “virtuele knop” from the homey experiments.
See picture
And the “apparaat” button in the community app.
See picture
The rest seems to work, does somebody know a solution?
Hello,
Thank you for this app!
Is there any plans to add a device class for Home batteries? Energy | Homey Apps SDK
I’m already using this app to create a VD for my solar panels to work with the new Energy tab, but would like to create a sepate device for my battery.
Thank you in advance.
/Alfred
Yes, @Evert_Dirksen the reply was:
“Thank you for reaching out to our support and for bringing this issue to my attention! Our apologies for the inconvenience. This issue has also been reported by other Homey users. Our development team is aware of the situation and they are very busy at the moment to find a solution and to fix this issue”
There was shared a new firmware (12.3.1) 6 days ago and seems the issue has disappeared now 
