Jump to content

lilyoyo1

Members
  • Posts

    7177
  • Joined

  • Last visited

Everything posted by lilyoyo1

  1. Sounds like it works outside of the Isy so it must be something you've programmed inside of it. My guess, is the button is in non toggle off mode and needs to be put in toggle mode
  2. Did you do what I said in regards to troubleshooting? The Kpl of obsolete so you may be better off just saying it out for a new one
  3. What's the model number
  4. Let me get this straight, you have to hit the C button on 2x in order for the Kpl C button to turn on? If this is the case, factory reset the Kpl. Turn on the C button. Does it still take 2 taps to make the button come on? If not restore the device in the Isy. Turn on the C button again. What happens?
  5. What are you using to turn your amp on or change inputs? Depending on setup, even if you run those same things again, it may not effect anything and start up the way you like I'm regards to actually program, you could make 2 folders and drop your programs in. 1 folder will only run if the variable is at 0, the other if the variable is set to 2. Put what you want in the corresponding folder
  6. 2 plms exhibiting the same exact issue... Especially 1 being brand new= highly unlikely to be a PLM issue.
  7. After you did restore PLM, did you also do a restore devices?
  8. I'm assuming you didn't read @MrBill warning about programs and the information in the upgrade post about upgrading! You have to update your programs as there is a difference with how 5.0 handles them vs 4.0. That's where the yellow is coming from Make sure you cleared your Java cache and use the launcher as well.
  9. https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP.2FRouter_-_Can_no_longer_access_ISY
  10. There's minimal delay in starting the scene but a delay in the whole program running since I separate each room with a 1 second wait. This is to ensure all communication has occured prior to moving on to the next room. Typically, I start my program with the most important room and end it with the least important. For example, if i hit my away button in the kitchen on my way to the garage (in the evening), it'll turn on the hall light, unlock the door to the garage, open the garage door, turn off the kitchen, master bedroom, etc. Rooms that we generally do not use such as the dining room and scullery are processed last since the likelihood of them being on are low. The same applies to my goodnight. Hitting it in the living room will dim my lamps, turn on the step lights, and turn off the fan and other lights. Then the kitchen, and other rooms with the least used rooms being last. The more things that happens in a program the longer it will take. A wait between each one actually helps you more since you don't have to worry about collisions and so forth. Running 20 scenes with a 1 second wait will be more efficient than trying to run a single program with 100 different devices.
  11. Being such an old system, it may not support newer devices since the firmware has not been updated for it. If it does work with the 99i, factory reset the device and make sure that the ID number was typed in correctly. I prefer to use start linking and pressing the set button so that I don't have to worry about typing something in incorrectly.
  12. 1 way to save link space would be to link basic multi-way switches together outside of the Isy. Obviously if your changing brightness levels throughout the day or other programs, you would want to avoid this.
  13. While this nodeserver is great for seeing what your isy has, basic device and scene count is a poor way to figure out link count. For example, an eight button keypad is 9 links but still only 1 device. A 2477d however is 2 links but 1 device. If your house had 50 eight button kpls, you'd have 450 links while a house with 50 dimmer switches would have 100. That's even before you get to scenes. Using the 2 houses described above, 1 scene with 20 kpls will show as 1 scene but the links would then be maxed out while 1 scene with 20 dimmers would still have space
  14. Not necessarily. Link count is more complicated than a simple 1 to 1 comparison. Outside of kpls, most insteon devices do not use many links (1 to 2 depending on device) Since you're close to the PLM limit, it does help to use zwave devices since it's on a different board.
  15. Zwave is not insteon so you are not adding to the PLM link count. That's why it has its own separate board. To eliminate the extra nodes, simply right click on them and delete. You'll also want to go to the zwave tabs and choose freeze additional nodes (something along those lines) once done.
  16. That thing is pretty much worthless beyond being a paperweight. Its been discontinued for years and hasn't seen a firmware update in over 5 years. Definitely wouldn't work with the launcher. If you do not have a PLM hooked up to it, it will be in safe mode.
  17. You shouldn't use a dimmer on non dimmable bulbs.
  18. You could with a program. You would write it like you stated. I would add a delay to account for the device turning off however. If switch is turned off Then wait 2 seconds And turn switch on 10% You'll probably have to play around with the percentage to get it to fit your needs
  19. What happens when you control the scene from the isy directly
  20. Thats a sign of a poor network. I would still take Asbril's advice as it doesn't take much to knock a poor network down and it could potentially affect future automations you may attempt to do. What you are experiencing is akin to your wife yelling at you from the other side of the house. You may hear her and respond most times, but there may be some moments where you don't such as other things creating noise
  21. Currently is not supported. While there's no guarantee a developer will take this on as a project, it'll help your chances if you could find out if they have an open API to use to develop against. If there is an open API, i would post that. The more you assist with providing the necessary documentation, the heater the chance someone will be in helping you
  22. I think the last 2 posters are trolls.
  23. The steps for port forwarding varies when it comes to different mfg. and setups (ie:double Nat), the mfg. of your router should have that information on their support page or a Google search for port forwarding with you router model number should give you the necessary links (possible videos) to properly set up port forwarding. In regards to the isy, I would recommend using their portal service as it negates the need for port forwarding
  24. Surprised with multiple break-ins in the neighborhood they didn't do more... especially with it on video. The Elk alarm has native integration with the isy and its the one i would recommend. DSC can be added via nodeservers but I don't know much about that one.
×
×
  • Create New...