lilyoyo1

Other than googling your question and sifting through the results, there isn't a single source that's readily answers what you're asking. In regards to why some mfg have codes and others don't comes down to the generation of the devices (ie: 700 vs 300) and whether they choose to implement it or not. Only the mfg. can answer that last one

He's no longer maintaining this nodeserver. You'll want to contact Bob @bpwwer

Couldve reversed engineered it which is something udi said that they would not do

I've had test devices (alpha/beta) running for the last few years (prior to covid) now without any issues. Historically I haven't had any issues with insteon failures and it's a small sample size but so far I must say I'm pleased.

Believe that if you want. They've come out with new product that supports Google since Google has implemented their changes. It's one hell of a coincidence that once their dispute got heated and new products were released, it became an issue. Besides that, If it were that hard, their other speakers wouldn't run it nor would other technologies use it either.

They didn't. They're in a patent dispute

It can be manually turned on/off from the isy but no status unless queried. You can manually link the devices but if memory serves correct, you can't link via the isy.

They need to be linked together using your controller.

Then he'd have to read...i guess the date being older than the 5.3.4 didn't help either...

UDI hasn't said anything about eisy being capable of being powered by poe

Does your firmware and UI match? How are you attempting to add step by step? Are you getting any messages?

He said pg3x supersedes pg3x and pg3x will be deprecated. Pg3 superceded pg2 which is why it currently runs on polisy

His last line answered that. In addition, the software for Polisy and eisy will be the same (except for hardware capabilities that eisy has such as the HDMI cable)

I dont think there will ever be a perfect migration when it comes to zwave.....so many things are simply out of UDI's control. When you look at all of the migrations that have taken place, you're getting a snapshot of those who has had issues on the forums minus the ones who went direct to UDI for help. That means there were many who didnt. The nature of forums is to have a place to go for help so you will see all of the problems vs the those with smooth migrations. Reality is, there will always be bugs (the isy had them too). You can wait for the perceived perfect moment but due to your environment, device types, preparedness, etc. still have issues when others may not. Judging by UDI's history, the farther you are from upgrading, the more painful it will be as more and more features are added.

That says alot. Kind of hard for UDI to fix (or help fix) something when you offer zero insight.

In the eisy user guide, it states: Z-Wave The Z-Wave network managed by ISY-994 will be migrated to the ZMatter Z-Wave implementation on Eisy / Polisy. The devices in the network will remain the same, but their representation in ISY may change. Pretty much all of us here are heavily invested in the isy994 and have upgraded without issue. It's been years since ive installed a 994 in clients home so im not as concerned about upgrading those customers should they ever call. The way I see it, if they want something newer, then it would be a new installation anyway that they're paying for. Support is for like systems not brand new ones. All of mine are beyond warranty swap out and I have enough ISY's to get through my 5 year guarantee so Im good. The point im making is that this may not be as big of an issue that you're thinking it is for the long term outlook. With that said, it would be helpful if you would state exactly what 3rd party integrations you are having problems with (or thats breaking). How can anyone fix anything or make something better if they dont know? Continuously posting on multiple pages without specific information means things wont get fixed. Afterall, UDI is beholden to ensuring devices work within their ecosystem. They may work with partner systems or developers to ensure compatibility but if they dont know exactly whats broken, they cant fix it. This goes back to what I said before- what exactly gets broken...Its such a broad term when other nodeservers dont have this problem or to the level that you state.

Are you voluntarily upgrading your clients to eisy? If they're not asking for upgrades, it seems like a money losing proposition for something that's already in place and that they're happy with. Have you tried, updating what each device is called to their original name and then re-saving the programs? I haven't upgraded to eisy yet so I don't know (it's had too many issues for me)?

Thats a very open question. It could be many different reasons. Give some insights to anything that may have changed or happened in the last 24 hours such as recent firmware updates, lost power, etc.

I don't know what other post you're talking about but it's these situations why you should post your issue on only 1 post vs multiples. I don't have any answers from you outside of factory reset and making sure the lock is within 3 feet of your controller when removing and adding. I assume your UI and firmware match and that you are on the latest firmware. Unfortunately schlage is notoriously finicky with automation systems. Judging by the support you've received, i would've moved on by now to a competitor without the baggage such as Yale

You mentioned using eisy not HA. Their setup is probably different than Udi's which is why it worked. Glad you got it working with your system

I know eisy has Bluetooth but I haven't seen any noderservers that take advantage of it. I suspect whatever device you're trying to use would need a specific nodeserver so that the eisy knows how to interpret the information it was receiving

The free nodeserver just allows you to control your speakers and provides status of your devices. The st Sonos version adds your playlists, favorites, and voice TTS

No it is not. Parameters are not guaranteed. Each mfg. can choose to use them or not use them at all.

Are you certain that this device has parameters? If there are none found online and the mfg. cant provide any, then there may not be any available

The keys that the system set with the device to control it was erased when you factory reset the device so you'll need to remove the device and re-add. It's akin to encrypting a micro SD card on your phone. If you factory reset the phone, your data can't be recovered on your drive due to the key being broken. I don't have the new matter board so things may be different now but historically, that's how it's been with multiple types of systems.