polski-g

@raman325 These automations: https://raw.githubusercontent.com/FutureTense/keymaster/main/assets/additional_yaml/zwave_js.yaml @firstof9 binary_sensor.frontdoor_network is listed as "Connected"

`User Code` is showing up. Code 1 (`[20-99-0-userCode-1] User Code (1)`) is defined. I defined it from within the zwavejs2mqtt control panel, *not* keymaster.

my log looks identical to @rsummers618

I also only have `keymaster_synchronize_codeslot_LOCKNAME_TEMPLATENUM`

Automation is `synchronize_codeslot_ ...` not `keymaster_synchronize_codeslot_ ...` I set up id for codeslot 1 (in which the MQTT/live value matches the value set in Keymaster) and the automation was executing....

There is no trace, it does not execute at all.

> Does the `binary_sensor.pin_synched__2` show on or off? Off

> and `sensor._code_slot_2` is populated right? Yes, it has a 4 digit number. Control panel `PIN Status` is currently stuck on "Adding"

> There's a workaround at http://fitblip.pub/2012/11/13/proxying-dns-with-python/ . It seems it just skips the DNS lookup, under the assumption that the SOCKS proxy can handle the DNS lookup itself. Maybe that...

treat_life nor treatlife are not valid. Tested with your debug_discovery.py script.