Well m8, you almost blew up my HP2023: importing the AVD took a few seconds, but the flows in the TEF took 30 seconds with all it’s variables etc …
Thanks tho, i still love this TEF for support, it does what is needed.
I, once again, have got your “old” messed up AVD including the error:
Thanks m8, resolved in the current testversion!
N.b. i do have some cleaning my variables todo after this import 
Well, but thats not accurate. You want the devices to be updated when you push the button of the AVD or set it’s value through a flowcard. You want it, to React then.
You only do not want to React, when the trigger for the React was an updated from a Reflected device.
So, i don’t agree to your suggestion, but i fully agree that my current definitions are also not clear and am thus open to suggestions.
Thanks so much, the issue was resolved in test version v2.10.18
Should I (HP2019) be afraid of slow down as per the message of @Peter_Kawa ?
Ah, okay, my bad.
Well, lets then HOOP this solution works aswell as the watcherscards on hp2023 (and ofc earlier models).
No no, i still use my hp2019 (pretty loaded) as my main. The examples and my testing is done on 2019 mainly!
Seems I am missing the easy bit 
I managed to create a VD that shows the status of my central heating with the devices I would like to see:
(yes, the images are not done yet…)
How do I set the status of the CV on the actiual VD as status and have it show JA/Nee?
Is it done here:
It insists I do a BLL calculation
Don’t use the status field, use a yes/no or button field.
After that, you can select the field as status indicator in the HOMEY MOBILE app.
Hi Arie,
It is already a Ja/Nee field,
but it is not selectable in the App:
Created a ‘button’ too, but that also is not selectable as indicator.
Set the ‘device class’ to Other I guess.
Because when it is Thermostat or Light you cannot set the status indicator on the mobile device tile
Well, just for Yes/No right now:
You have it Shown as Sensor, which cannot be selected as Status Indicator:
For yes/no, to display the field as status indicator, it needs to be some kind of alarm type:
Device Indicators and Custom Capabilities
The Homey web app and mobile app can display indicators next to the device icons. This gives users the ability to view a specific capability, such as a temperature value or battery status, at a glance. Custom boolean and number capabilities can also be shown as indicators as device indicators.
Boolean Capabilities
Boolean capabilities, also called Alarms in Homey, are displayed in two different ways if they start with the prefix alarm_. By default all capabilities with this prefix are grouped, and a warning icon is shown if the value of any of the boolean capabilities is true. Alternatively users can choose to show the indicator value of a single specific Alarm capability. The alarm_battery capabilities will show an “empty battery” icon instead of an exclamation mark.
Number Capabilities
Number capabilities, are displayed as a numeric value together with the unit of the capability. Users are able to select capabilities that start with either the prefix measure_ or meter_. The measure_battery capability will always be displayed with a custom battery icon instead of a number.
So, choose any other Show As for yes/no, and you can than choose it.
Also, but, the issue right now is using Show As Sensor, which cannot be selected.
Using Alarm (custom) or any other alarm will work (when device is other).
Thanks guys!
Not sure how to have a simple “Ja/Nee”…
Great to get help instantly!
Fijne avond 
Yeah I was also thinking maybe it is possible to use string values Yes/No or True/False or even 1/0 as status indicator
I think it can be realized when the BLL expression is optional, Arie?
Just a brainfart
Simple yes no is not possible yet for status indicator.
@Emile has responded to the status indicator petition and had a nice idea.
Unfortuantly, the next day i had a very bad moment and reaction, so, im not sure if that idea is still planned.
If so (text fields as status indicator), than the options for Yes/no aswell as text indicators, will be implemented asap.
Please note tho, like Peter said.
You can add an onoff button, create flowcards to true, and now set the device class to something.
This will create an unique mandatory status indicator per class type.
Yes, this kinda stuff is indeed why the BLL expressions exists. However, the currently only way to show text on the device tile, is the “units” i use for the special first status indicator. But currently, the reflection for that only works for the number part of the status indicator.
I can add support for the text part, or better yet, change the status indicator to target the text part instead of the number it now does.
But to be honest, if Emile still plans to allow text fields to be chosen as Status Indicator, than the best thing would be to support that, and drop (or hide with new AVDs to keep existing AVDs working ofc.) the Status indicator from the AVD settings).
Hey Arie,
thanks for the great reflection feature. I only missed the option to reflect a homey variable.
Maybe you could also implement that.
Thanks for your great work!
Sure, please create a feature request tho, so it won’t be forgotten
Thanks!
Hi @Arie_J_Godschalk ,
I’m trying to figure out why my HP2023 is constantly crashing (not blaming your app), going trough all the containers logs and I found these… anything you can address or it was due to eventually Homey not ready ? It appears in logs hundret times possibly… thank you.
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: 2023-03-23T23:05:54.466Z Homey [err][ManagerFlow] HomeyErrorNotFound: Not Found: FlowCardTrigger with ID homey:app:nl.qluster-it.DeviceCapabilities:trigger_app_device_available
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at ManagerDatabase.findEntry (file:///app/lib/ManagerDatabase.mjs:56:15)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at Function.findEntry (/node_modules/@athombv/homey-core/lib/DatabaseEntry.js:198:19)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at AdvancedFlow.runTriggers (/node_modules/@athombv/homey-core/lib/AdvancedFlow.js:643:28)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at AdvancedFlow.run (/node_modules/@athombv/homey-core/lib/AdvancedFlow.js:363:61)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at /node_modules/@athombv/homey-core/lib/ManagerFlow.js:847:9
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at async Promise.all (index 1)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at ManagerFlow.triggerFlows (/node_modules/@athombv/homey-core/lib/ManagerFlow.js:839:5) {
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: statusCode: 404
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: }
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: 2023-03-23T23:05:54.468Z Homey [err][ManagerFlow] HomeyErrorNotFound: Not Found: FlowCardTrigger with ID homey:app:nl.qluster-it.DeviceCapabilities:trigger_app_device_available
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at ManagerDatabase.findEntry (file:///app/lib/ManagerDatabase.mjs:56:15)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at Function.findEntry (/node_modules/@athombv/homey-core/lib/DatabaseEntry.js:198:19)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at AdvancedFlow.runTriggers (/node_modules/@athombv/homey-core/lib/AdvancedFlow.js:643:28)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at AdvancedFlow.run (/node_modules/@athombv/homey-core/lib/AdvancedFlow.js:363:61)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at /node_modules/@athombv/homey-core/lib/ManagerFlow.js:847:9
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at async Promise.all (index 2)
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: at ManagerFlow.triggerFlows (/node_modules/@athombv/homey-core/lib/ManagerFlow.js:839:5) {
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: statusCode: 404
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: }
Mar 23 23:05:54 homey-6405cb261f19900b82ed4326 homey-pro[1165]: 2023-03-23T23:05:54.482Z Homey [err][ManagerFlow] HomeyErrorNotFound: Not Found: FlowCardTrigger with ID homey:app:nl.qluster-it.DeviceCapabilities:trigger_app_device_available
And also…
Memory cgroup out of memory: Killed process 3209 (node:nl.qlust) total-vm:376660kB, anon-rss:97148kB, file-rss:8676kB, shmem-rss:0kB, UID:0 pgtables:400kB oom_score_adj:0
Yeah, this seems to be outside of the scope of the app itself. This is not my coding, but Homeys, and it cannot serieously be broken, thus, i would personally put this under random and not even report it unless it happens again with sufficient power.
Im pretty sure the flowcard exists
