Xathros

I can't say for sure but my gut says that the lock itself is the weak link here. The 599 in particular bugs me in that it can't be remotely unlocked for more than a few seconds yet there is a button on the lockset that will unlock the lock until it's told otherwise. Seems to me like Schlage never finished the ZWave interface on this one. -Xathros

Looks like only user access codes are represented in the "Control" list. Lock and Unlock are Status only events. -Xathros

You could break your program into two separate programs, one for each lock. That would also solve the problem. -Xathros Sent from my iPhone using Tapatalk

I'll have a look at what is available on my 599s when I get home and report back. My memory says I'm using control for some of mine but won't know for sure till I look. -Xathros Sent from my iPhone using Tapatalk

The if is evaluated any time either status changes. The FE599 when unlocked remotely will automatically relock after a few seconds changing it's status and forcing your if to reevaluate. This may be where the extra unexpected notification is coming from. You could change "Status" to "Control" and get the result you want. -Xathros Sent from my iPhone using Tapatalk

Sorry. I have learned from doing over many years. While I'm sure there are resources out there to learn from, I don't know where to point you. -Xathros Sent from my iPhone using Tapatalk

Thats how I read it. -Xathros

Excellent! Glad you got it going. -Xathros

Try port 587 and check the Use TLS box. -Xathros

Or, you could narrow this down to one program: Motion On Master Bath Motion On - [ID 0023][Parent 0025] If Control 'System Devices / Master Bedroom and Bath / Motion Sensor-Sensor' is switched On Or Control 'System Devices / Master Bedroom and Bath / Z-Wave Shower Motion Sensor' is switched On Then Set Scene 'Scenes / Master Bathroom and Shower' On Wait 2 minutes Set Scene 'Scenes / Master Bathroom and Shower' Off Else - No Actions - (To add one, press 'Action') In this program, the wait restarts with each new Motion On received and will timeout and turn off the lights after 2 minutes with no motion detected. Hope this helps. -Xathros

I'm using pool.ntp.org on both of my ISY's just fine with "Custom location" based on my lat/lon. One thing I found way back when I set this up was that I couldn't get the ISY to accept my location until I enlarged the custom location window and discovered that the longitude field that previously hidden. Once expanded and both lat/lon values entered, all worked like a champ. See below: One additional item to check: look at your error log after trying to sync. Make sure you have no DNS errors. If you do, you may want to try providing the ISY with 8.8.4.4 for a DNS server. Hope this helps. -Xathros

With the upcoming V5.x firmwares, things like date and time may be assignable to variables. Once that is possible, you should be able to order them however you like. -Xathros

Your looking at the settings for your incoming mail server. You need to look at the SMTP (Outbound) settings in your Apple Mail program. The settings Jimbo provided however will likely work for you. -Xathros

Hmmm. I replied to this around 4:30. Dunno what happened to my reply. Anyway, I tested and got the expected result- fail. Pretty sure that was a typo and should have read Device rather than Scene. -Xathros Sent from my iPhone using Tapatalk

Hmmm - Just noticed this in my notes: /rest/nodes/<node- id>/cmd/<command_name>/<param1>/<param2>/.../<param5> eg: /rest/nodes/<node-id>/cmd/DOF - turn off a device or a scene Insteon - /rest/nodes/<node-id>/cmd/DON/128 - turn on a scene to 50% This was copied from an older WSDK document an may be a typo. I have not tested this yet but will in a minute. -Xathros

That is because they are two entirely different actions. In the first case, the ISY's PLM is sending a DIRECT command to the ONE device in question. In the second case, the Device itself is sending a group command to all linked devices when you press the paddle. It's actually a very common to have this confusion with new users here. "Why when I control a device from the ISY does it not control the other devices linked to the device I controlled?" The difference is that the ISY and most other HA controllers are controlling the device with direct commands - not group/scene commands. If you were to analyze what happens when you brighten the scene by holding the paddle, you would see that the device is sending "Fade Up" then Fade Stop" to the group. You can do that same thing from your App via the PLM. The difficulty here is going to s specific brightness as that is NOT built into the protocol for a group command. -Xathros

I make a new backup after any significant change and with every firmware update. I have never needed to restore for reasons other than going back to an older firmware to test something. Regardless, I'd not want to be without a current backup. -Xathros

Not sure on the adjust scene part as I've never done that via REST. The direct ON commands are simply: /rest/nodes/12 12 1F 1/cmd/DON/143 /rest/nodes/12 12 1E 1/cmd/DON/143 /rest/nodes/12 12 1D 1/cmd/DON/143 -Xathros

Not sure how else one could end up in that situation but, as long as you have a good backup of the ISY, recovery shouldn't be difficult. -Xathros

I suspect that a Delete PLM was issued from the menu at some point. -Xathros

You issue adjust scene statements to however many devices in the scene you want to change then issue a scene On command or issue direct ON commands the the member devices with whatever brightness you desire. -Xathros

Do you have an recent ISY backup from before the PLM failure? If so, I would restore the backup then run the Restore PLM again. -Xathros

UDI currently has their first batch of 5 test PLM's ready but I believe they are waiting for a resolution to the pesky All On events before going into full scale production. -Xathros

Additionally, make sure the address is correct. 8 and B are often mistaken for each other. -Xathros