Hmm…I was still on the latest live version 
So I updated to the test version. Restarted the Device Capabilities and BLL apps as well as
Homey itself (just to be sure). However, the issue remains.
I tried changing the BLL variables in the repair screen of the AVD, but after I save the changes, the names of those vaiables shift to another one in the list. The AVD itself keeps displaying data from the correct variables.
You have to restart CD after each change to get the correct names
As indicated, I have restarted the Device Capabilities (and BLL) app several times after making changes, which did not solve the issue.
I seem to have found a solution:
Apologies that this is probably a newbie question, although I have spent quite a bit of time searching for answers in this forum and elsewhere.
I am using HP 2023 12.2.1 & wanted to create a virtual device that could be used to store electricity kWh consumption values from an external API using Homeyscript and display using Insights.
I started with the Virtual Device app to create a senor \ power meter device. I could set a value using a flow but when I used device.setCapabilityValue in Homeyscript I was getting a ‘Capability Not Setable’ error.
I then switched to using this Device Capabilities app, added a sensor device class and a number field to show as Energy (Sensor) but got the same error when trying to set a value.
I experimented with a couple of different number fields and when I look at these in the Homey Developer Tools app can see that any of the built in energy/power sensors are read-only whilst a Sensor (default) can be set.
However what puzzles me is if the built in/predefined energy/power sensor capabilities are read-only, how is it then possible to set them via a flow and via the creation of custom devices?
Setable means that you as a user can set it.
But ofc the value is setable through the device/app itself (else it would mever have a value).
You could use homeyscript to set the value through the API or emulate a flowcard to set the value.
Thanks for the really quick response.
As noted, I am trying to set the value via HomeyScript and it doesnt work.
I modified the sample printSensorValues script as shown below:
The following worked 
thanks for the pointer.
It would be awsome if i could set the cumulative property also for meter_power, meter_gas and meter_water. Then it would be possible to create a virtual smart meter that could be used with homey energy, see Energy | Homey Apps SDK
I am getting this error from today after pressing one of my buttons. Has anything changed with the app?
Hi @Tirrazo
I am in contact with developer of the app. I have the same issue. Maybe it is the app but it could also be the update of the mobile app. Keep you posted.
Rogier
Hi,
Thank you for the information.
Awaiting response from you
Longshot: does restarting the BLL app help?
I can’t reproduce the ‘press button’ error, but the settings screen of random devices were fully empty. BLL restart solved it.
(Homey app: Jan. 14 Android beta update 9.1.0.1653)
No, the app has not changed.
Hi @Peter_Kawa
I feel kind of stupid… what is the BLL app?
What could be the issue?
No I wasn’t clear, I meant this app, which is a great “plugin” for advanced virtual devices (in this case):
https://homey.app/en-nl/app/net.i-dev.betterlogic/Better-Logic-Library/
Different app, same error (after an update fw to v12.3.0)
If Arie did not update these apps… it most prob is Homey firmware related.
It’s probably Pro 23 only.
Love your work Arie 
Somehow I don’t understand the “Get flows…etc” card.
I cannot figure out what I am doing wrong.
Working example with a text and wildcard (*)
Using the same example, but now using a Tag, does not work:
Another example using a wildcard looking for ‘Solar’. While I do have a BLL variable named Solar Opwekking:
Using the tag Solar Opwekking, also does not work:
Likely I misunderstand, but cannot figure out what.
And; what does ‘plat’ yes/no do…?
I am just trying to find out what flow is using a certain variable, so if there is another / better way, I am open for suggestions 
@Arie_J_Godschalk Any thoughts on that?
@Sprotte Jep, its coming.
THX
