gages97

I have a stock EISY with no addl node servers. Not clear to me what this means. Happy to pay foe any enhanced functionality just not clear on what needs to get done.

I am on EISY. If we upgrade to the latest version of UD Mobile, based on the updated notification module we rcvd the email about today https://www.universal-devices.com/notifications/ Will anything be impacted?

Whew, thought I was losing my mind..... What's the best way to report something like this if it happens again?

Just started working w/o any actions from me. Was down for me from EST 7:15am - 8:25am

My setup has been working for months w/o issue. This morning, subscription won't start for UD Mobile or when I access my EISY remotely (local is fine). Control of devices from Portal works and EISY shows online in Portal. I just can't the subscription to work so can't use UD Mobile or remote cloud access.

Agreed, that would be helpful and potentially calming. It's a big upgrade and no going back.........

Correct. Doco could be a bit more clear as it states in the What to Expect During Migration section to migrate the network resources, but then post migration, doesn't mention it. Note, if you don't resave and do a bunch of testing that use the network resources, the eisy will slow down a lot as it waits for the timeouts, and it appears that there is something not right with the box, so def want to get this right. One thing I noticed, for 3rd party devices that access the eisy (rti remote as an example), the login port is now 8080 and not 80.

Reread the migration instructions. I changed back to 443, then saved each one and now it seems to work. 8,443 is local, 443 must be for the portal

DId my isy to eisy migration. Everything looks pretty good. I can not get the network resources working for notifications. w/ 994 it looked like https to my.isy.io port 443 w/ eisy it wouldnt work, so I changed to port 8.443 but I can't get the messages to send Any ideas?

is the attached the latest?

New EISY just arrived. I did the module update. How do you know when it is done? Any dox on what the latest versions of all modules are?

I saw the Zmatter Board in stock today so I grabbed one.

I was able to use the Silicon Labs PC Software w/ a Zooz 700 stick to do firmware updates to the Zooz water sensors. A bit tricky but it can be done. In the end I just couldn't make Z Wave battery powered devices as reliable as the Heartbeat on the Insteon devices for status indication.

Right, but how do I properly reset the 994 and the serial PLM so they no longer have links to the original deviceS?

Preparing for my 994 to EISY upgrade. W/ a new EISY and USB PLM, after I run the upgrade process. What is the status of the 994 and old PLM? Do I factory reset them and then can use as a separate system?

At this point I am getting rid of the few Z Wave devices I added (water leak sensors) and replacing w/ Insteon (now back in stock). Too many issues w/ various brands re features and reliability.

Guess that is why Maybe I am being too hard on z wave. But it is really hard to like these class of devices after being spoiled by Insteon simplicity and reliability....

In thinking about this, I don't recall ever discussing a firmware update on an Insteon device. Is it not a thing at all in the insteon world?

TY, I will be ordering my EISY as soon as it is back in stock! In this video they reference an export from the primary control to a 2ndary controller and then updating from the 2ndary controller . Is this a Homeseer proprietary thing or a Zwave std thing?

So what is the current procedure to do OTA updates for Zwave devices? Do I have to use a 3rd party tool like Silicon Lab PC Controller or HomeSeer Z-Flash. Can those tools import the config from the ISY? It appears w/ SIlicon Labs you have to exclude from 994, include on PC Controller, update, exclude on PC Controller, include on 994, which is less than ideal.....

or enable push notifications to the UD Mobile client. Vtext starting giving me problems a few weeks ago, so I made the switch.

I have deployed many of these on my 994, few quirks but overall works well. There are some old threads around here that address the details. The Zooz zwave water detectors also work well.

I recently starting having this issue where the ISY will sometimes show up and sometime won't (worked with no issue for many years). This must be some type of network discovery issue. Does anyone know how the IoX finder "sees" the ISY?

I see in one of the examples the ability to use a variable ${sys.time} Is there a variable for the device state that can be used versus hardcoding the text On or Off?

OK, so on / off logic for now. Again, overall a very nice solution for notifications.