hart2hart

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.

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?

Hi. I created the following programs when I moved from NodeLink to EnvisaLink-DSC to account for differences in their state tracking models. The goal is to have 3 variables that tracks Security Armed/Disarmed, Security Away Armed/Disarmed, and Security Stay Armed/Disarmed. It looks like they are still fine but could be updated now to simpler representation. Can you take a quick look to see if you agree? Security:Set Armed - [ID 003A][Parent 000C] If ( 'Security System / Security System:Partition' Partition State is Armed Away Or 'Security System / Security System:Partition' Partition State is Armed Away Zero-Entry Or 'Security System / Security System:Partition' Partition State is Armed Stay Or 'Security System / Security System:Partition' Partition State is Armed Stay Zero-Entry ) And $Security_Armed is not 1 Then $Security_Armed = 1 Else - No Actions - (To add one, press 'Action') Security:Set Disarmed - [ID 0059][Parent 000C] If ( 'Security System / Security System:Partition' Partition State is Ready Or 'Security System / Security System:Partition' Partition State is Not Ready ) And $Security_Armed is not 0 Then $Security_Armed = 0 Else - No Actions - (To add one, press 'Action') Security:Set Armed Away Armed - [ID 0005][Parent 000C] If ( 'Security System / Security System:Partition' Partition State is Armed Away Or 'Security System / Security System:Partition' Partition State is Armed Away Zero-Entry ) And $Security_Armed_Away is not 1 Then $Security_Armed_Away = 1 $Security_Armed_Away_I = 1 Else - No Actions - (To add one, press 'Action') Security:Set Armed Away Disarmed - [ID 0031][Parent 000C] If ( 'Security System / Security System:Partition' Partition State is not Armed Away And 'Security System / Security System:Partition' Partition State is not Armed Away Zero-Entry ) And $Security_Armed_Away is not 0 Then $Security_Armed_Away = 0 $Security_Armed_Away_I = 0 Else - No Actions - (To add one, press 'Action') Security:Set Armed Stay Armed - [ID 005C][Parent 000C] If ( 'Security System / Security System:Partition' Partition State is Armed Stay Or 'Security System / Security System:Partition' Partition State is Armed Stay Zero-Entry ) And $Security_Armed_Stay is not 1 Then $Security_Armed_Stay = 1 $Security_Armed_Stay_I = 1 Else - No Actions - (To add one, press 'Action') Security:Set Armed Stay Disarmed - [ID 005D][Parent 000C] If ( 'Security System / Security System:Partition' Partition State is not Armed Stay And 'Security System / Security System:Partition' Partition State is not Armed Stay Zero-Entry ) And $Security_Armed_Stay is not 0 Then $Security_Armed_Stay = 0 $Security_Armed_Stay_I = 0 Else - No Actions - (To add one, press 'Action')

I used nodelink and moved to envisalink-DSC a couple years ago. It does update status and last user.

I recapped every capacitor and brought two of them back to life. This included the daughter card capacitors. None of the capacitors had ruptured and were not even swollen.

It sure did and I did same with Nodelink. It’s where I became acquainted with optimal humidity levels based on temperature.

I also use Venstar Colortouch thermostat to control humidifier. I have programs that monitor outside temp (also on thermostat if you install remote sensor) and set optimal humidity levels to prevent too much humidity that will fog windows and can cause mold.

I’ve got a copy of nodelink.dll that you can run on a Windows PC. Docker not required. Let me know if you want it.

EnvisaLink-DSC is a node server that runs on PG3x. It does all same things that original DSCLink did and then NodeLink when it combined several xxLink programs into one program. NodeLink if it can be found will run on Windows. The author io_guy was great but has moved on to other HA endeavors and his automation shack site was shut down. Are you running in ISY994 and if so do you plan to move to eISY?

I moved from it to eISY and PG3x. There is EnvisaLink -DSC node server that replaces nodelink.

Good morning, @bmercier. Got an update notice and upgraded to 1.2.1 from 1.2.0. It says installing but still reports 1.2.0 as version. Also, there are no release notes.

I believe it’s called TimeData. There is also one called Sun. I may have renamed it to include celestial in the name.

My guess is it calculates the sunrise and sunset times at midnight but did not apply new time to the calculations correctly after the change. As others have said, it will probably be right just after midnight. I feel like that this was reported last change and it was confirmed that it’s the displayed sunrise and sunset that are wrong but the actual comparison times used in programs is correct. Did I dream this or does someone else recall the same? I located post where it was discussed. /topic/43242-sunrise-off-1-hour-this-morning/ I use lux value from weatherflow to turn on and off lights based on night and day so wouldn’t notice if it were wrong with eISY.

Here you go: DayLight Saving Time:Check For Change If 'Date Time and Celestial Info / Calendar' DST is not '$Daylight_Saving_Time_Current Boolean' Then Wait 5 minutes Send Notification to 'Me' content 'Daylight Saving Time Change' $Daylight_Saving_Time_Current Init To 'Date Time and Celestial Info / Calendar' DST $Daylight_Saving_Time_Current = 'Date Time and Celestial Info / Calendar' DST System: Restart IoX Else - No Actions - (To add one, press 'Action')

I have a program that uses time nodeserver to detect time change and then forces a reboot. Works great!

The latest version of the node server is for ESPHome based ratgdo firmware. Is 2.59 ratgdo firmware only for the mqtt version? Which would break its connection with the node server.

You can upgrade ISY to 500 board and then make the jump to eISY. It’s what I did.

I had about that length over shielded cat 5 or 6 for a time. Seemed fine. I don’t recall which 2 of the 3 wires were in a twisted pair but I’m sure google will tell you. Also a balun could be used which moves signal from unbalanced to balanced for the trip over wire.

FYI PaulWieland commented 4 days ago I finally have an example of this problem in front of me so I can trouble shoot and fix it, and plan to do so in the next few days PaulWieland added a commit that referenced this issue 31 minutes ago Fix command values … 7521d1e PaulWieland commented 20 minutes ago Version 2.59 changes the data values sent to the GDO for control, and should hopefully fix this issue. PaulWieland closed this as completed 20 minutes ago