Goose66

The erase is not as important as going through the setup steps to get the initial settings right so the Discovery process will work. See here and here.

The original issue just sounds like the “profile” for the plugin didn’t get successfully loaded. You could have loaded the profile from the PG3 dashboard and restarted the Admin Console to see if that straightened it out. However, now it sounds like the plugin setup is corrupt once you updated your ratgdo. I would suggest factory reset ratgdo, delete plugin, and then follow all the instructions again to install and discover.

I only did it once. It was the DSC1832 I had when I wrote the original PG1 version of the plugin. It had been installed by an alarm monitoring company (Loud). The keypads and everything was branded. The factory reset via pin jumpering technique took it back to default factory settings.

There is a way to factory reset the 1832 boards to default values (including passwords) by jumpering two pins in the controller chip.

Run the plugin with “Debug” logging level so we can see what it’s doing differently.

I think you need an EyezOn UNO4 expander as well. Never tested the plugin with this setup, though.

A new version of the plugin v3.2.10 has been uploaded to the Production Plugin Store. This version adds the ability to specify a user code for the Disarm command. If you do not specify a code, it uses the user code from the Custom Configuration Parameters.

Just refresh your Plugins Store. It's there.

We don't need an updated version of the pyschlage library to implement this functionality, so I went ahead and rolled out a new version 3.2.4 using the older library that adds the requested functionality. Let me know if it works for you.

A new version v3.2.4 of the Schlage plugin has been uploaded. This version adds last message time, last message, and last used access code state values from lock nodes. Remember that this plugin relies on polling of a cloud service, so changes to node state, like an access code being used to unlock the lock, may not show up to up to 60 seconds or so after it occurs. Please don't set the polling intervals too low to capture this information any faster, because frequent, repeated polling may cause Schlage to start blocking access (a la MyQ). Instead, try and find some other event, e.g., a motion sensor, that may indicate that someone has entered or exited through the door, and in a program use the Force Update command to refresh the state of the lock before checking the state values for further action. See the Release Notes at https://goose66.github.io/nsdocs/schlage-pg3.html for more information.

I uploaded a new version of the 3.3.15 zip file to the Production Plugins Store. If you upgrade one last time, it should stop posting the message. Also, I updated the release notes for the 3.3.15 version.

Sure. Not released yet, though.

@JBalog Was this resolved? Also, did you delete and rediscover your devices after installing the update?

Does the Bond Home app show more commands than just Open or Close? Also, what is the device type up at the top of the node details in the Admin Console? A Shade should never show “On” or “Off,” but “Open” and “Close” (at a minimum). Adding a screen grab from the Admin Console would be helpful.

The docs suggest it may be a Pro only thing, but you can try deleting and re-discovering your shades to see if they show up as having position support.