[DRIVER] Ring Alarm Keypad G2 Community Driver - Continued

[rob9]

I was looking at the topic @bcopeland had on writing Z-Wave Drivers for S2

[GUIDE] Writing Z-Wave Drivers for S2

I took a bit of a different approach with S2 to address the problem of devices that don't support S2 properly, while still allowing my S2 driver code to be used with those that do. I found that, for certain devices, S2 was simply broken. For others (several of my HomeSeer dimmers / switches), the device received the Supervision message, but then sent back the wrong S2 status code. So, what I did was put together my own S2 sending library, but in the driver, you can define two simple mapping f…

The "multi-event" code definitely doesn't appear to be in this driver (and, my hacked attempt at adding it made for a mess (somehow, got a "groovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (hubitat.zwave.commands.entrycontrolv1.EntryControlNotification, java.lang.Integer) values: [EntryControlNotification(sequenceNumber:61, dataType:2, eventType:0, eventData:), ...] Possible solutions: wait(), chars(), any(), wait(long, int), take(int), trim() on line 980 (method parse)" error.

I'm such a noob when it comes to the arcane details of S2 and z-wave protocol, that doesn't surprise me that I'd hose it up.

It seems that @jvm33 was tracking well with @bcopeland. Maybe @jvm33 would have some sort of idea.

I put my latest (NOT meant to be ready for use!) code here:

https://raw.githubusercontent.com/robstitt/Ring-G2-Keypad-Driver/main/Ring%20Alarm%20Keypad%20G2%20Community

As I mentioned earlier, the problems I am seeing look for all the world to be somehow tied to things getting out of sync--so the hub and keypad stop talking to each other.