hart2hart

@Goose66 , I contacted Schlage support and received updated instructions compared to when I first purchased the locks. The locks now work all three ways: 1. Schlage App 2. HomeKit app 3. Nodeserver The new instructions is to add to Schlage App first and then in the Schlage App to take option "Works With Home?" to add them to the Apple Home app. I can now unlock with just touch of iPhone and Apple Watch.

Click Start Linking and then Press and hold set button till it dings always works best for me for adding devices. Is that method you used or did you key in the insteon id?

Try the login credentials you used before 6.0.0 was installed.

What version of FW is the eISY running. It changed with version 6.0.0 and started using the UD portal credentials.

I'm using only Wifi as far as I know and want to have control in eISY eco system like now and to be able to use Home Keys from Apple Watch and iPhone.

@Goose66 and others. I'd like to use my locks so that I can unlock with Apple Watch after a run. When I first got the I could only use one of these methods at a time. The nodeserver is great and so I can now do things from Schlage App and eISY NS. I want to add Apple home for watch and iPhone access. I located the following Schlage Encode Plus in Apple Home (w/ HomeKey) and Home Assistant - Hardware - Home Assistant Community Does anyone have experience with this config to support all three? The article mentions Home Assistant but it feels like the NS does the same. Alos, I see mention that using locks via Thread makes battery life 2x to 3x longer. Is it possible to leverage it with the NS or some other decent path like through HA?

That’s method I always use to add.

If moving only Insteon devices, it works well. Zwave adds to complexity. You want to upgrade as the knowledge around isy994 migration is fading.

How long has it been updating?

Thanks @bmercier ! That’s good news! Paul

Partition State has entry and exit delay. I use both.

@bmercier is this possible? Thanks for great plugin. Paul

Reboot eISY. There is a known issue where newly added devices show up with ghost nodes until a reboot.

…adding a bit more. Since node server can see need to Authenticate, could that be added as a node or field to detect it in eISY program?

Thanks, @bmercier . I can only recall needing to authenticate at install and couple weeks ago. Do you know what triggers a need to authenticate? I'm considering replacing my ring doorbell wit the new Pro 3 4K version. The issue is the new pro 3 does not have a way to ring you in house chimes. I use this capability in older doorbell to close a relay that signal to my Russound whole house audio system that plays the chime overall a set of speakers per floor. I've created the following programs that will detect the ding and close the rea in an IOLinc. Before I use it (in all the cloud glory) to signal doorbell, I wanted to ensure that Ring (device or service) is not prone to going offline and hence I would miss the doorbell ring. Ring should create a kit like the mini chime that receives the signal wireless but not cloud that will see the ring and close a relay. What do you think? Is there no way to detect Ring is not working for whatever reason? What does the Test function do? Sorry for all the questions as I can't locate more documenations. Thanks, Paul Front Porch:Doorbell Rang - [ID 017A][Parent 00E3] If 'Front Porch / Front Porch:Ring Doorbell' is switched Ding Then Set 'Attic / Attic:Doorbell Trigger' On Ring:Ring Front Porch Doorbell Status - [ID 0153][Parent 01F5] If 'Front Porch / Front Porch:Ring Doorbell' Status is not Online Then Send Notification to 'JPaulText' content 'Ring Node Is Offline'

@bmercier I had to authenticate recently and made a note to see if I can catch that condition via program. I already test the node server status for being offline. Is being offline also potentially an indication authenticate required? I don't think it does as I didn't get a notification in recent case. To that end, I wrote following 3 programs. Would they catch it at least within an hour? Also, is best practice to test each ring device for offline in addition to the node server (read other posts where they are not necessarily the same-- none of my Ring devices are battery powered) Ring:Ring Test Results_Run At Startup - [ID 014F][Parent 01F5][Run At Startup] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'Ring:Ring Test Poll Results' (Then Path) Else - No Actions - (To add one, press 'Action') Ring:Ring Test Poll Results - [ID 0150][Parent 01F5] If Time is Last Run Time for 'Ring:Ring Test Poll Results' + 1 hour Then Set 'Ring / Ring' Test Ring Else - No Actions - (To add one, press 'Action') Ring:Ring Test Poll Results Evaluation - [ID 0152][Parent 01F5] If 'Ring / Ring' Test result is Ring Auth. Failure Or 'Ring / Ring' Test result is Timeout Or 'Ring / Ring' Test result is Failure Then Send Notification to 'JPaulText' content 'Ring NodeServer Failure' Else - No Actions - (To add one, press 'Action')

Are the LED lights listed as dimmable?

i saw issue with mixture of Insteon and other plugin devices. All corrected by reboots after the device was added.

It’s a bug in 6.0.0. Reboot eISY and they’ll go away.

Exactly what I use.

In admin console, click on: Link Management Start Linking At this point you press and hold the set button on the switch and it will pop up on the screen to be added.

It does that for one day after each time change and corrects itself I believe at midnight that day. Programs actually use the correct time for sunrise and sunset, it’s just displayed incorrectly.

@[mention= rel=]sjenkins[/mention] has done excellent work with the virtual plugin. The only thing I’d add is if you are on eISY V6.0.0 it’s got an issue and may show the new device 3 times. You can fix it by simply rebooting the eISY. Edit: eISY has the issue not virtual

I reported to UD and response was it’s a known issue and will be fixed in the next release. If you reboot eISY, the extra devices go away.

[mention=16016]bmercier[/mention] I was researching another issue and located a couple year old post that suggested an eISY reboot. I rebooted and it fixed that issue, so I looked to see if this was resolved and it damn sure was!