Jump to content

Michel Kohanim

Administrators
  • Posts

    26777
  • Joined

  • Last visited

Everything posted by Michel Kohanim

  1. Hello gregoryx, First of all, I would like to hear about your RL's weirdness for, using programs instead of scenes, is usually not very efficient. With kind regards, Michel
  2. Hi Rich, Perhaps it would be a good idea for you to contact our tech support (if you have remote access enabled) and let them walk through it with you. With kind regards, Michel
  3. to_lighter, Thanks so very much. I am going to contact you shortly for next steps. With kind regards, Michel Hi Michel, Your description of the communications issues exactly describes my issues. My installation: 4 access points PLM firmware E.DC.9 v72 PLM has 840 links. I have four Filterlinks for lamps/etc where I was worried about noise The Switchlinks are v.35, Keypad links are v.2D, lamplinks are v.33 I don't know the count of my devices, many dozen. All of the equipment was purchased recently. Cheers!
  4. Hello gregoryx, Thanks so very much. Would you be kind enough to describe what you are experiencing and whether or not it's isolated to some devices only. With kind regards, Michel
  5. Hi Steve, The programs will not run if they have been tagged with an "unknown device". So,what you are experiencing is accurate. To make this process seamless, please use the Find function and re-save all those devices that you have removed and readded. With kind regards, Michel
  6. Illusion, Thanks so very much for the feedback and it is already on our list of todos. RLIKWARTZ and huddadudda, First of all, I'd like to apologize for the inconvenience. This endeavor must be quite frustrating and we are doing everything we can to find answers. Now, as far as answers: 1. Burak's issue is completely unrelated. That bug has to do with ISY becoming 100% unresponsive 2. We have found the following pattern of issues: a. Newer SWLs/KPLs do not work reliably in scenes. This is not i1/i2 related since restoring them in either mode has no noticeable impact b. Newer LampLincs/ApplianceLincs (v31+) have related scene issues where they turn on with a noticeable delay. Restoring has no impact c. RemoteLincs eat up the battery if programmed in i2 mode ... this has been identified by SH and fixed d. In large installations, it seems that links at higher addresses do not report device statuses. We have not been able to reproduce it since we do not have a very large installation For 2, we are working very closely with SH to identify the root cause. I can assure you that SH is working diligently on resolving all these issues. As we all want a reliable system, may I humbly suggest that, collectively, we help SH in resolving these issues? This exercise will entail the following activities: 1. Sending one or two of your troubled switches to a designated person at SH and getting replacement units 2. Describing at high level your topology ... the number of access point, signalincs, filterlincs, devices, and your PLM's firmware version Your continued feedback, help, and support is very much appreciated. If you are interested - please send me an email (tech@universal-devices.com) with your contact information. Thanks again for all the great feedback and information. With kind regards, Michel
  7. Hello upstatemike, I tested the same PLM version and it's working fine here. Of course, I don't have as many devices as you do. What I did, though, was to add more tracing and debugging in the hope that we can find something. We should have a build soon. With kind regards, Michel No, there is nothing at all in the Event Viewer. I can see the traffic generated in the flashing LEDs of other Insteon devices repeating the signal but there is NO entry in the Event Viewer at all. It seems that the PLM simply does not pass anything on to the ISY.
  8. Hi Steve, I would love to do that and thanks so very much. The only problem is that the motion sensors should be put in programming mode other wise we cannot communicate with them. If possible, would you just capture the Event Log for the ones that do support i1 and then the Device Link Table (not ISY Link Table) for each. I would sincerely appreciate it. With kind regards, Michel
  9. Hello lloverin, Would you be kind enough to do the following: 1. Tools->Diagnostics->Event Viewer (Level 2) 2. Link Management->Link a ControLinc 3. Enter the address Please send event viewer log to support@universal-devices.com. Please put "http://forum.universal-devices.com/posting.php?mode=quote&p=16492" as the subject. Thanks and with kind regards, Michel
  10. Hi reakhavok, We still do not have any TriggerLincs but, theoretically, the answer is Yes. Do you already have a TriggerLinc? With kind regards, Michel
  11. Hi Steve, Wow. Please do NOT tell me this!!! You are saying that you have some motion sensors that actually let you program them in i1 and then read the database links in i1? This will be unprecedented and something that I had received assurances for its impossibility. Are any of these Beta units? With kind regards, Michel Michel, I tried as suggested. Some devices use engine i1 and do finish restoring. I check and found links in the device tables. I tried again 4 times with another Version 1.0 and it says using i2 but I always get writing links failed. I haven't checked all of them but I have version 1.0B on some. I'm wondering if the version difference have something to do with this.
  12. Hi Robert, In the next release we are going to revert to i1 for RemoteLincs and, as such, you are no longer going to experience this problem. I do apologize for the inconvenience. With kind regards, Michel
  13. Hi Steve, No Motion Sensor work in i1 mode. Well, let me rephrase: although they do NOT complain, but nothing gets written into their databases. So, the only reason that your solution works is because the RESPONDERS are being programmed. In short, there are no master links in your motions sensors. This explains why you were experiencing the other issue with your bathroom light. So, please try the following before considering RMA: 1. Factory Reset your Motion Sensor 2. Wait 5 minutes 3. Retry With kind regards, Michel
  14. Hi Joe, Yes, and "hopefully" by the end of the week. With kind regards, Michel
  15. Hi dss, I see the issue ... we are trying to use i2 and, in all likelihood, it failed. The next release should fix this issue. Thanks so very much, With kind regards, Michel Okay tried that, still comes up in 6 button mode. It displays 2486s/WH6 v.31 at the top of the ISY. Sticker says v1.0 0459, and 2486S 0810. So I reverted back to firmware 2.6.8 and tried again. Came up with 8 buttons! Seems like problem must have come up somewhere between v2.6.8 and 2.6.13.
  16. Hi Gary, Actually, we have never thought about this but it makes sense. I do not think we would be able to provide this functionality any time soon since we have too much to do and so little time! Thanks so very much, With kind regards, Michel
  17. Hello Steve, This is very odd. If you look at Tools->Diagnostics->ISY Link Table for your 1st floor bathroom, do you see a link to your motion sensor? Is your 1st floor bathroom part of any scenes? If so, how many and in what role (controller/responder). Was the motion sensor ever a controller for any one of these scenes? If so, which one? If you know which one, put the sensor in that scene and then remove it. With kind regards, Michel
  18. Hi someguy, As Eric suggested, you should factory reset the CL and add it back to ISY. Furthmore, I do think the problem is actually in the responders to your CL. Would you be kind enough to do a restore on one of these responders and see if still responds to the CL. If the request fails, then would you be kind enough to let me know which version of SWL do you have? With kind regards, Michel
  19. Michel Kohanim

    Rescan scenes?

    Hello oktane, To reset the PLM, you should 1. Unplug and leave unplugged for at least 10 seconds (mandatory) 2. Press and hold the set button while unplugged, plug it back in (while holding the set button) and keep it held in for at least 10 seconds. With kind regards, Michel
  20. Michel Kohanim

    Rescan scenes?

    Hi okane, Again, since we have never gone through this exercise with another device changing links, the outcome of what I am going to suggest might not be what you envision. Here's what you should do: 1. factory reset your ISY 2. factory reset your PLM 3. choose a device that has the most number of links to other devices, add it to ISY (either Start Linking or New INSTEON Device), and then choose the 3rd option (add devices found in links and import existing links) With kind regards, Michel
  21. Hi, It's really odd because we do check to see how many buttons does a relay report as supporting. So, do you have 2486S? If so, would you be kind enough to let me know what ISY reports? Click on one of the nodes for this KPL, at the top you see name, version, and some numbers. Please provide me with all. With kind regards, Michel I manually changed it to 8 button mode and put an 8 button button plate on it. When you press the A button only that one lights in the upper left corner in toggle mode and not the A&B as would in 6 button mode. Instead of "Start Linking" I tried "New Insteon Device" and noticed that there isn't a model number for an 8 button Relay. Actually Smarthome doesn't appear to sell an 8 button relay, you have to but a 6 button one and chant it and the faceplate. I wonder if that has something to do with it?
  22. Michel Kohanim

    Rescan scenes?

    Hello oktane, I am not sure I understand the context. Have you already had ISY import devices/links? What does "relink itself" mean? With kind regards, Michel
  23. Hi dss, Do you now have 8 independent buttons on your KPL? ISY reads a flag in the KPL itself to figure out how many buttons it has. So, there are 3 possibilities: 1. The factory reset did not work 2. This KPL does not support 8 buttons 3. Defective switch With kind regards, Michel
  24. Hello lloverin, I do apologize for the inconvenience. We changed the way ControLincs/LampLincs are linked in 2.6.13. Wiki has not been updated with these changes. Did you enter the address and then chose the 3rd option? With kind regards, Michel
  25. Hi David, You have to airgap the switches for the local on level/ramp rate changes to take effect. To airgap, take out the set button, wait about 10 seconds, and then slide them back in (do NOT push/hold them back in). With kind regards, Michel
×
×
  • Create New...