Perhaps restart DC one time?
I jist tested the flowcard, and for me it was working. And my homey is quite up2date i believe.
I recreated the two cards and then they work. Strange… ![]()
I did make some changes to that AVD some time ago. I believe I activated the ‘create real fields’ setting. Maybe that action impacted existing flowcards.
Yes, when selecting that Checkbox, the actual capability type changes.
And that flowcard is a generic DC card, which watches the capabilities of devices. Its not a specific AVD card: it doesnt know about Numberfield1 and 2 and so on. It just sees any devices and their capabilities.
So changing that checkbox would have required you to reselect the correct capability indeed.
Perhaps i should build an AVD specific sustained-flowcard, altho its hardly not required anymore with the Homey default flowcards (only on HP16 en HP19).
Ah, that makes sense. It was my own fault
.
Your version of the sustained values cards still has one key benefit over the Homey built-in ones: you can indicate the mode: execute only once vs. continue executing while the condition is true. I actually use that quite often (e.g. to keep sending alerts in case a water sensor detects a leak).
Homey’s built-in cards execute only once. The condition needs to change and re-occur again before those cards trigger again.
Yes, ill keep writing my licence for Athom ![]()
![]()
I sometimes use the ‘Get flows containing’ card to generate a complete list of flows that use a specific device (based on its ID). It’s a really handy feature, especially when the device’s tags are used in a condition (Homey misses these in the standard flow-tab (app), or right-click → flows)
However, I recently noticed that some flows were missing from the list—specifically the flows where the device is used with simple built-in trigger cards (e.g., “when turned on/off”) or actions (“Turn on/off”).
Is this intended?
These flows do turn up in the Homey flow-tab of the device, but that view doesn’t include instances where the device is used as a tag.
I now use both the flow-tab and the ‘Get flows containing’-card for a complete picture, so not really a problem, but a complete JSON overview is more convenient to work with.
Nope, it certainly isn’t, the card (and script) really is ment to find any and all references to devices (or apps, zones or variables).
I will have a look and fix it.
However, I’ve been developing and updating the DC app for days now, and when its done its gonne stay in Test for a moment before rolling it out the production version.
Could you send me this post (plus what homey you use and perhaps include a flow that contained a card that couldn’t be found + the name/id what you searched for) in a PM for me?
(The issues/tickets of bitbucket has been removed and i havent found a good alternative yet).
Thanks!
You can alt-click in my.homey.app on a flow to copy it.
@Drako74 @Leeuwhoofd I did this by analyzing a log file of the dryer’s power consumption. During part of the drying cycle, there’s a 30-second period when the dryer isn’t doing anything—its power consumption was below 15W. After these 30 seconds, it takes another 9 minutes before it’s finished.
Then the anti-wrinkle function starts, which lasts about an hour.
So I measured the 30-second period when power consumption is below 15W, followed by a 9-minute timer.
It’s here!
Sorting of fields!
It took some time, but it’s here. You can now freely change the order of fields, the order in which they appear in the device.
This is done in a separate “view”, not in the main repear, but one more click away:
(Sort Fields)
The reason its been done in a separate view: So you can order based on where it is shown in the Device. For instance, you can have Texts, Numbers and Yes/No’s all on the Sensor tab of your device. By doing it this way, you can actually sort those different fieldtypes just how you want it, f.i.:
Here i repeat a Textfield, then a Yes/No field and after that a Number field.
This is shown in the Device like this:
Have fun y’all!
Other updates in this version:
- Fields can now be ordered/sorted.
- Numbers decimals, steps, min and max has been synced with each other.
- When decimals are filled, steps need to be in those decimals, and min and max also.
- Min can be filled in freely, but max is dependend on the min+step(s).
- When changing a fieldname, the settings are not reset anymore (because for a second the fieldname became empty).
- Some small UI and UX changes.
- Some bugfixes.
It’s in test now:
Oh and @Rrrr : removing a field, like number4, will not remove number5 and so forth.
You are the best!
Version 3.0.0 is in test now
Next to the above mentioned improvements, the DC app has some new images and icons.
Device Capabilities app image and icon
AVD image and icon
Want to support development more?
Become a Patreon at Arie J. Godschalk | Membership | Patreon
i am using the test channel and i am not able to edit my Devices, i can only sort the fields. Has this menue moved elsewhere?
Which version do you have installed?
Can you send me the TEF?
(Click on Offne Teile Dein Gerat and then export (without the flows is fine)) and send me the TEF?
And are you creating a new device or changing an existing AVD?
and can you send me a diagnostic?
Exciting one,
[tef:AVD:"H4sIAAAAAAACA6XW2Y6jOBQA0F8ZoXlLITazRZoHlpCQPWTPaNQyYJaELbYJSVr976NUVVd1V1dHGQ0PRuL6XuyDbfGVCdEpDZAblAXTZnqAuMbLZRmCsBRFNfDiq54FPTEPkGYrUdM97BXJ5JpcdcRiZuOJm4T+VeHKoWfyC8Ut94tDOgkudSGpyATRRtbqQtC5XqxpqBePsTYFrc2wpRdbLeplHMep6jWQsoD0HG2K960l3LWQTwGXNSF30kEkDZHdIC6b98SJsdjV+9j1zU6QS/1eER/QKGuGjmyb3dN60NmXh445VkTiikOSjLe7+Lyy3cuxu7WTTTnDZnw8mtuEt/PJYSRsPTAty0bWaWJUBiU26QbKZdHsluNEjGi1d82uuj4k2YlLbJffXqu0apoL4fMrAcOzsrQ3J9yTV8LCNK/eZDFbo6lcLWYlsrLV1BitrTJZ1ROYnr0FosL+MO84nWV3e9oIXBF73pGrr3Ozo1vhrOiusXPO9rMGXy6OviC7TTNfT/db0KitIyl0C7T6YH/1rhW2x/O9sTtO4oFYWMKqXFw8JTNI7Zh9shzJZ4jXQj7g3eMlh9zxelg6u9Gyv9+OaOV23FRACIXXlmKuN9NR/5rE+gEK5Vya0wYtObJC2cxLgwMHKFDmenzIvLKcL8/HwaVbSV4yjOfTbniFsWQVDj5cMzSPw2JiTrL84o2SquMMDcGPlInWlWhyquHZlmHfOGZmWuet5WSxyjROdcYtlTct6qBBR3TV6NrvU3ujm6PcKC0y6+8Glt50cTzobqFQeF7YlYJqp8YFX0864agH7XJ+9EW1Dl2y0rbGcTUR07Euj0/xNh/HxYDfbXGALXGZ1s5pTKJzv7MDEsZRuj20WnJ3DJMAKC19vMO543i7jYCKGdzopY05qlrcUi6khOttBG4qo+l+fB55fKTMokhuRfsSFXslPGHQmiZyrYqccpKmvE0OeDOvRh3DMP5inpigJrTMb3uLMO2v356YEqdxWsDMDZk2o0YaEBDQWBSAkAW8LrO6pIosQJHAQ0mPIklnnhiCKE2L+FaBQQXC8eXLCWY1+nIrS2FBmXZRZ9kTU9S5j/AkWqAzdVKUhYRp8++Px8/37wH5PWCWZYZg8UmKWVNafhawYI4w/CQwTMmP7w4ywrSZBlKEE3Rrme9dhTHMEdNmHFwW9I+Jj4r3kIeiDAXUfj6ZCNP++yvz558JJMkAXZg2U/p7FNC2CnjmiUlvkqGmSUhRVTbSRI0Fih+xfiQDVpUCWVCgpAeKzDwxFS4rhOmtRo4gqTH6QlFeIQxpjRHz7Z+3EcxRBTGkyIIV9NMspeltHBHMCHrvk5SNQX5T662XhW/zdrKysSC+qVBco48zvU0haIev8/2Q6xYkjRP6IVV89eulBUXFz4DiY4CCDKTvgrzPa4IAVVYKfMgCRddYTUYBC0WgyirPyzwA/0VQfEBQfEhQvCso3hUU7wlKPwsub+1bpvQYofjC8rIIVR/osiayCOk6CyIpYmGkQ1YPQKirvCRokv9fCKUHCKWHCKW7hNJdQulzwpeDyKrzOoM0PaEP4wKvtkOUEloX8Vs58KAreN6wz64QAQnqoc8KUSCyQNBE1vdDlZVVTVF9XtcB+s3SrMoG4R9EwQOi4BfRlypv8buW4K4luLcc5Veyzk02ff948oNiGi/9HzGK8C9e8gNe8g9e7zXeone15LtacufDGnPzqsQUhR+KfIb67en1v/YVdQ1x3kBCECYVSoPkeYiQaf/9z7d/ATA1OCcCCwAA":/tef]
diagnostic: 501ae020-f5e0-4820-b1e9-ab764b5b9df9
installed auto update 3.0.3 amd now i can’t modify my virtual devices anymore…







