hart2hart

Has there been a better than $10 off on $50 (20%) items since Insteon came back to life?

Great, thanks. Let’s see if UD upgrades the python library. If not, is it possible I could use HA(potentially on eISY) to implement this functionality?

To be clear, did you define the scene in the Admin Console and then create the same scene using device to device method?

My guess is the switch connected to the fixture is going bad and losing its link table. I would have restored it only to see the impact. Or maybe one of switches is going bad and generating noice on that circuit to which I’d air gap them one at a time to see if problem goes away. First the two controller only and then one connected to fixture. If it’s the one connected to the fixture turning other two on and off will show in their LEDs but fixture will not be controlled.

Thanks. I could use the alarm open zone via envisalink-DSC because the doors I open are entry delay so could catch that to force update and then get the user.

Thanks. I recall that now. Was there something called Force Update you had added that could be used to effectively lower polling interval?

That sound good! As we discussed in the past (can't find thread or DM but recall the exchange), the ability to catch the unlock event and the Access Code (not the actual number but a representation) would be a great feature for me. With the Schlage ZWave locks these WiFi versions replaced I used a UserNumber and with that via a program then sent a Disarm security command via Envisalink (likely using NodeLink at that time). I had a user on the lock with the Distress Code so that code could be entered on the lock to send through as Distress code to alarm monitoring. This was a big plus when having hands full coming in door located near alarm keypad and even greater to allow entry though doors not near the keypads.

Thanks. If we get to that point, does it look like access_code_id could be used in programs to identity the code used to disarm?

Thanks. @Goose66 I suspected that it would not be until python was updated on eISY. However, once/if that occurs, would the newer library provide features like detection of who just unlocked the door? Going into an area I don’t know, do you think/guess will it be possible to use the updated library from another box like rpi or on eISY once the HomeAssitant extension is released to leverage those features?

Good morning @Goose66 I was just reading about the plugin issues related to library version and supporting python version required to run it. That prompted me to look at the public documentation for pyschlage. I notice some methods that may have been added at some point. With these methods (if I read correctly -- big if) could we possibly now detect unlock events and quickly get the user that unlocked it? for example method below. Thanks! lasspyschlage.log.LockLog(created_at: datetime, message: str, accessor_id: str | None = None, access_code_id: str | None = None) A lock log entry. access_code_id: str | None= None Unique identifier for the access code that triggered the log entry. accessor_id: str | None= None Unique identifier for the user that triggered the log entry. created_at: datetime The time at which the log entry was created. message: str The human-readable message associated with the log entry.

Thanks @paulbates

Thank you.

@bmercier , thanks for great plugin and updates. I received notification the a new version is available. Where are release notes posted or is it just internal cleanup?

Only as a point of reference, I have 3 7900. They all have 6.93 fw (which is the latest & been that for years) and function as desired.

I use humidity control and the values for Humidifier Active are True and False as Goose describes. Do you have the Thermostat setting for Stages and Outputs then Aux Output Stage set to Hum?