mango

Regards the x10/A10 module, I didn't experience any issues moving config to a pro unit that did not have the module installed. I used to use X10 as virtual devices which was handy for controlling stuff from UD Mobile / Mobilinc. The device tree still showed the X10 device but it was presented as exclamations. They were delete-able.

Late to the party. I may be able to help you. I have quite a few ISY994s I don't really need most of them. I acquired quite a few when I bought Insteon lots over the last few years, they came with everything. Let me know if interested I could probably find one spec'd the same as you use now. I live in Canada if shipping is a concern.

Thanks both!

Sorry to hijack this thread, but I'm interested in this method. Care to explain a bit further?

Not wishing to ever disservice UD and the excellent products and services they provide, there are ways to connect to the ISY securely / remotely without using the portal for UDI mobile and mobilinc. I have some 994i's that are still currently subscribed to the portal but also have a backup configured that uses Wireguard VPN and works very well.

Copy to clipboard is a function that helps. Paste to a text file with chunks of others then once tweaked, import into new program.

It's relatively easy to reinstall regular switches and dimmers, the wiring should be traditional and power everything the circuits are wired to.

I have some hardly used new appearance 2466SW toggle switches at the cottage. If you're interested, hit me up. Shipping would be from Canada.

Perfecto thank you so much.

Hey Javi, https://fonts.google.com/icons?icon.set=Material+Symbols&selected=Material+Symbols+Outlined:door_open:FILL@0;wght@400;GRAD@0;opsz@48&icon.query=door&icon.platform=web door_open

For @Javi If possible please add the google door_open icon Both icons together (door filled and door open) would work well for door sensor status.

Why don't you have the courage to use your name, and own your issues? You obviously did not do any research about the upgrade and did not follow protocol.

Yeah I appreciate everyones comments I may rethink this.

Never, had a problem in years of using Schlage zwave locks. That function has been rock solid, Unlock, Jam, etc. Default mode upon first arrival is Owner/Away. Everything would work for the guests when they arrive in that mode anyway, they really wouldn't notice a difference. I am notified of human activity upon their arrival through Pushover on my phone and I can set the modes remotely should things not work, but as I say, it's never had to come to that. It's only basic stuff. For instance the guests stay is usually 5-10 nights, I am aware of check in and check out day, and keep an eye on things. Upon first change of mode from Owner/Away to Guest/Home, if around dusk all the main lights turn on to welcome you. I have also have modes for housekeeper and handyman. Guest/Away mode and Owner/Away mode are both automated security lighting at night and a few other things. 95% of the building scenes and functions are shared through all modes

Hi @MrBill This is where I appear to think I have things already decently setup. Most of the programming is generic for all users. It's only some functions where I want a bit of granular control between uses. The modes are set when the doors are unlocked, and guests are unable to set the modes.

Well, Mr Bill, we use pretty much the same nomenclature 😬 This basic one has been working well for me for a couple of years now. I'm concerned with what @DennisC has said. Perhaps I should just use a structure of IF programs(?)

Thanks both. The ISY involved is a cottage rental, so I have conditions (mostly security, some utility control (HWT, Well pump) for Guest, Owner, Home and Away. The conditions folder feature works well for me, but I have things a little untidy as folders were added over time. I think I can make a cleaner structure which will have the benefit of reducing a bit of load (steps and triggers) on the ISY. EDit: typo

No need to answer I found this in the Wiki: Program folders can have conditions. These conditions must be met before any programs within the folder will run. Folders can be nested and thus Folder Conditions can be cascaded. I can assume from this 3 nested folders down will work properly.

Hi folks, I'm cleaning up some program structure and just want to make sure that nested folders inside a root folder that is set to conditionally allow to run will allow programs to run? Is there a limit for folders inside folders? I anticipate no more than 3 nested folders. I did a quick test and it appears to work, but want to make sure this is permitted by design, and works 100% before I change things around.

Yes, working again now.

Ironically this follows a power outage at a remote address so I ended up chasing pixies for a couple of hours. Ugh.....

Not only you! I have been trying to troubleshoot this morning. I shall stop and wait it out now. UD Mobile - Error 500 Mobilinc Pro - Connection Error my.isy.io - Up

having a known working PLM to test would be the way I would go, but I'm no expert YMMV. It's *usually* always the PLM that croaks before anything else.

Sorry for the delay I have not been on the board for a while. Yes, zwave plus. No comms issues here but most of the installations are within good range with the ISY's directly. I think Bluetooth features come with the sense range (sense has no zwave) not the connect range. Yes, I use some locks at a guest house and change the pins remotely according to the guests preference (that way they always remember it). The locks can trigger events based on user number, locking and unlocking the door(s), and lock state. I perform some actions based on that (guest mode / owner mode etc.).

Schlage Connect have been rock solid for me over the years.