lilyoyo1

It's always crazy to me when a person tries to get smart with those responding to their questions for help- especially when they have multiple posts with issues. You'd think they would hold off from doing that until their issues were at least resolved

160commands. I'd have a headache trying to remember all of them. ?

Add extra devices

If it ever hits 200, I'm going to start selling a few of the extras that I have

I'm out there every couple of months

It's hard for a long time user of Insteon to transition to zwave due to the inherent differences between the 2. The difficulties and nuances of zwave become readily apparent. With that said, since you already have the devices, a pigtail, and planning to factory reset anyway, I'd try it one more time. What I do is add each device to the Isy, so that I know it works and the Isy can communicate with it. Starting with the device which will be closest to the Isy, I'll add it and then install in its final location. I'll then add the second device and install it, working my way out. While I'm getting my 3rd device set up, I'll run update neighbors on the second device. I'll follow the same sequence with each device. By installing next to the Isy, I rule out distance and communication issues allowing me to focus on the device itself if it doesn't work. Once at its final location, if there's communication issues, I know I need to fill in the gap somewhere. Please Note- everything you read about zwave range is open air under perfect scenarios. A device can talk across a football field outside but put it in a metal box behind walls, mirrors , and furniture (not saying this is your home), and now you can barely get communication in the same room.

Orange County is much better than LA! ?

First, I would make sure Network wide inclusion is turned on. This can be found in the zwave menu. Then try adding devices from their final location using that going from closest to Isy and working your way out. Zwave uses routed messaging so anytime a device is moved from its original inclusion place, its routing table must be updated. You would achieve this by doing an update neighbors as Asbril mentioned. Self heal takes time. If setting up a new network that you want to use immediately, I would not trust it. Besides, if a device has problems overall from the start, it doesn't guarantee self healing will work.

That's how it's supposed to be done

You are incorrect. The hub is its own separate system.

What's your UI

There are still many people using insteon with their ISY who would like to use it with Polisy. Polisy supports the USB plm of which there is stock showing as well as with standard devices such as light switches, keypads, and outlets. Recent development has been for zwave since zwave is new technology for UDI (compared to Insteon). Insteon has had its development since the ISY26 over 10 years so its mature whereas zwave started in 2014 or so and due to the nature of its process, takes much much longer to develop for than insteon.

Newer devices (zwave plus) do report status for the most part. Whether it can be used as a controller is a different story

Given that you've had additional posts about other stuff and were still posting the next night about other issues (including on this thread) that cropped up, I doubt it solved it in an hour. And if it did...then closing old threads accomplished exactly what it was intended to do.

I highly doubt that someone would have commented being that Kush (original author from your 1 year old post) hasnt been on here since July and jca001 has been on but didnt even bother replying on here, you probably would not have gotten a response. Had your approach been much different, I wouldve given you the answers from the start. YOU chose to be difficult and act entitled which is why you had to go through all of what you went through over the last few days. Think what you want. You are the one with issues. You were the problem every step of the way. Those willing to help you have working systems and the knowledge you lack. This is all on you and you alone.

We wouldve been had he not specifically mentioned, x10, insteon, and his ISY system (in a residential home). Context matters

I couldve sworn we were talking about residential home automation not large corporate offices (who wouldnt be using the ISY and Insteon anyway). Ditto for small to medium sized businesses.

Please stop making mountains out of molehills. Yes, closing old threads worked out the way they intended. You did make a new post didnt you? Unfortunately, you chose to act entitled and ranted and raved instead of simply posting your issue and asking for help solving it. The same wouldve happened had the old threads still been up. The difference is that UDI and everyone else wouldve needed to go through all of the posts. Those posts were 1 and 3 years old. If the authors were going to update them, they would have done so by now since they've been open until recently. Not only that, if they were still perusing these forums recently, they could have chimed in on your posts giving you an update (which they did not), which means they either aren't on here or didn't care enough to update you. Either way, whether it was on this post or an old post, you would've been in the same boat. Most people don't update their posts when something gets fixed or works out for them. Using one of your old posts for example, UDI, added what you asked for when it comes to notifications and you didn't bother to go back to it with an update. You were using 3 year old software, ranted about a bug and when I tried to help you, you refused the help. Had you simply put your pride aside and asked for help or responded to my request, i would have given you the needed information a long time ago. Unfortunately you chose a different path and now you're still here doing the same. You're the one stuck with issues but instead of setting pride aside, calming down and asking for help, you double down which lessens the chance of anyone bothering to help you now and in the future

X10 is a 70s/80s technology as such has stuff for control during that time. Insteon and the Isy is modern technology so their focus is on modern technology means of control. Present and future users most likely would be focused on web based means of control and other modern technologies. Most likely they would not be purchasing older systems such as X10. Because of that, I just don't see UDI spending time trying to add support for something that 60% of homes do not have anymore (a number that's dwindling) and most do not use when they do. Financially, that simply wouldn't make sense. You could always plug your modem Into an X10 appliance module and their telephone module to reboot it

Exactly why it's important to provide information on the forums vs assuming things are simply bugs

What sensors? The Isy supports many types

Oldest to newest release. V3 is for Polisy only. RPI is incompatible with V3. You are running the latest version for the Rpi.

Well, i have done at least 30 homes with zwave devices including 2 of my own and none have that issue. Your don't want help so it's a moot point. Good luck

Since you already feel a 3 year old post is a bug (especially considering no recent posts on the matter from anyone), I'll step back. Good luck

Since you've provided zero information about your setup we can't be off much help. We could assist you if you stated how many devices, what they were, Firmware, and UI, etc. https://forum.universal-devices.com/topic/29371-zwave-tips-and-tricks/