lilyoyo1

So sensitive. It's simple. Instead of being selfish, start a new post instead of hijacking someone else's so that others can easily find your solution. We appreciate you posting the solution to your problem for others who may be in a similar situation. Had it stayed in your hijacked post, it probably wouldn't have been found.

You don't have to try and be smart about it. After all- You are the one coming here for help. One of the many complaints about the forum is how hard it is to find information which results in unnecessary duplicate posts. We all are just trying hard to make this a better experience for everyone- especially new members who are not aware of the best ways of finding information.

This has nothing to do with the original post. Please do not hijack a thread like this as this screws up the search results. This really needs to be it's own post. Thank you @Geddy

I suspect the x10 module doesnt exist on polisy which allows you to add x10 to the device list like it does for 994. Since you ported to the Isy, the original came over with it but new add-ons aren't possible which means you'll need the code via programs

He's using recent firmware while you're using older 4.xxx series firmware

I use a combination of both. I'll put the devices in the scene and then use a program with my assistants. This way, when I tell my assistants to turn a light on, it'll do so and if i say turn lights off, it'll turn off any light that's on

Can't beat this part!

Depends on device. He'd have to check with the mfg. There is no consistency to zwave behavior

If it's hardwired then it's no longer a battery operated device.

It's probably firmware that has not been released yet. Plus I'm assuming he's referring to their own board

This is the best news right here

I'm glad i could help. Polisy currently uses S0 security when adding locks. There is no issues with adding locks that I've seen to polisy so you'd be able to add to either of them. I have a contact as I'm a qolsys dealer. While I'll still use the elk for specific use cases, qolysys is about 95% of what i do now. Security doesn't necessarily need to be a major part of automation. The only thing I'd want it for is to enable/disable my alarm system when I come and go. The good thing with qolsys is that you can use your phones Bluetooth connection to disable the system when you come home (that's what I do). For those without a system, I'll use the locks with it as well so that the system can lock the doors and close the garage doors too.

I'm referring to qolsys being the primary. The locks will add to the ish (if it's a secondary but will not update.

Things may have changed since I've last looked into it but I'm not aware of any alarm system that can be used as a secondary controller. Due to the nature of the product, all want to be the primary. Once polisy supports S2 encryption, you may be able to get your locks to show up in polisy (at least i hope so).

Do you have a link to that article? Secondary controllers are great for large or spread out systems. If you have an avg home with a typical install, 1 centralized controller would be better. To put things into perspective, my old house was 5400 Sq ft and I was able to use a single controller with all of my devices (about 40-50). There is no documentation as each system has their own way of doing things. Some will only be a primary and can't be used as a secondary. Some will not pass on security keys to track secure devices such as locks. Because each has their own stipulations, you'll have to look through each manual of your chosen system and/or talk to them (which they probably won't help with anyway). The why you'd use a secondary controller is simple. If you have a large home with devices on opposite ends, it would be cheaper to have 2 controllers than fill in the gap with unnecessary additional devices just to communicate with each other. Second reason is a large system. Zwave controllers are limited to around 250 devices. Real world is probably half that (depends on device types). In addition, the larger the install, the slower your system will be as well as the likelihood of issues. Secondary controllers allows you to bypass those limitations while having the benefits of integrating everything under 1 controller.

The tabs are glued on as the battery is designed to be none replaceable.

https://forum.universal-devices.com/topic/33710-solution-for-dimmable-led-light-strips-with-automations/

Not sure why you feel polisy may not support insteon in a few years when UDI's next gen controller (eisy) supports insteon as well. The work for insteon is already done. They'd need to rework the whole system to remove insteon capability. Maybe somewhere down the line but definitely not in the near future to worry about another Isy. Besides, you'd simply be continuing on with an obsolete device

@Geddy- this is posted in the wrong forum. Since the op is using Polisy with the zooz stick, it could cause confusion with it being posted in the Isy zwave 300/500 series section To the op @Prana electric. Leviton uses hail for status. You'll have to use programs to query it and get status. https://forum.universal-devices.com/topic/34097-leviton-zwave-plus-doesnt-report-status/#comment-321618

Not all node servers offers a trial. You could use the PG2 version which is free (though unsupported if you want to temporarily test things before purchase

It would help if you provide us with the devices you're having issues with, your programs, how you set it up, your Isy firmware & UI, etc

Same process as swapping out a PLM. Best practice would be to read the wiki and follow it. Not following would be what not to do. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29 Also, make sure you have a recent backup of your system before doing anything

Contact UDI

Isy exposes what zwave offers within a device category/command class. It's up to the mfg. whether or not they take advantage of it.

It's the same as all of your other devices. Weakness in the zwave design