Question, I try to move an advance flow from a Homey 2023 to a Homey 2019. But I get stuck in the WEB API with an error:
I use export on the 2023 and get a TEF.
I import the TEF in Device Capabilities on the Homey 2019 and I get the code to import in the Web API. and then it goes wrong.
"root":{1 item
"error":string"Cannot read properties of undefined (reading 'split')"
}
I tried to change a function, which I use in one of my devices. It was not there anymore in the function list, but it is still working.
So I recreated it with the changes I need. But it does not output a value even though it gives the correct result, when I test it in VSCode with nodejs. Even renaming the new function and using this does not give a result. Instead the $value (which is the input of the function) is displayed.
Can anyone help with this, please?
I tried a bug report on Bitbucket, but got no response. I also sent a bug report: 53dfc5ac-fbee-4471-9b75-4b77b5d09fbd
Does anybody experienced âlost propertiesâ issue after a restart?
My Homey was unplugged for almost 8 hours because of an electricity maintenance. When it went online again one of my AVD device which was a button and a chronograph timer on that it lost these capabilities.
Now I restarted the app AVD and Chronograph and Homey as well but Iâm unable to remap the chronograph timer. If I select the correct timer and click save it happens nothing.
Iâve checked the timer it started.
Iâve created a diagnostic report if it matters. 2517f61c-2bb1-43b6-a384-cbce083618e4
It does not fire off automatically, although the Tado Geo does, but the icon of the advanced device does not change (I checked with a notification behind the tado geo, and that I do receive.
strangely enough if I start the tado manually, then the icon of the AD does changeâŠ
I am running into the strange issue in the settings/repair screen of some advanced virtual devices. For some fields, when the value is a reflection of a BLL variable, the selected/displayed BLL variable changes to another BLL variable, though the actually used variable is the correct one. This occurs both in text based and boolean based fields.
As an example. The virtual device contains a text field called âStatusâ. The value of this Status field is based on BLL variable âbllWTWStatusâ, which is a string.
When I select that BLL variable from the list of BLL variables the settings screen shows the correct selected item. However, after I save the settings (Save device button), the selected item is changed to another BLL variable: âbllWTWKoelenâ in this example, which is a boolean.
Also if I close the settings/repair screen and open it again, the indicated BLL variable name is the incorrect one (âbllWTWKoelenâ instead of âbllWTWStatusâ).
The strange thing is however, that the Status field is actually populated based on the correct BLL-variable: âbllWTWStatusâ.
So there seems to be a glicht in the user interface of the settings/repair screen.
I have already tried to restart both the Device Capabilities and BLL apps, as well as my Homey Pro 2023, to no avail.
Is it possible to achieve the following with DC app: create a device composed of multiple Homey devices, but when I click on the device tile to see the detail, it would only show me devices that meet a defined criteria (the ones in red in the image below).
Iâm trying to create an DC device for my door / window sensors, and would like to show only the ones that correspond to an open door / window.
If itâs not possible (this may not be in line with the very logic of DC app), maybe at least I could order the list of devices based on the value (to show at the top of the list the open ones)
EDIT: I understand from @SunBeech displaying values in a list is not currently possible with DC app: @Arie_J_Godschalk : is this something you would consider adding to the app or do you not see the value?
What I have in mind something similar to the climate button:
when opening the device I get a list of all windows / doors with their status (open = yes / closed = no). The open ones show up in red, which makes it quite easy to spot in the long list (I have 27 doors / windows)
It works really well for me and iâm happy with the solution.
Here is how I have achieved this if anyone wants to find some inspiration
1°) Using a YES/NO field, I have created a âsummaryâ device, grouping all my doors and windows. It is important to select "show as: alarm (custom)
they all have the same setup, just linked to a different device (door / window sensor)
Et voilĂ !
This is my firsy real use case with Advanced Device Capabilities app and I am amazed with the possibilities.
Thanks @Arie_J_Godschalk for your great work. Could you provide the link again for donation please?
Hi and thanks for a super app. I do run into some problems. Today I have approx. 140 pieces virtual devices. Most of them holding fields that are set from flows, some are picking up information from other devices when they are updating. The problem is that DC are running just below 130 mb in memory RSS on my 2023 Homey. So my question is how to lower the memory use of DC without deleting any DC devices ?
I donât know whatâs consuming memory in each device, anyoneâŠ
The app is quite memory heavy when you have large(r) numbers of AVDâs;
140 is quite a number of AVDâs you have there.
Out of curiousity, did you actually count them, or was the last one named âadvanced virtual device 140â? (that number just keeps incrementing, even if you delete AVDâs on the way).
The number of AVDâs affects the memory usage:
Pro 2019 #1 (apps should use less than 40MB)
60 AVDâs: 55MB
I have the test version installed. And I didnât count them just looked at the last name. But I have a lot. Most of them are connected to energy meters like the Shelly 3 pros and covering 3 different buildings and several energy measure points. Also several preset devices for LED RGBW drivers. I really like this app but it looks like Iâm hitting the roof. Do we know if there is any new version coming out ?
Heu @Sharkys ,
Just to reassure, yes, im âjust busyâ. Have been sick, which made me fall behind on work stuff.
I do hope to have some time aroud the holidays and january to put time in Homey again.
I also have chosen to wait a bit so Homey2023 would be more stable and the homey-api is (more) fixed. Else i can keep programming without real effect.
No, not really.
The difference between test en live version is the homey-api instead of the athom-api.
The DC app itself is not really different, creating an AVD is not different.
You can switch between the test and live version without issues.
Thank you Arie for letting us know Fingers crossed that all will be fine.
Yes but Iâm using it since beginning so itâs hard to say but at this moment, DC app is force stopped by Homey multiple times in hour, however true is that I start utilizing DC more and more over last year so itâs hard to say.
So is there any difference in memory use in AVD considering if the AVD consists of ex. a on/off button or one AVD with several numeric fields that getting there data from âreflectâ other devices ?
Or is it only the amount of AVDÂŽs
I allo discovered that if you donât check the field âInsightâ if you create a number field, the homey makes the insight anyhow but without any name just the kind ex. energy .
.
