I get an error on control two dimmable lights as on when React to changes on the real devices and set the AVD Dim to average.
Created a new one to test if I had a wrong setting but the new created avd has the same error.
Ah I see! The function name should not be renamed by itself though.
The other day I switched several times from EN - NL - FR - EN, but my function names were not renamed/translated
So not sure if it’s app related…
What could’ve happened is when Homey is set to EN and your web app was translated by the browser to Dutch.
That can result in unwanted translations (when you hit save after edit).
Question/Request : Can this PLEASE all be done with/by this app without "GRANTING FULL ACCESS/CONTROL of the whole Homey (Pro). Its a matter of privacy / security (& peace of mind for some users.) . Also people which use any kinds of security app/alarm app like e.g. “Woonveilig/HeimDall/ Yale Doorman” etc. could be seen as negligent when somebody breaks in their house and their security system is connected to a insecure device granting full access to their (smart) home to unknown sources/people. A dream come true for every insurance company (not Having to pay any insurance claim).
Please Don’t take this personal. NOT AT ALL. I am suspicious/cautions in general.
No worries, i fully anderstand the feeling.
But indeed, as @robertklep said, it’s just not possible.
Well, you cannot use Homey as a real security system with insurence, homey is a non-real-security system.
You can do amasing things with the apps like Heimdall, but i trully hope you are not using Homey as the basis voor your real security, since almost Everything is with wireless signals, thus, (very) easy to interupt!
But that’s just my opinion.
I have security systems and camera’s around my house, but the basis of the alarm system is independend of Homey.
Homey is just an addition for it, but without Homey, the basis of my alarms will still work fully and Homey only has some sensor input, can read stuff. Homey cannot open my doors directly or influence the real alarm system.
@DaneedeKruyff or is Heimdall really capable of more?
(Sorry i dont use Heimdall (yet), so im not sure of its capabilities)
But using Homey as the basis for real alarms etc. doesn’t feel right to me.
Can you somehow link it also to a Homey standard logic variable too, like you can do to a BLL variable please .
its because the current value/state of a BLL variable doesn’t survive a Homey crash/restart/powerloss and a Home standard logic variable does.
And I would like to keep for exmaple the Whisper/DND Mode the same after this kind of things ↑ happen.
What do you mean? On a non-bugging Homey, BLL variables ARE saved through reboots, yes!
And, even if i change it to a Homey variable, the permission is still needed, because i can only publish one version of the app, with or without. And becuase others do need it, i than still cannot remove the permission.
If your BLL variables get cleared at reboot, please create an support ticket, because that’s not suppose to happen.
But, yeah, implementing Homey Variables into AVD is on the todo list.
Many times when my Homey Pro crashes or loses its power the value(s) of the BLL variables are not preserved / the ladt values/state they should be like just before the crash/powerloss.
Maybe a reboot is fine but not these kind of catastrophic events.
Well, you will not be forced to use these apps.
As written before:
standard apps can only access their own devices and flows => no special rights are needed
apps using other apps devices or system settings, logic variables etc. are using HomeyAPI and that needs special rights (full access).
Developers can’t define other permissions like “access app xxx” or “access logic”. It’s all or nothing.
Are you talking about the values of BLL variables as shown in the App Settings, or in the droptokens?
And, why does your Homey crash or loses power? Perhaps you should solve that first, because thats not good m8!
And, do you have a hp2023 or another model?
Because, if you have a HP2023 with the “failing power adapter”, than the attempt of saving the BLL variables could just as easily be a reason for that “random” crash, since writing settings makes it crash sometimes.
BLL saves it variables directly when it is changed, always!