Jump to content

Mark Sanctuary

Members
  • Posts

    1391
  • Joined

  • Last visited

Everything posted by Mark Sanctuary

  1. Yes, the PLM is still the new guy on the block and is getting many firmware updates these days.
  2. Yeah you’re back to the communication error then. When the ISY puts up that error message it has no way to guess the level then, so it’s just giving you inaccurate info. When you get the communication issues figured out all your problems will greatly minimize.
  3. For three way ciricuts there is this post "3-way / 4-way / Multi-way Virtual Circuits" you can check out. Also here is steps for creating a three way circuit. [*:2hbzpcde]Create your "Three Way Scene". [*:2hbzpcde]Control click all three devices under "My Lighting" and drop them on to the scene. [*:2hbzpcde]In the "Confirm Move" popup window set all three to controller then ok. [*:2hbzpcde]Click on the "Three Way Scene" set all the scene levels so they are what you want. [*:2hbzpcde]Click on each switch entry and click "Copy Scene Attributes From Three Way Scene" so all buttons do the same levels. Your 3-way is ready and should look like this below. Three Way Scene _____ Switch 1 _____ Switch 2 _____ Switch 3
  4. I am not sure about this one but here is my thought; that the device may have some old settings the system is picking up on. Maybe doing device soft reset (pull the set button out 10 sec, push in and hold 5 sec) might help. Then go back to the ISY and right click on that device and do the "Restore Device". After that see if it still happens. Again I am not sure about this answer but it won't hurt to try it.
  5. It does not really matter if you’re networked well before because when adding new devices it changes the dynamics of your whole network. The 5.2 PLM is a finicky little guy. You’re going to have to remove the PLC, and re-setup you’re Accesspoints with one on top of the PLM, and the other on an apposing power phase. Then re-program your devices with the ISY. Lots of other users have gone thru exactly what you are now and the end of the story it was communication issues and PLC garbage. Setting up the ISY and PLM may be difficult at times but once you get it running you won’t look back. If you just can’t get it working I suggest you give Michel a call and he will walk you thru the difficulties.
  6. Oh I did not notice you said PLC. There are most likely two things going on here; an Insteon communication issue and your PLC is disrupting your PLM. If you have a 5.2 PLM then you will most likely have to have your Accesspoints plugged in directly on top of the PLM. The new 5.2 PLM has about 50% of the signal strength as the 4a PLMs so it does not reach out very far on its own. Your PLC is most likely not playing nice with your PLM. The PLC tends to dirty up the network and the PLM can’t deal with it. What you might do is remove the PLC from your network and then try doing “File --> Restore Devices†from the ISY. Your device links are most likely incomplete because, of the communication issue not letting them program correctly.
  7. One other request to add to this is can the program table have the white/blue background like the other tables in the ISY. It makes it easier to read across the table then.
  8. Sounds like an Insteon communication issue; do you have any Signalincs or Accesspoints installed in your setup?
  9. I think I remember that the X10 stuff in the devices is not touched by the ISY.
  10. The X10 support is only done thru ISY programs, here is an example program of how you use the X10 support. If X10 'A1/On (3)' is Received Then Set Scene 'Movie Time' On Else - No Actions - (To add one, press 'Action') Right now the ISY X10 support works correctly but, the PLM X10 support is giving some of us some real headaches. If you get X10 working well please let all know how you did it but, otherwise I would suggest that you work on the Insteon stuff first because the X10 stuff might get frustrating.
  11. You got my vote; when things stay put it is much faster and easier when returning to continue from where you left off at.
  12. This might be some good reading for this suggestion question. Unsupported Devices in Link Tables
  13. Michel what do you think about this issue?
  14. Ok I fold; I don't hold any XX.00.XX devices so I can't test it myself.
  15. While your waiting for an answer could you try right clicking on one of the problem non-keypadlinc devices and do a "Restore Device" to make sure that its link to the ISY PLM is in good shape.
  16. Click ons - are trickier than off ones because the device is going to want to do its default behavior and toggle between its “On Level†and “Full On Levelâ€. So “click on†programs will work but the light is going to first change, then it’s going to change again a half a second later when the program changes it.
  17. Making a single button device multi functional; so I got here a single button device that I want to add more functionality too, how do I do that? Easy for how many ways you can think of that button can be clicked you have options. Double click off If Control 'Master Read Mark' is switched Fast Off Then Set Scene 'Inside All Scene' Off Single click off (if device is already off) If Status 'Master Read Mark' is Off And Control 'Master Read Mark' is switched Off Then Set Scene 'Master Bed Scene' Off Double click on If Control 'Master Read Mark' is switched Fast On Then Set Scene 'Inside All Scene' On Single click on (if device is already on) Used ‘not’s for the ‘Single click on’ program to avoid having to guess the percent on level. If Status 'Master Read Mark' is not Off And Control 'Master Read Mark' is not switched Off And Control 'Master Read Mark' is not switched Fast On Then Set Scene 'Master Bed Scene' On
  18. No problem; I read my first post and left it not very comprehensive so I think its my fault for not documenting it better. I fixed the first post to read better.
  19. Rand, Forgive me but are we talking about the same thing? I just want added one of these. Next to this button. Like this example here. This way I could change all the levels for the selected controller device with one movement than a whole bunch of movements.
  20. That must mean we are close to official 2.5 release then.
  21. No problem. Forgive me if you already knew this info.
  22. If your wanting to add to that document the remaining entries (ie. Is Load, Location, Notes) you have to enter them in the device properties. To get to each device properties go to the Main tab, expand the tree to your ‘My Lighting’, right click on a device, and select properties. In this window you can add details to each device for the spreadsheet.
  23. Have you tried the "Tools --> Generate Typology" command? It gives you a html spreadsheet like document.
  24. Chris, Is today going to be a 2.4.13 beta release? If so could you update the top post with what is in it. Thanks!
  25. This is just a preventive measure because you should be able to setup your keypadlinc without them changing the LEDs for non-toggle buttons. This is only for when somehow very remote they do get changed.
×
×
  • Create New...