First tests work as a charm!
@Arie_J_Godschalk
I have an issue with the latest official version (3.5.7) of the app. The action card to open the door doesn’t work anymore. When i test or debug the flow the card throws the following error:
this.unsetWarning is not a function.
I also tried the latest test version (3.5.8), the problem still persists in that version as well.
Thats weird. What kind of homey are you running it on?
Or are you on cloud/premium?
I am running a Homey Pro on version 13.5.1-rc.5.
The lock it self runs on version 2.8.4, and the bridge on version 72.
Are you sure you had 3.5.7. installed (before)? Because i never released that version.
Anyway, the current test version 3.5.9 should solve the issue 
I installed version 3.5.9, and it indeed solved the issue.
Thank you!
There is a new issue now. Opening the lock doesn’t function anymore since the update. I get the error message in the flow: “this unsetWarning is not a function”.
Yeah, its been resolved in the current test version.
I have no idea why 3.5.6 was pushed to production since i never submitted that release.
And unfortunantly, because of the Name change, it has to go through the Store Review to be pushed to production.
In Homey app version 3.5.12, the “Then” card “Unlock” now also opens the day latch. Previously, this card only retracted the night latch.
Expected behavior:
Action: “Unlock” → Night latch is opened (the day latch is not operated).
Action: “Open” → Opens the day latch for a few seconds (if the lock is locked, the night latch is retracted as well).
In the Loqed app v3.07 (1) for iPhone, this still works as expected.
Hey,
This is a setting in the device settings: Unlocks opens the door"
{
"id": "unlock_also_opens",
"type": "checkbox",
"label": {
"en": "Unlock also opens the lock",
"nl": "Ontgrendelen opent ook het slot"
},
"value": false,
"hint": {
"en": "When checked, unlocking the lock will also open the lock.",
"nl": "Indien aangevinkt, zal het ontgrendelen van het slot ook het slot openen."
}
}
This setting has been there for about 2-3 years, when i update the app to SDK3.
The dafault value is always false. Users can manually turn it on if they would like.
(It is automaticly turned off also when the lock doesn’t support ‘open’).
Straingly enough, i havent changed anything about this in years. But this week while testing, one of my locks suddenly had the setting set to true.
But i’ve just rechecked the sourcecode, and indeed, nothing about this has changed in any way (except right now im building in an error that when you save the settings, and this setting is set to true, an error will be shown.
But for you, just put the setting off in the settings of the device.
