I'll take a look later this evening. By the way these devices are super cool. I wish they weren't $70 a piece. I have too many windows for my wife to be OK with that!
1 Like
One last thing, when you loaded it in as Device, could you please go to the device and paste the part that looks like:
Actually if you could paste a screenshot, plus that inClusters part as text (so I don't make a typo retyping it!) that'd be great. Think I'm making progress, just have no way to test
I'll probably have to do that on Thursday night. I'm off site now and haven't had time to sort out a good VPN method so I can only see the dashboards at the moment.
Gotcha, well I think I have it to a point where it would work, but without that data section it won't autodetect, it'd still pair as Device. I'll upload the code to github tonight and you can test on Thursday.
Give this a shot
When you can get me that data section I'll update it. If you run into any issues let me know but I think I fixed the 3 errors you reported.
1 Like
Here is the Data section:
inClusters: 0x5E,0x86,0x70,0x8E,0x85,0x59,0x7A,0x71,0x22,0x5A,0x73,0x72,0x60
Cool... so moment of truth, does the driver I provided work? 
Was just trying it as I pasted that. It gets farther than the previous driver, but I'm still getting some errors:
dev:1622020-05-14 08:49:10.054 pm debug'zw device: 1A, command: 600D, payload: 0B 00 71 05 00 00 00 FF 09 FE 00 C4 00 , isMulticast: false' parsed to null
dev:1622020-05-14 08:49:09.748 pm debugChild not found for endpoint. Creating one now
dev:1622020-05-14 08:49:03.329 pm errorjava.lang.StringIndexOutOfBoundsException: String index out of range: 7 on line 143 (parse)
dev:1622020-05-14 08:49:03.161 pm debug'zw device: 1A, command: 6008, payload: 80 09 C4 00 , isMulticast: false' parsed to [[name:epInfo, value:[null,null,null,null,null,null,null,null,null], displayed:false, descriptionText:], 600901]
Got a little time to try to debug? I just checked in a little debug logging
FYI for anyone following, @dtbrewer helped test and I have this working now. Information is availabe at [RELEASE] Andersen Verilock Translator Driver
I'm looking to combine a lock and context into a single device, exactly as the thread topic suggests. The drivers in the thread seem to refer to a specific Andersen product, Verilock. Has anyone successfully combined a lock device and a contact device into a single lock/contact device. My primary purpose is to have one tile on a dashboard that indicates both attributes.
Even if you create such a device, there is no dashboard tile that will display it like that. You'd need to create a custom tile using HTML with something like SuperTile
Totally prepared to do that. I have other tiles that show 2 attributes, like temp and motion.
Ok good. Then this is really something that would require groovy coding to take care of. You would need an app that allows you to pick both the lock and contact and then a device that supports both capabilities.
I remember that @mike.maxwell had a universal device handler for SmartThings that had lots capabilities and devices - including lock and contact sensor. But I can't find it on GitHub any more.
I would also check the ST forums - there maybe another device handler similar to it that you could port to Hubitat.
2 Likes
