Get Started (v1.3)

[Michel Kohanim]

Hello all,

To get started:

- Find the IP address for your Polisy 
- Click the Add button on the ISY Launcher
- Enter https://ip:8443/desc where ip is the IP address you found in #1. This should put polisy in your Launcher
- Click on the Polisy | Admin Console (Cloud or LAN)
- If migrating from 994, simple restore your backup on Polisy (File | Restore ISY)

In this version, INSTEON is disabled by default:

- Admin Console | Configuration | System
- Check INSTEON Support checkbox
- If you have this Z-Wave dongle, Check Z-Wave Support checkbox
- Click on the Save button and then Reboot button (restarts the ISY service)

Fixes and enhancements in this build:

1. If INSTEON is enabled (see above), ISY will try to find a PLM attached either to a USB port or the DB9 port
2. ISY Portal activation is now identical to that of ISY. Since you do need ISY Portal for node servers to work, please start a 30 day free trial of ISY Portal for your Polisy. Node server functionality remains regardless of the status of the license
3. Back off delay in case we cannot connect to ISY Portal

With kind regards,
Michel

[MrBill]

5 minutes ago, asbril said:

I think that I successfully executed the sudo commands (I did not get any error message during update and upgrade processes), but where would I see the difference ?  Is this supposed to give access to ISY on Polisy ?

Run ISY launcher and see if you have a new entry in finder.....

(mines is the 4th line...) then open the admin console on that one if you do.

[bgrubb1]

@Michel Kohanim   anything I can try to get around the 

 

 ISY automatically discovered at http://192.168.0.27:80 however the username and password need to be set in the settings menu.

I can access the ISY on Policy via ISYFinder  Once I try to set the ISY password on Polisy the ISY still runs but doesnt respond to commands and Polisy URL will not connect until I restart the ISY

...Barry

[Michel Kohanim]

@bgrubb1,

Please checkout the latest release. The reason you have that issue is because Polyglot does not support self signed certs. Please use http/localhost/8080.

With kind regard,
Michel

[bpwwer]

5 minutes ago, asbril said:

No I don't have that 4th line

Did you start the ISY software on the Polisy?  I don't believe installing it starts it automatically. You can check if it's running with:

sudo service status isy

If it's not running, you can enable it and start it with:

sudo service isy enable

sudo service isy start

[larryllix]

Is there anything shared between the polisy and old ISY? like variables or some way to cross data and/or controls?

If not, can cross NRs be used to manipulate variables for lighting commands or what not, yet?

Sent from my SM-G781W using Tapatalk

[MrBill]

@asbril See Michels linked post below.  You need to manually add it to finder after you start ISY launcher:

 

[BamBamF16]

When I execute:

sudo pkg install isy 

I get 'no package available to install matching 'isy' have been found in the repositories. 

 

Thoughts?

 

Thanks, Jeff

[Michel Kohanim]

@bambamf16,

You need to upgrade to 13. What's the output of

uname -a

With kind regards,
Michel

[BamBamF16]

When I tried it previous I got an error with uname -a.  Now it shows 12.2.  I executed the update/upgrade combo though.  What did I miss? 

Thanks, Jeff

[Goose66]

What are the PLM options? Just USB or will a serial PLM work?

EDIT: Never mind - can't buy either, so it doesn't really matter.

[MrBill]

37 minutes ago, Goose66 said:

What are the PLM options? Just USB or will a serial PLM work?

EDIT: Never mind - can't buy either, so it doesn't really matter.

Either will work.  for the 2413s you need the original cable that came in the box.

2413u is showing in stock on SH, I just rechecked.  (a number of people have ordered this week tho, including me).

[Goose66]

Ah, I swear the 2413U showed "sold out" when I posted that post, but it does now show "in stock."

[gzahar]

I am on version 13: FreeBSD 13.0-RELEASE-p3 #11 releng/13.0-n244752-b368bb75bad

ISY service running: isy is running as pid 1098

But response from add URL in Launcher (http://192.168.2.12:8080/desc) is 'Not Found'.

Tried https port also with same results.

Not sure where to go from here.

[MrBill]

11 hours ago, gzahar said:

I am on version 13: FreeBSD 13.0-RELEASE-p3 #11 releng/13.0-n244752-b368bb75bad

ISY service running: isy is running as pid 1098

But response from add URL in Launcher (http://192.168.2.12:8080/desc) is 'Not Found'.

Tried https port also with same results.

Not sure where to go from here.

my launcher entry is https://<ip.addr.of.polisy>:8443/desc

[gzahar]

2 hours ago, MrBill said:

my launcher entry is https://<ip.addr.of.polisy>:8443/desc

I know I tried the https port last night and it wasn't working.

Today it is.  Thanks for the push to try again.

Not sure why the http (8080) connection is still giving 'not found' response, but will use what is working.

[MrBill]

27 minutes ago, gzahar said:

Not sure why the http (8080) connection is still giving 'not found' response, but will use what is workin

I hadn't tried http and 8080 yet, but I just did and it worked for me.

[gzahar]

After starting admin console and enabling Insteon/reboot, I'm back to 'Not Found' on both http & https.

Thinking it might be firewall or java related, I tried from another computer.  Same outcome.

Maybe another wait will clear it up....

[Michel Kohanim]

@gzahar,

Thank you. Thanks to a lot of help from everyone, we found an issue with the FTD driver. I am hopeful that we can have a fix by mid next week.

With kind regards,
Michel

[gzahar]

On 7/21/2021 at 2:36 PM, gzahar said:

After starting admin console and enabling Insteon/reboot, I'm back to 'Not Found' on both http & https.

Thinking it might be firewall or java related, I tried from another computer.  Same outcome.

Maybe another wait will clear it up....

Found the problem.  (I think)

If anyone is using the Hue emulator nodeserver and left the default configuration at port 8080, you will need to change it to something else.

Not sure why https port 8443 wasn't connecting reliably, but may be due to traffic from hue emulator on port 8080 locking up isy service?

But able to connect on both ports now, after stopping hue emulator nodeserver.

[Bumbershoot]

14 hours ago, gzahar said:

If anyone is using the Hue emulator nodeserver and left the default configuration at port 8080, you will need to change it to something else.

 

The Ecowitt nodeserver has the same issue (using port 8080).  I changed the port and everything works as expected.  The developer has been notified.

[gzahar]

3 hours ago, Bumbershoot said:

The Ecowitt nodeserver has the same issue (using port 8080).  I changed the port and everything works as expected.  The developer has been notified.

I ended up, changing the ISY to use port 8081 and then re-enabled Hue Emulator.

[Bumbershoot]

3 hours ago, gzahar said:

I ended up, changing the ISY to use port 8081 and then re-enabled Hue Emulator.

I did the opposite, changing the Ecowitt device and nodeserver to use port 8082.  Either method should work.  This port conflict between nodeservers and the ISY is something that UDI should be aware of as they prepare PG3 and the Polisy/ISY for release.  Flagging @Michel Kohanim and @bpwwer as a courtesy, though dollars to doughnuts they know all about these port conflicts...

[Jimbo.Automates]

4 hours ago, gzahar said:

I ended up, changing the ISY to use port 8081 and then re-enabled Hue Emulator.

The latest version of the HueEmulator allows changing the port number, just for this reason.  Previous versions allowed you to set it, but it didn't actually work.

[gzahar]

2 minutes ago, Jimbo said:

The latest version of the HueEmulator allows changing the port number, just for this reason.  Previous versions allowed you to set it, but it didn't actually work.

I was aware of that (that it could be changed) and it was my first thought, but it seemed more trouble to reconfigure the components using the HE nodeserver than to just change ISY port.