This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Official
Comments
So is there a way to make it be recognized?
Two options to solve:
1) Create an Github issue for Athom to add this productTypeID to the current app and wait for the app update to be released to the app store
2) Download the current version of the app and manually add the productTypeID at https://github.com/athombv/com.danalock/blob/master/config/drivers/danalock_v2.json#L19
to be changed to `"productTypeId": [3,8],` and install it via the Command Line Interface (see https://developer.athom.com/docs/apps/tutorial-Getting Started.html)
Thanks, i'll see how i can create an issue on GitHub, for the long term it may be better, and if i feel in the mood of it i'll try modding the app
I'm considering buying Homey to use with Danalock V3. If connected, does Homey then serve as a danabridge also? E.g. enable remote locking/unlocking?
Thanks in advance,
Hope my question is clear.
Thanks for the support so far.
Sander
When opening the door with the geofencing on the danalock app the status in homey isnt upated, so in homey its stays on lock most of the time.
Also whem homey notice iam away its locked the door. But then when coming home and unlock the door with homey it works. To bad it also unlocks the door with the danalock app. So worst case senario if you fast and you already clossed the door it unlocks a second time. I already had a few time the door was open at night.
Good thing is athom has now a lock itself so the can playing around with it and fixing things.
For now i only use it with the danalock itself. Meanwhile trying to fix the precense status of homey. And if thats 100 procent again i only gonna use it trough homey.
I have tried to unmount the Lock from the door and bring it within 50cm of the Homey again. Then I was able to remove the device, and add it back in. Also I could control it at that distance.
Also, I have tried to restart the Homey with no luck.
I du see a number of timeouts and errors in the z-wave log, like this:
Does that mean anything to you guys?
Should I return the Danalock, or is this a Homey issue?
the Philio is a battery operated device, isn't it? The z-wave routing only works with mains powered devices. You could place a z-wave socket nearby.
Just went and got another Fibaro Wall Socket, and that seems to do the trick... At least for now!
But out of curiosity, shouldn't the Danalock be capable of connection to Homey, when when the Philio and the Fibaro devices are? The new Fibaro is actually another 5 meters away from the Homey
Good, nice that it worked.
Yes they should.....I have heard more z-wave range issues with the Danalock.
greetings,
Aaron
Athom is looking into this
First the log would not communicte if not REALLY close to Homey.
Then I added the Fibaro Wall Socket, and now the locks communicates nicely through Fibaro...
Maybee youre zwave network is still small. Then flirs trafic doesnt get lost that easy
Do you have any plans for supporting Danalock Bluetooth/Zigbee
Have been trying to get it work with you app as reference but probably getting the functions wrong.