lilyoyo1

OTW= over the wire

If you purchased it new last year on Amazon then you have the 500 board and can upgrade to 5.3.4. The missing light confirms it's 500 series

The ISY can still be a secondary controller. You just have to know what you're doing to make it happen.

I assume you meant zwave encourages the use of multiple devices not hubs as its the devices that builds out the network not the hubs. Multiple hubs can be used in a single install by adding other hubs as secondary devices. Thats not something an entry level person should attempt however unless they are willing to settle for a huge learning curve.

Spoke to soon. While I'm able to get in now, i do not have the portal. Manage modules shows all up to date but does not show the portal in help>about. No portal tab either under the Configjuration tab. Added polisy to my portal account. Shows as my preferred Isy but is currently offline

That did it. Thank you for your help. As always, you're the best

I had already tried the factory reset but when I went into polyglot every still showed. I deleted everything but wanted to make sure polisy was cleared too. Thank you Cloud works as far as pulling the admin console up. The default password worked.

@Michel Kohanim I am unable to log into one of my polisy's. It shows up in the launcher but nothing happens when I click on it. SSH'd into it and ran the different updates which there are none. Stopped and started UDX and ISY and its still a no go. Also is it possible to sart all over with a clean slate as if this polisy had never been used? It was once connected to my isy but I dont want to port the system over (I want to do a fresh install). uname -a=13.0 release P6 Free BSD 13.0 release p6 #16 pkg info udx= 2.5.3_36 pkg info isy=5.3.0_26

Im reading into what the op was referring to from the original post which deals with what parameters are. If your referring to something different then we are talking about 2 different things. Any database not designed to take into account future devices and changes is one set up to cause issues. As someone who's ran f500 company systems, I would think you would know this. I dont have any ideas on how to do this database as I think its unnecessary and there are much simpler ways to accomplish most of what was spoken on. Obviously if others feel different, thats their feelings and I have no issues with them or anyone pursuing what they feel will make the ISY a better system. You say that you have the knowledge, experience, and desire so feel free to pursue it instead of simply talking about it. Thats the part that I speak about. People constantly saying what someone else should be doing without taking any amount of time to see what it takes to accomplish any given task.

Whoever you were implying should have a database is irrelevant. I did assume you meant UDI since you did not volunteer in your initial response and you said UDI should harness the community. If you werent referring to them you could have easily stated it was something you were looking to work with UDI on or take on for yourself. With that said it doesnt matter who maintains a database, its still an extremely daunting task that requires a tremendous amount of manpower (man hours) to setup and maintain. The only thing worse than no database is a poorly maintained database with incorrect/out of date information. Take a moment to peruse the fibaro's manuals for their motion sensor alone (1st and 2nd gen). Then extrapolate that across thousands of different devices and firmwares (different firmwares support different things). So yes, while the community can add information to it, who will ensure it is the correct and up to date information (without losing or confusing with older devices). Lets say a database of every zwave device made is maintained and keep up to date with zero errors. How does that make it easier to find things than a person simply downloading the owners manual from the manufacturers website to their computer? In regards to my non techie comment, read for context. It was a statement made towards another one implying that most of the general public wouldnt want to invest in the time needed to learn and setup an ISY/Polisy. The fact is, most people who use the ISY/Polisy will have some technical ability. Most of the non technical general public will automatically gravitate to easier systems such as smartthings, google, amazon, etc. Nothing about this post has anything to do with teaching someone professional methods. Since you decided to mention that, we could talk about some of the things professionals do to make their installs much better. One of the main things professionals will do that most do not is take the time to learn about their craft and the devices they plan to install. One of the simplest methods to do this is to read the manuals (which if this post is any indicator doesnt happen). Many people will create overly complex solutions to the most basic of problems and for what?! Another is they focus on installing a limited number of devices. This allows them to focus on a few select devices and know them in depth. Trying to install a multitude of like devices is counter to that as the likelihood of being highly knowledgeable about the product goes down the more they use. Next, they just dont use the product. They'll test it. Learn its strengths and weaknesses so that they use it in the best manner possible for success vs. trying to fit a round object into a square hole. This includes but not limited to taking the time to learn all that you can about the chosen technology. If people took the time to do so, they would understand,the difference in how zwave handles different device properties via different mechanisms. If people do so, some debates such as this would be moot as they would understand the ROI on trying to build and maintain a database along with the additional coding needing to try to find the matching parameters.

Only you can answer why one works better than the other for you. Then again, depending on nodeserver, you may only have the option for cloud based or local based only. Most on here prefer local access to their devices (me included) so they would shun cloud based nodeservers since those require internet access. Even if you have perfect internet, who's to say someone else wouldn't have problems with their server? There are plenty of recent threads talking about the differences between pg2 and pg3 so I'm not going to rehash easily found information. Basically, pg2 is old and pg3 is new/up-coming. Most development is being done on PG3 so there's really no point in worrying about pg2

You didn't answer the rest of the questions

If you do not use zwave then you must update to 5.3.4

Firmware, UI, distance from isy, and process used to enroll?

What are you trying to get to work

Does your UI match your firmware? Did you exclude the device first? How close is the device to the isy

I never took the Isy as a device for non tech users. The biggest mistake i see people make is not taking the time to read the manual for the devices they are just getting into vs. it being an Isy issue

And who's going to manage this database and the 10s of thousands of parameters that could potentially be out there? Everyone says what UDI should and could do but yet I bet not a single person has looked into seeing what it would take for this to happen. How many have taken the time to read up on what it takes to program for zwave or looked deeper into what goes into setting up their device? Not even the op took the time to read the manual to see what was going on with his device before posting about his issue. However, he's quick to be on here saying how things should be done. A simple Google search (or owners manual search) on aeotech's website would've provided the answer. But that was too much work. Yet everyone expects UDI to spend countless time, money and effort to try to program in a database of 10s of thousands of potential parameters for thousands of different devices for something that takes an individual 5 minutes of effort. No one wants to do any research or listen to those who has but have all sorts of ideas of what others should be doing (but won't do for themselves). And people wonder why prosumers are being abandoned by companies. They have the most to say but no willingness to take the time to understand things how things work.

You assumed wrong. Zwave alliance does not define that information.There are no such thing as basic Parameters. Any that you see is what the mfg. decided on. It's easy to research to see for yourself. Take a look at old and new Jasco/GE manuals. You'll see some of the same parameters doing different things for like devices. Ditto for fibero and aeotech

With this statement, I assume you do not plan on ever buying another car, computer, phone, tv, house, etc? Everything in life gets upgraded at some point. 3 controllers in 10+ years is still less than a grand.

Good question. I took it to mean that hubitat provides information to the isy about the device and it's state but doesn't know what the Isy does. Meaning Isy can see hubitat devices but hubitat can't see Isy devices

Id upgrade to the latest 5.3.4. remove the device from the Isy and re-add it to see what you get

Most likely you aren't experiencing issues because you aren't doing anything complex with your setup. If you were, you'd already be facing serious issues with your system. Alot of veterans here focus on automation vs control which is typically what new people are doing with their system (though they'll say they're automating. This is why Oberkc tried to warn you. Things are great now but won't be long term as you expand your knowledge and try to do more. When you look around, redundancy doesn't come via disparate systems that do not play nice with each other. Redundancy comes from built in controls to allow one to continue what they are doing should something fail and allow them to get back up quickly. Those redundancies (while possibly less capable) generally do not negatively impact the main system. You claim redundancy but how are you actually accomplishing that other than using a fancy word? Should your hub fail, it's goodbye Alexa/Google until you get another hub or set it all up again on another system. Sure, your Isy timers and app may work but you still have a lot of work in front of you to get going again. Once you replace your hub, you'll end up with half links in your devices which can potentially slow down your devices as they try to talk to the old hub which is no longer there. Yes there are ways to work around that if you know what you're doing but there's no quick and easy fix w/o taking shortcuts which only hurt you long term. The same applies If the Isy fails, you have nothing again. You have the hub app and voice control with no timers. Once you replace your Isy, you'll end up corrupting your hub links once again causing you more work to get back up and running. Oberkc, is only trying to keep you from setting yourself up for failure. As you start doing more, and the headaches come, you'll find that you have zero help. Insteon can't help because of the Isy and UDI can't help because of the hub. Forum help will be non existent as well. With 81 views and 2 replies, no one wants to wade into this since they already know the long term outcome. Good luck. You'll eventually need it

300 or 500 board? Firmware AND UI of your ISY

Experience is the best teacher. Just like others who've gone through the same thing...only to come asking for help as stuff starts breaking down and going wrong. He'll have to learn for himself