Jump to content

gzahar

Members
  • Posts

    670
  • Joined

  • Last visited

Everything posted by gzahar

  1. I just changed out my router/access point equipment to the TP Link Omada based equipment and have been very happy so far. Only 4 or 5 months use though.
  2. If you have modified the iTach node server to receive IR, please release or provide instructions to modify for the rest of us. I’m not on PG3 yet, but it could help others now. I would be happy with Lirc or Flirc. I understand that others might like the idea of keyboard input, but that is secondary in my mind to a simple IR input for Polisy. If security or development favors one over the other, so be it. Long live IR!
  3. Harmony is obsolete. Even if you were willing to pay for the products you can currently find, we need a non Harmony solution for the future. Not to mention it does not receive IR or work with non harmony remotes. iTach in it's off the shelf form does not provide received IR signals. It will display a received IR signal using their iLearn program but I do not see an API listed for this functionality so that it can be used in the mode you suggest. Possibly someone could reverse engineer this and create a Node server. I think the Flirc idea sounds great (since they are inexpensive and I have several...); but as mentioned a driver would be needed for native Polisy support and/or a Node server (if USB s/w access is allowed).
  4. 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.
  5. 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
  6. I think the comment was in reference to your transposed 0 and 3/4's.
  7. The bottleneck is the Insteon and/or Zwave traffic, not a function of the Polisy hardware.
  8. 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.
  9. See @lilyoyo1's post above. Currently there is not a node server for Ring. It is probably seeing configuration information from your previous setup.
  10. Thanks! I had been doing this manually with Search/Replace. But looks like they just fixed this in 5.4.0
  11. 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.
  12. You should install Java from the link you referred to. http://www.java.com/getjava
  13. I would try using http (no s) and/or a different browser. Doubtful it is firewall, but you could turn off briefly to test.
  14. Fanlinc or switchlinc should work just fine as long as wattage is ok.
  15. 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
  16. It is stuck to the clear plastic case with two wires running to the PCB. You can't miss it.
  17. 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.
  18. Do your neighbors ever complain about the volume? [emoji16]
  19. In my experience, it removes it every update and you have to remember to add it back
  20. Regarding Mobilinc, you might try the UD Mobile app.
  21. 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.
  22. 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)
  23. Just to be clear. I was only quoting the info in the data sheet. I do not know if they are correct.
  24. They are separate. After logging in with ssh, use the passwd command to change the password.
×
×
  • Create New...