gzahar

In the device properties section, select Show advanced drive properties. A disk symbol will appear right of the device selection box.

I had an issue with Polisy where the SSD went bad and any changes made would revert after any reboot. Sounds similar.

IR receive is not built in to Polisy or eisy. IR transmit was not included in ISY994, so as @lilyoyo1mentions, whatever solution you used for transmit before should work the same with the newer boxes. This can be done with network resources or node servers and itach devices, etc. Regarding IR receive, I have looked for external solutions and have found a number of add on devices that could work. But in the end of my analysis; the cheapest (if you already have an ISY994IR) and easiest solution is to continue using the 994 for IR receive and relay IR activity to eisy (or Polisy) using the rest interface. This will most likely add additional delay to IR processing, so this may affect your use case. Ideally, someone can/will make a node server that utilizes an IR receiver plugged into the USB port on eisy (flirc, USBUIRT, etc.). This assumes node servers have access to the USB ports and that may be a big assumption.

If you have a VPN connection to your local network, you can control (restart) PG3 and individual node servers through the normal web page UI (<ipaddress>:3000). I'm sure you could also do this using port forwarding, but that is generally not recommended.

@bpwwer After clicking the authenticate message, Google responds with the following message: Access blocked: Holidays Google Node Server’s request is invalid You can’t sign in because Holidays Google Node Server sent an invalid request. You can try again later, or contact the developer about this issue. Learn more about this error If you are a developer of Holidays Google Node Server, see error details. Error 400: invalid_request ----------------------------------------------- More about this error: Access blocked: Third-party app is using an unsupported OAuth method Google has safe ways for users to sign in and share their Google Account data with third-party applications. To help protect your account, Google sign-in requests are blocked from apps with less secure authorization methods because they’re more vulnerable to phishing and app impersonation attacks. Learn more about how your data is shared with third-party apps App sent an invalid request If the app is blocked because it uses an unsupported authorization method, you may be directed to an “Error 400” page that says “Access blocked: App sent an invalid request.”

The parameters can be updated using the Notify Sensor node that was created when the device was added (I have a 700 series ZSE40, so it is possible that node may not be created on 500 series). Or right click a node and select Z-wave -> Set Configuration Parameter.

Did you enable NWI/NWE in the ISY?

Based on this comment: 3) Both the controller and responder are linked to the ISY at the same security level (i.e S0 security or no security) I think both of your devices need to be security=S0 or both security=none. You have one device with none and the other at S0. I'm not that knowledgeable on Zwave security, so it's possible these are the same, but I didn't think so.

Other than this? "Anyway, this one has worked well for over 2 years without any issues and mounts easily in corners:" https://www.amazon.com/gp/product/B01MQXXG0I/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

I think the comment was in reference to your transposed 0 and 3/4's.

The bottleneck is the Insteon and/or Zwave traffic, not a function of the Polisy hardware.

I have one 994 and one IoP. Not sure if that qualifies as 1 ISY or not per your comment. Here is my experience with that environment. 1) 994 on 5.0.16c. Download admin.jnlp from IP addres of 994. When you started admin.jnlp first time it created shortcut that allowed you to go straight to login screen w/o selecting anything from finder. I think a blank finder window opened in background but still went straight to login prompt. 2) 994 on 5.3.4 (haven't used anything between that and 5.0.16c) did the same thing except it would only work the first time to get to login screen. Any attempt after first login, would error out with no connection or something like that. Unless you cleared java cache and re-ran admin.jnlp to get a new shortcut. Again would only work for first login attempt. Obviously this is much more work than Launcher and selecting which ISY to login to. 3) IoP on 5.4.0 (I think earlier versions of IoP worked similar to 994 on 5.0.16c, but don't remember). Download admin.jnlp from IP of IoP and saved admin.jnlp file. Running this file does not create a separate shortcut but goes straight to IoP login screen (with empty finder window in background). This is easier (in my opinion) than starting Launcher and then selecting which device to login to.

See @lilyoyo1's post above. Currently there is not a node server for Ring. It is probably seeing configuration information from your previous setup.

Thanks! I had been doing this manually with Search/Replace. But looks like they just fixed this in 5.4.0

For IoP you can use: http://<IoP IP:port>/admin.jnlp This will download the admin console to your computer. You can then just run that file directly w/o going through the launcher/finder. (goes straight to login screen) This use to work for ISY, but no longer works on the latest releases. Remember that you will need to redo this when a new version of the IoP firmware/admin console is released. Which is probably why they want people using the Launcher instead.

You should install Java from the link you referred to. http://www.java.com/getjava

I would try using http (no s) and/or a different browser. Doubtful it is firewall, but you could turn off briefly to test.

Fanlinc or switchlinc should work just fine as long as wattage is ok.

It is the Zwave Learn menu item. You might want to read up on Zwave secondary controllers before utilizing that. Here is a very basic article about a different controller but should be relevant. https://community.smartthings.com/t/faq-zwave-secondary-hub-basics/201631

It is stuck to the clear plastic case with two wires running to the PCB. You can't miss it.

If it turns out to be a bad device (which it sounds like), I would keep it as as spare. As hard as they are to get now, you could always cut the leads to the piezo "beeper" if you had to.

In my experience, it removes it every update and you have to remember to add it back

Regarding Mobilinc, you might try the UD Mobile app.

There is a Zwave setting in ISY to turn on/off the ability to add devices using security. Make sure that is set correctly. But the ISY usually tells you this needs to be changed when it is not set. So probably not the problem.

Do you have a large Zwave network that reaches your test location? I would test near the ISY by using a paper clip (or similar) to short across the leads. (or damp paper towel)