[APP][Pro] Advanced Virtual Device (Device Capabilities App) with Unique Text Status Indicator

It is optional…


They can already.
And for most people they are fine i suppose.

But personally i want a lot more customisation, and i’m not gonna build AVDs in every app that has devices you want customised :slight_smile:
That would seem like the other way around :wink:

But i’ll create a setting in the apps so you can completly disable it (altho, if you don’t set any reflection, there is not actually anything happening.

Please note that Chronograph was already sending out the realtime messages when a timer/stopwatch/transition was updating, because it was needed in the Chronograph App Settings.

“All i did” is include it (again optionally) into DC, by listening to those realtime messages.
So you don’t need any flows anymore and can configure more parts of the AVDs in the settings with just one or two clicks.

But nobody needs to use it if the don’t want.

I personally cannot wait till i find time for myself (and a few remaining features are completed) and design a few needed AVD’s for timer-controlled-groups…

But let me solve the TEF bug on the new HP2023 first :stuck_out_tongue:


Solved, in test now: Device Capabilities | Homey

In test now:

  • Multiple Bugfixes with exporting and importing TEFs (with AVDs, flows and icons)
  • Some improvements in those parts/views.
  • Toggle’s in the App Setting (under the functions logo/button) to disable BLL and Chronograph Reflection:

When you disable one, it will be disabled directly, it will remove the listeners.
However, if you still want to save a few hunderd Kb potential memory, restart the app after disabling it (ones ofc) to make sure it was never even initialized.

(Funny to toggle Chronograph while seeing an AVD being updated with a stopwatch - and not - and again - and not…

1 Like

yes there it works TEF flow export

1 Like

Please report it if there are things not right after flows are imported, there might still be a few bugs and i didn’t spend time on the flowtokens yet.
(Flowtokens is how i find “Entities” from other apps, like find BLL Variables you have: Through it’s flowtokens.
So, those kind of entities, when importing, wil show: Create new, but no items in the select list.

The 2.10.1 TEST version can export TEFs on HP23 / fw v10.0.0-rc61 see this message:

1 Like

@Arie_J_Godschalk, @Peter_Kawa, in my 3 years with Homey, I haven’t seen any need to display the times of a timer, stopwatch or transition in the device overview, even with the original tiles of the Chronograph app. I also can’t think of a use case for extracting a time into a variable. That’s why I’d like to see a useful example sometime.

But for what?

I also support Ronny’s point. Arie, you say that such functions are optional, but still the apps become more complex and complicated to understand. And if I wanted to use a complex and complicated SmartHome system, I would switch to Home Assistant and not buy a new Homey Pro 2023… :stuck_out_tongue_winking_eye:

I want to mention that you are doing a great job Arie. And the many additional features you’ve added to your apps over the past weeks and months (probably) make sense. I just haven’t understood the point of some of the features yet. That’s the point I was asking about meaningful use cases. There is no need to reply to my post, as the features have already been explained multiple times. However, what I would like to see and understand is a meaningful use case so I can move forward.


Good point!

Perhaps you (and others) can create a (short) list of functionalities that could be considerd “Advanced”/“Complicated” and we can hide some stuff behind a “Advanced mode” toggle!?

In test now:
@fantross and @Peter_Kawa

Part two of reflection: Devices.
You can now select (multiple) devices to be reflected on an AVD field:

Does it need further explaination?

This also works for all fields:

1 Like

Okay, last update for today:
@fantross and @Peter_Kawa Here is a practical example of part2 of Reflection:
I finally have created my AVD smoke-detector (part 1).

I have created one new AVD, added one filed (for now) with Smoke Detectors, set it to reflection:devices, and selected all my smoke detectors.
Now this AVD is automaticly updated if any smoke detectors change.
This works for all types of fields.

N.b. No real new loadings or anything has been build: this just uses the existing Watch-flowcard functionality plus other existing parts of DC; thus no extra performance required.


I will also be rebuilding my grouped Lux-Sensors with this: because this has an option to automaticly exclude device-values that are older then (setable) x number of seconds, f.i. 3600 seconds old.

So, if create an AVD with lux and group a few devices together with reflection, if one LUX is not being updated, it will be automaticly excluded.
This will be very handy, because sometimes my lights don’t switch on/off, because one of the lux-sensors in the group is not working. This will solve that.


I think I get it, Arie, fiddled with it and it does what I think it should do :wink:
#daretoask Is it possible to control the grouped devices as well? If only OnOff would be possible that’ll be great.

That is a very practical idea!


Indeed, that’s part of the point.

I’ll be finishing the Reflection today, while building my own new AVDs today as real-tests.
I don’t have all day, but i still hope to finish it.

Then i can finally remove some “double” devices and turn them into signle AVDs with full control, mostly right now, my garden lux/groups.


I’m trying to make some VD’s for my curtain and Sonos (like the OT)
But when it comes on to the volume slider or curtain slider i’m getting an error:

Can someone explain what i’m doing wrong?

Decimals not filled in, but can’t select -1.

I’ve searched on the forum, but could not find an answer.

Which version of DC are you running?
And what kind of Homey?

version 2.9.29
Homey Pro 23

Please update to the latest Live version for 2023:
Device Capabilities App voor Homey | Homey

If this error is still there, let me know then :wink:

There was a bug in a version prier to the live one, but i am not sure in which it was resolved, but the issue was precisly this issue.

I’ve updated to the latest live version. But I got the same error.

Is it possible I have to use #positionreading instead of #positie? Or does that nothing to do with the error.

I have t with media and window covering.

Nope, it seems lick a bug in my code. But i am having trouble simulating it.

Please send me your TEF.:

  • Goto AVD Repair
  • Click Share Your Device (button on top).
  • Press Export
  • Click Create TEF
  • Now press Ask for Help
  • Click reply on this topic (where you then are) and press Ctrl+v / Paste-clipboard


Question about: Gordijnen

[Write your question here]




1 Like

Right, sorry, any change you can update to the test version?
TEFs had an issue on HP2023 which is resolved in 2.10.1.

The current test version is more stable, certainly for HP2023, just do not use Reflection:DEVICES yet in AVD, it’s almost done, but not yet :wink:
Device Capabilities | Homey

And then the TEF again please after update, this one is “corrupt”, not functional.