Skip to content

DDF for EasyAccess EasyFingerTouch doorlock #6334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 16, 2022

Conversation

Smanar
Copy link
Collaborator

@Smanar Smanar commented Sep 15, 2022

See #5870

  • Product name: EasyAccess EasyFingerTouch
  • Manufacturer: Onesti Products AS
  • Model identifier: EasyFingerTouch

This DDF is for sensor version (ZHADoorlock) it expose :

  • config/lock to unlock lock the device
  • state/lockstate that can be not fully locked/locked/unlocked/undefined
  • state/open that say if the door is open or not

This device don't have poll cluster.

I have added a json item corrected for ZHADoorlock.

@Smanar Smanar mentioned this pull request Sep 27, 2022
@manup manup added this to the v2.19.0-beta milestone Oct 16, 2022
@manup manup merged commit 62fa62d into dresden-elektronik:master Oct 16, 2022
@manup manup changed the title DDf, add support for doorlock EasyAccess EasyFingerTouch DDF for EasyAccess EasyFingerTouch doorlock Oct 16, 2022
@cortado
Copy link

cortado commented Jan 4, 2024

Have EasyAccess EasyCOde Touch, and it seems to be the same lock. It shows up in Deconz, but not in HA (via Phoscon app ) – that is to say: it shows in DeConz plugin, but only with MAC address, no name or controllers or anything. Any suggestions @Smanar ? Here is info from DeConz:
Skjermbilde 2024-01-05 kl  08 04 09

Here is what is exposed to Deconz plugin with lack of controllers and info:
Skjermbilde 2024-01-05 kl  09 54 03

@cortado
Copy link

cortado commented Jan 5, 2024

to be mote precise: to make a correct DDF to make it be recognized by the system, what is needed/missing?

@Smanar
Copy link
Collaborator Author

Smanar commented Jan 5, 2024

I can make the DDF, except the cluster 0xFEA2 all seem classic, will take 5mn, but better to start a new issue (an admin can close this one, not respecting rules) , and I need at least a complete capture from the cluster 0x0000 with all attributes.

@cortado
Copy link

cortado commented Jan 7, 2024

I managed to load the DDF you have made (changing name to EsyCodeTouch) - and things are looking better :) But still something missing - controller not correct. So how do I provide what you need to get the last details right? Do not know how to "complete capture from the cluster 0x0000 with all attributes", or is this it?:
Skjermbilde 2024-01-07 kl  23 11 54

Skjermbilde 2024-01-07 kl  23 05 53 Skjermbilde 2024-01-07 kl  23 09 46

@cortado
Copy link

cortado commented Jan 7, 2024

Update: things looked even better after some reload of deconz. now it is only state that is a little quirky when it cones to state (does not reflect open-close auto sequence) - but I can open it through HA!
Skjermbilde 2024-01-07 kl  23 28 36
Skjermbilde 2024-01-07 kl  23 28 46

the info in Phoscon app in HA is probably result of a missing attribute?:
Skjermbilde 2024-01-07 kl  23 32 41

Also: is it possible to add managing of PIN codes and users through controllers in HA, instead of deCONZ interface?

@Smanar
Copy link
Collaborator Author

Smanar commented Jan 8, 2024

Ha yes I m seing there is clone for this device

zigbeeModel: ['easyCodeTouch_v1', 'EasyCodeTouch', 'EasyFingerTouch', 'NimlyPRO', 'NimlyCode', 'NimlyTouch', 'NimlyIn'],

But better to use the issue than the PR for comment.

now it is only state that is a little quirky when it cones to state (does not reflect open-close auto sequence)

After a missing state change, the value is updated when you read it in deconz ? Cluster 0x0101 attribute 0x0000.
I m seing this device have too state/open and state/lockstate (if they are not visible in HA can use Phoscon/help/API Information/sensors)
If yes, it's a bind/report issue else the problem is in the DDF.

For PIN code there is a basic code, but not valided yet #5918

@cortado
Copy link

cortado commented Jan 8, 2024

Thank, you! Sorry I am not very familiar with this, and put it the wrong place.

@Smanar
Copy link
Collaborator Author

Smanar commented Jan 9, 2024

Let me know if you continue your problem on an other issue (with saying my name), I m not checking all of them ^^.

Found it > #7525

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants