Network Resources Post EISY Migration Won't Send

[gages97]

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?

 

[gages97]

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

 

Edited May 21, 2023 by gages97

[Geddy]

This is from the wiki: 

Quote

Network Resources

All Network Resources will be migrated seamlessly, however, you will need to open and save each one individually.

Hopefully that's what you went back and read again. 

It's from this section:

https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#What_to_Expect_During_Migration

 

[gages97]

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.

 

[MrBill]

16 hours ago, gages97 said:

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.

Why should Doc's be repetitive?   If anything perhaps a migration Troubleshooting section could be added, "if you're seeing this then see step __ of the migration instructions."

[gages97]

Agreed, that would be helpful and potentially calming.

It's a big upgrade and no going back.........

Edited May 23, 2023 by gages97