Eug Posted January 3, 2009 Share Posted January 3, 2009 I'm trying to migrate my Insteon programming from HomeSeer to my ISY-99, and I'm having some trouble getting conditional programs to work. Here's a simple test program I'm trying: If Control 'Office - Keypad (D)' is switched On Then Set Scene 'Office - South Track Light' On Else - No Actions - (To add one, press 'Action') I would think that this should turn the light on when key D on the KeypadLinc goes to "on". This doesn't happen, though. I've tried schedule-based programs and those seem to work, so I'm pretty sure I'm entering and saving things correctly. Link to comment
Sub-Routine Posted January 3, 2009 Share Posted January 3, 2009 That program should work fine. When you use Switched you must physically press the button, it won't work if the button is turned on/off in any other way. For that you need to use Status. Rand Link to comment
Eug Posted January 3, 2009 Author Share Posted January 3, 2009 I am physically pressing the button. I've tried this with both KeypadLinc buttons and RemoteLinc buttons, and nothing happens. Link to comment
Sub-Routine Posted January 3, 2009 Share Posted January 3, 2009 It sounds like the ISY isn't seeing the change. If you watch in the Administration Console do you see the state of the button change from Off to On? Link to comment
Eug Posted January 3, 2009 Author Share Posted January 3, 2009 The Administration Console appears to not show any state at all for any buttons that aren't part of a scene. (Firmware 2.6.8 for whatever that's worth). Link to comment
Sub-Routine Posted January 3, 2009 Share Posted January 3, 2009 The Administration Console appears to not show any state at all for any buttons that aren't part of a scene. I didn't realize that was true with the KPL, I know a SwitchLinc doesn't send group commands unless it is linked to another device. Linking a SL to the PLM is enough, but of course there is only one group for a switch. What if you create a new scene with only the KPL button in it? If that works there may be a bug in the ISY. Rand Link to comment
Eug Posted January 3, 2009 Author Share Posted January 3, 2009 Looks like that doesn't have any effect. I created a scene, added the KPL button to it, and it still showed a blank status box (this was true whether I set it to be a controller or responder in the scene). Link to comment
gregoryx Posted January 3, 2009 Share Posted January 3, 2009 The Administration Console appears to not show any state at all for any buttons that aren't part of a scene. (Firmware 2.6.8 for whatever that's worth). That is not what I see in 2.6.13. If I press button B on a KPL (non-load button, just to be sure) that is not part of any scene or links at all (haven't figured out what to use ALL the buttons for yet) and I'm in the Adminsitrative Console on the device itself, the "Current State" changes from "Off" to "On" and back. As a separate question: why run a program for this? Why not just make the button PART of the scene by adding "Office KPL D" to "Scene Office - South Track Light"? Other than our (mutual and long ingrained) HomeSeer habits? Link to comment
Eug Posted January 3, 2009 Author Share Posted January 3, 2009 The Administration Console appears to not show any state at all for any buttons that aren't part of a scene. (Firmware 2.6.8 for whatever that's worth). That is not what I see in 2.6.13. If I press button B on a KPL (non-load button, just to be sure) that is not part of any scene or links at all (haven't figured out what to use ALL the buttons for yet) and I'm in the Adminsitrative Console on the device itself, the "Current State" changes from "Off" to "On" and back. Ok, I'll try installing 2.6.13 later today and see if that helps. As a separate question: why run a program for this? Why not just make the button PART of the scene by adding "Office KPL D" to "Scene Office - South Track Light"? Other than our (mutual and long ingrained) HomeSeer habits? It doesn't matter for this test case where I'm just trying to get it working, but in reality, I want to trigger my "good night" program by double-clicking an off button on a RemoteLinc. If I understand correctly, I can't really do that unless I just want every device in my "good night" scene to instantly switch off as a result. Link to comment
gregoryx Posted January 3, 2009 Share Posted January 3, 2009 That will require a program in ISY and won't require the KPL to be part of a scene. Just a program where "control" of the RL button initiates the scene. I haven't played with RL "on" versus "fast on" signals (double-click); but I've got stuff just like that: an RL key initiates a program which kicks off a scene. It's taking me a bit to figger the diffs in ISY; one of them seems to be a diff between "status" and "control" of an Insteon device. The "becomes" logic of HS seems somewhat similar to these... though not directly. Just as an FYI, since you mention coming from HS. For comparison, when I had used a load on / off to initiate a program (when "Master.Bath is Off") it worked if the light was on then got turned off; I had to change to control ("Control 'Master.Bath' is switched Off") to get it to work as I wanted even if the light was initially off. HTH. Link to comment
gregoryx Posted January 3, 2009 Share Posted January 3, 2009 Point of note: if looking at the "Devices" page on the web interface (not the "Main" tab of the "Adminsitrative Console") you will NOT see non-load KPL buttons. Link to comment
Eug Posted January 3, 2009 Author Share Posted January 3, 2009 Point of note: if looking at the "Devices" page on the web interface (not the "Main" tab of the "Adminsitrative Console") you will NOT see non-load KPL buttons. Right. I'm looking at the main tab. Link to comment
gregoryx Posted January 3, 2009 Share Posted January 3, 2009 Huh. Maybe a version thing, then. Link to comment
Sub-Routine Posted January 3, 2009 Share Posted January 3, 2009 Looks like that doesn't have any effect. I created a scene, added the KPL button to it, and it still showed a blank status box (this was true whether I set it to be a controller or responder in the scene). That doesn't sound good. That is not what I see in 2.6.13. If I press button B on a KPL (non-load button, just to be sure) that is not part of any scene or links at all (haven't figured out what to use ALL the buttons for yet) and I'm in the Adminsitrative Console on the device itself, the "Current State" changes from "Off" to "On" and back. It could be a communication issue but if links are created without errors (new scene) then Status and Control should function properly. Rand Link to comment
MikeB Posted January 4, 2009 Share Posted January 4, 2009 Remember that the state will show blank until the button is pressed for the first time. If you're hitting the button, and it's still showing as blank, I would right-click the KPL and try a RESTORE DEVICE. Link to comment
ulrick65 Posted January 4, 2009 Share Posted January 4, 2009 A key point that Rand touched briefly on above: The act of adding a device to ISY is actually creating a link. (to the PLM) so the KPL button should status should get updated in ISY no matter if it is part of an ISY scene or not (just like gregoryx said). Remember what MikeB said though...it will only show status AFTER it has been pushed at least once (you said you pushed it, so this is likely a moot point) Rand: I am 99.78% sure that KPL's work the same way as SWL's, they don't send group commands unless they have a link...however, as you said connecting to ISY is a link (one for the SWL and either 6 or 9 for a KPL depeding if it is 6 button or 8 button mode). If the restore device that MikeB suggested does not work, then I would remove the device from ISY, factory reset it and then re-add it. Out of curiosity, what version and rev level this KPL is? Link to comment
Eug Posted May 30, 2009 Author Share Posted May 30, 2009 After having given up on this back in January, I'm making another attempt to get it to work. My ISY now has firmware 2.7.0 on it, and I've tried doing a "restore" on several KPLs. The ISY still doesn't update status when a KPL button is turned on or off, whether the button is a member of a scene or not. Any more ideas? Link to comment
Michel Kohanim Posted May 31, 2009 Share Posted May 31, 2009 Hello Eug, Two questions: 1. Please go to Tools | Diagnostics | PLM Status/Info and let me know the version number 2. How many INSTEON devices do you have registered in ISY in total? If all else fails, may I humbly suggest giving our support team a call on the weekdays so that we can login remotely and figure out what's causing all these problems? With kind regards, Michel After having given up on this back in January, I'm making another attempt to get it to work. My ISY now has firmware 2.7.0 on it, and I've tried doing a "restore" on several KPLs. The ISY still doesn't update status when a KPL button is turned on or off, whether the button is a member of a scene or not. Any more ideas? Link to comment
Eug Posted June 1, 2009 Author Share Posted June 1, 2009 Hi Michel, Hello Eug, Two questions: 1. Please go to Tools | Diagnostics | PLM Status/Info and let me know the version number 2. How many INSTEON devices do you have registered in ISY in total? 1: PLM version is v72. 2: 30 devices at the moment. Link to comment
Michel Kohanim Posted June 1, 2009 Share Posted June 1, 2009 Hello Eug, The only reason ISY would not get statuses back from your KPLs is that there are no slave links in the PLM for that device. Since your PLM version seems OK, then would you be kind enough to do the following: 1. Remove your KPL from ISY (one that's not that important in your setup) 2. Do a factory reset on it 3. Add it back to ISY 4. Let me know if you get status feedback If you do not, then I would suspect the PLM. If you do, then I suspect that originally the system was crawled and that's why the links were missing. With kind regards, Michel Hi Michel, Hello Eug, Two questions: 1. Please go to Tools | Diagnostics | PLM Status/Info and let me know the version number 2. How many INSTEON devices do you have registered in ISY in total? 1: PLM version is v72. 2: 30 devices at the moment. Link to comment
Eug Posted June 1, 2009 Author Share Posted June 1, 2009 Hi Michel, One of the KPLs in question is a new device that I just installed, so that's effectively factory reset. Is there some way to check the PLM's links? Link to comment
Michel Kohanim Posted June 1, 2009 Share Posted June 1, 2009 Hi Eug, Ok. Yes, you can check the PLM link tables by going to Tools | Diagnostics | Show PLM Links Table. You should have 6 to 8 entries for your KPL depending on the number of buttons you have. If your setup is not that current, then may I humbly suggest resetting your PLM and starting over with your most recent KPL. This way we can definitively decide where the problem is coming problem. My suspicions are: 1. PLM itself 70% 2. Noise related issues 30% With kind regards, Michel Hi Michel, One of the KPLs in question is a new device that I just installed, so that's effectively factory reset. Is there some way to check the PLM's links? Link to comment
Eug Posted June 1, 2009 Author Share Posted June 1, 2009 Hi Michel, When I do "show PLM links", I get an empty "PLM links table" dialog. Clicking the "Start" button has no effect. Clicking the "Count" button shows me a message box that says "0". Link to comment
Michel Kohanim Posted June 1, 2009 Share Posted June 1, 2009 Hi Eug, Then I would suspect you have a defective PLM. To make sure this is the case, please try adding a device to your ISY and retry. If you still get no records, then it's the PLM. With kind regards, Michel Hi Michel, When I do "show PLM links", I get an empty "PLM links table" dialog. Clicking the "Start" button has no effect. Clicking the "Count" button shows me a message box that says "0". Link to comment
Eug Posted June 1, 2009 Author Share Posted June 1, 2009 I can add devices to the PLM without issue, and the ISY has no problem controlling devices, or querying them. Just want to make sure that's clear in case it changes your hypothesis, before I call SmartHome to RMA the PLM. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.