From: Richard Z. <rs...@gm...> - 2012-09-10 22:49:33
|
OK, I'm having some trouble just getting off the ground with Insteon. Probably a stupid question, but I've been searching for info and I just can't seem to nail this one: Is there a way to delete all the device links that are not defined in the mht file? For instance, I've got a few controllers that have some orphaned links that I no longer want. For instance, I've got 2 switchlincs linked together in a 3-way configuration, but that's no longer specified in my mht file. I try to "Sync All Links" under the Insteon menu, but that doesn't seem to delete these old crosslinks. Do I have to go to each switchlinc and do a factory reset? 2nd question: When using the web interface things don't seem to update properly when I press on them. For instance, I'll turn on one of my Switchlincs, but the web button will still say "Off" until I press it a second time, at which point the "On" icon will appear and I'll be able to turn it off. Thanks so much! |
From: Richard Z. <rs...@gm...> - 2012-09-10 23:45:20
|
OK, I did have one other question as well... I'm having another issue simply crosslinking two switchlincs and getting the status of both switches to update properly in mh. Here's my mht file: Format = A INSTEON_PLM, PLM, IPLL, 0D.B8.DD, test_one, All_lights|Blah, PLM, # 2476S IPLL, 16.1F.98, test_two, All_lights|Blah, PLM, # 2476D SCENE_MEMBER, test_one, test_two, 100%, 2s SCENE_MEMBER, test_two, test_one, 100%, 2s Simple, right? Well, when I turn on test_one, it turns on both lights, but only test_one shows as "ON" in mh. Same goes for reverse. The documentation seems to indicate that this should be sufficient to inform mh that one button controls the other, (and to poll the other if you go into "DIM" mode), but that just doesn't seem to be happening. |
From: George F. <fa...@sh...> - 2012-09-11 02:03:17
|
Hi Richard, On Mon, 2012-09-10 at 16:44 -0700, Richard Zimmerman wrote: > OK, I did have one other question as well... > I'm having another issue simply crosslinking two switchlincs and > getting the status of both switches to update properly in mh. Here's > my mht file: > Format = A > INSTEON_PLM, PLM, > IPLL, 0D.B8.DD, test_one, All_lights|Blah, PLM, # 2476S > IPLL, 16.1F.98, test_two, All_lights|Blah, PLM, # 2476D > You need to have your IPLL defined like so: IPLL, OD.B8.DD:01, test_one, All_Lights|Blah, PLM The :01 is the switch side of the equation so now you can link in both directions. This allows you to have: Switch A as a controller with Switch B as a responder and Switch B as a controller with Switch A as a responder Cheers George |
From: George F. <fa...@sh...> - 2012-09-11 04:04:45
|
On Mon, 2012-09-10 at 15:49 -0700, Richard Zimmerman wrote: > > Is there a way to delete all the device links that are not defined in > the mht file? For instance, I've got a few controllers that have some > orphaned links that I no longer want. For instance, I've got 2 > switchlincs linked together in a 3-way configuration, but that's no > longer specified in my mht file. I try to "Sync All Links" under the > Insteon menu, but that doesn't seem to delete these old crosslinks. > Do I have to go to each switchlinc and do a factory reset? Not that I'm aware of. If it isn't in your *.mht file then I think you are best doing a factory reset on the devices. > > 2nd question: > When using the web interface things don't seem to update properly when > I press on them. For instance, I'll turn on one of my Switchlincs, > but the web button will still say "Off" until I press it a second > time, at which point the "On" icon will appear and I'll be able to > turn it off. Yes I have the same problem with it. Never really dug into it so not sure, someone else may be able to answer this one. Cheers George |
From: Eloy P. <pe...@ch...> - 2012-09-11 04:40:32
|
Hello, On 09/11/2012 12:05 AM, George Farris wrote: > On Mon, 2012-09-10 at 15:49 -0700, Richard Zimmerman wrote: > >> [...] >> >> 2nd question: >> When using the web interface things don't seem to update properly when >> I press on them. For instance, I'll turn on one of my Switchlincs, >> but the web button will still say "Off" until I press it a second >> time, at which point the "On" icon will appear and I'll be able to >> turn it off. > > Yes I have the same problem with it. Never really dug into it so not > sure, someone else may be able to answer this one. This one has been asked before here in the list; we should probably have an FAQ entry for this one somewhere in the wiki. If I remember correctly, and if I understood correctly the explanation that was given when someone asked the question, the reason for the behavior is that as soon as you click on the button in the web user interface, MH will process the HTML form/page and send the command to the INSTEON device. However, the acknowledgement from the device, which MisterHouse needs to 1. know that the device received the INSTEON command and that there is no need to re-transmit the command, and 2. update the internal state of the device, has not arrived when MH finishes processing the initial form/page, so the state that is presented in the new HTML page (after clicking on the button) is the state that existed *before* the button was clicked. A bit later, the acknowledgement arrives and MH updates the state (on or off) of the device. However, by then the HTML page is already rendered, presenting the *previous* (before clicking on the button) device state. When you press the button a second time MH probably sends an unnecessary command (because in reality the device is already in that state after the button was clicked for the first time) that causes no harm, and then reads the internal state (which was updated when MH received the ACK to the first button click), which then causes the correct state to be displayed in the page. I believe a workaround that I saw mentioned here was to define the INSTEON device as an X10 device -- unlike INSTEON, X10 does not support ACKs, so MH updates the state of an X10 device as soon as you click on the button in the web UI. It'd be nice if the web page isn't re-drawn so quickly, and instead, is re-drawn after the ACK is received (like what happens when you press "submit" on an HTML form and your browser waits for the server to process the form). I have no idea if that is technically possible here, though. The above is a mouthful. Hopefully it makes sense. Cheers, Eloy Paris.- |
From: Marc M. <ma...@me...> - 2012-09-11 04:41:07
|
On Mon, Sep 10, 2012 at 09:05:22PM -0700, George Farris wrote: > On Mon, 2012-09-10 at 15:49 -0700, Richard Zimmerman wrote: > > > > > Is there a way to delete all the device links that are not defined in > > the mht file? For instance, I've got a few controllers that have some > > orphaned links that I no longer want. For instance, I've got 2 > > switchlincs linked together in a 3-way configuration, but that's no > > longer specified in my mht file. I try to "Sync All Links" under the > > Insteon menu, but that doesn't seem to delete these old crosslinks. > > Do I have to go to each switchlinc and do a factory reset? > > Not that I'm aware of. If it isn't in your *.mht file then I think you > are best doing a factory reset on the devices. With the old insteon code, you want 'delete orphans' in the PLM menu. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ |
From: Marc M. <ma...@me...> - 2012-09-11 05:02:01
|
On Mon, Sep 10, 2012 at 03:49:06PM -0700, Richard Zimmerman wrote: > 2nd question: > When using the web interface things don't seem to update properly when I > press on them. For instance, I'll turn on one of my Switchlincs, but the > web button will still say "Off" until I press it a second time, at which > point the "On" icon will appear and I'll be able to turn it off. You got the answer for that. If you use the insteon web page http://server:8080/bin/list?Insteon You can toggle devices and the web interface will work properly there. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ |
From: Richard Z. <rs...@gm...> - 2012-09-11 17:13:41
|
> > You need to have your IPLL defined like so: > > IPLL, OD.B8.DD:01, test_one, All_Lights|Blah, PLM > > The :01 is the switch side of the equation so now you can link in both > directions. Thanks George. I tried that and it didn't seem to work. My mht file is now: Format = A INSTEON_PLM, PLM, IPLL, 0D.B8.DD:01, test_one, All_lights|Blah, PLM, # 2476S IPLL, 16.1F.98:01, test_two, All_lights|Blah, PLM, # 2476D SCENE_MEMBER, test_one, test_two, 100%, 2s SCENE_MEMBER, test_two, test_one, 100%, 2s As before, the crosslinking works, but when I touch the paddle on test_one to turn it on, mh only thinks test_one is on and doesn't know that test_two also went on. |
From: George F. <fa...@gm...> - 2012-09-11 17:45:44
|
On Tue, 2012-09-11 at 10:13 -0700, Richard Zimmerman wrote: > You need to have your IPLL defined like so: > > IPLL, OD.B8.DD:01, test_one, All_Lights|Blah, PLM > > The :01 is the switch side of the equation so now you can link > in both > directions. > > > Thanks George. I tried that and it didn't seem to work. My mht file > is now: > Format = A > INSTEON_PLM, PLM, > IPLL, 0D.B8.DD:01, test_one, All_lights|Blah, PLM, # 2476S > IPLL, 16.1F.98:01, test_two, All_lights|Blah, PLM, # 2476D > > > SCENE_MEMBER, test_one, test_two, 100%, 2s > SCENE_MEMBER, test_two, test_one, 100%, 2s > > > As before, the crosslinking works, but when I touch the paddle on > test_one to turn it on, mh only thinks test_one is on and doesn't know > that test_two also went on. Right and do you have your devices linked to the PLM as well? Switch as controller and PLM as responder? I've not tried crosslinking devices yet, guess I'll have to try it. George |
From: Richard Z. <rs...@gm...> - 2012-09-11 18:16:15
|
Yeah, If I switch on test_one (using the toggle), it shows as ON in the web page. If I switch on test_two, then it also shows as ON in the web page. What doesn't work is the OTHER one showing up as ON. Here's a related, but even more odd problem: I've got a KPL and a switchlinc. I've button E to control the switchlinc, and correspondingly backlinked the switchlinc to turn on/off the KPL button. Here's the mht: IPLL, 16.1F.98:01, test_two, All_lights|Blah, PLM, # 2476D IPLL, 0E.29.87:05, kpl1_button_e, All_lights|Blah, PLM, # KPL SCENE_MEMBER, kpl1_button_e, test_two SCENE_MEMBER, test_two, kpl1_button_e What happens here is very strange. The buttons work as planned (E turns on and off the switchlinc, and the switchlink turns on and off button E). The strange part is what MH thinks the state is. If I press button E, MH will know that E *and* the switchlinc are on. However, if I turn on the switchlink with the paddle, it only thinks that the switchlinc is on, and not the button E. Setting up the surrogate stuff doesn't seem to make a difference. So it would seem that MH knows about some links, but not others. Odd..... -Rich On Tue, Sep 11, 2012 at 10:45 AM, George Farris <fa...@gm...> wrote: > On Tue, 2012-09-11 at 10:13 -0700, Richard Zimmerman wrote: > > You need to have your IPLL defined like so: > > > > IPLL, OD.B8.DD:01, test_one, All_Lights|Blah, PLM > > > > The :01 is the switch side of the equation so now you can link > > in both > > directions. > > > > > > Thanks George. I tried that and it didn't seem to work. My mht file > > is now: > > Format = A > > INSTEON_PLM, PLM, > > IPLL, 0D.B8.DD:01, test_one, All_lights|Blah, PLM, # 2476S > > IPLL, 16.1F.98:01, test_two, All_lights|Blah, PLM, # 2476D > > > > > > SCENE_MEMBER, test_one, test_two, 100%, 2s > > SCENE_MEMBER, test_two, test_one, 100%, 2s > > > > > > As before, the crosslinking works, but when I touch the paddle on > > test_one to turn it on, mh only thinks test_one is on and doesn't know > > that test_two also went on. > > Right and do you have your devices linked to the PLM as well? > Switch as controller and PLM as responder? > > I've not tried crosslinking devices yet, guess I'll have to try it. > > George > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |
From: Richard Z. <rs...@gm...> - 2012-09-12 01:37:03
|
OK, I did some debugging here to try and get to the bottom of what's wrong. I found an issue with line 252 in Insteon_Link.pm: if ($self->is_plm_controlled or !($self->is_root)) { This is preventing the firing of the links stored for the object if the object in question is "root" (i.e. group ID 0x01). That's why keypadlinks work and switchlincs don't. I commented out this line (and the associated } ) and everything seemed to update just fine. Looking through the subversion tree, it appears that this may have been something specifically put in during version 1306. It seems that a checkin was made in version 1635, but then was backed out in 1636. Clearly there must have been some reason why this was backed out. I'm not familiar enough with the code to tell what's the correct behavior. -Rich P.S. Is this the right forum for reporting these programming bugs/issues? On Tue, Sep 11, 2012 at 11:15 AM, Richard Zimmerman <rs...@gm...>wrote: > Yeah, If I switch on test_one (using the toggle), it shows as ON in the > web page. If I switch on test_two, then it also shows as ON in the web > page. What doesn't work is the OTHER one showing up as ON. > > Here's a related, but even more odd problem: > I've got a KPL and a switchlinc. I've button E to control the switchlinc, > and correspondingly backlinked the switchlinc to turn on/off the KPL > button. Here's the mht: > IPLL, 16.1F.98:01, test_two, All_lights|Blah, PLM, # 2476D > IPLL, 0E.29.87:05, kpl1_button_e, All_lights|Blah, PLM, # KPL > SCENE_MEMBER, kpl1_button_e, test_two > SCENE_MEMBER, test_two, kpl1_button_e > > What happens here is very strange. The buttons work as planned (E turns > on and off the switchlinc, and the switchlink turns on and off button E). > The strange part is what MH thinks the state is. If I press button E, MH > will know that E *and* the switchlinc are on. However, if I turn on the > switchlink with the paddle, it only thinks that the switchlinc is on, and > not the button E. Setting up the surrogate stuff doesn't seem to make a > difference. So it would seem that MH knows about some links, but not > others. Odd..... > > -Rich > > > > On Tue, Sep 11, 2012 at 10:45 AM, George Farris <fa...@gm...> wrote: > >> On Tue, 2012-09-11 at 10:13 -0700, Richard Zimmerman wrote: >> > You need to have your IPLL defined like so: >> > >> > IPLL, OD.B8.DD:01, test_one, All_Lights|Blah, PLM >> > >> > The :01 is the switch side of the equation so now you can link >> > in both >> > directions. >> > >> > >> > Thanks George. I tried that and it didn't seem to work. My mht file >> > is now: >> > Format = A >> > INSTEON_PLM, PLM, >> > IPLL, 0D.B8.DD:01, test_one, All_lights|Blah, PLM, # 2476S >> > IPLL, 16.1F.98:01, test_two, All_lights|Blah, PLM, # 2476D >> > >> > >> > SCENE_MEMBER, test_one, test_two, 100%, 2s >> > SCENE_MEMBER, test_two, test_one, 100%, 2s >> > >> > >> > As before, the crosslinking works, but when I touch the paddle on >> > test_one to turn it on, mh only thinks test_one is on and doesn't know >> > that test_two also went on. >> >> Right and do you have your devices linked to the PLM as well? >> Switch as controller and PLM as responder? >> >> I've not tried crosslinking devices yet, guess I'll have to try it. >> >> George >> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> ________________________________________________________ >> To unsubscribe from this list, go to: >> http://sourceforge.net/mail/?group_id=1365 >> >> > |
From: Eloy P. <pe...@ch...> - 2012-09-12 02:03:35
|
Hi Rich, On 09/11/2012 09:36 PM, Richard Zimmerman wrote: > OK, I did some debugging here to try and get to the bottom of what's > wrong. I found an issue with line 252 in Insteon_Link.pm: > if ($self->is_plm_controlled or !($self->is_root)) { > This is preventing the firing of the links stored for the object if the > object in question is "root" (i.e. group ID 0x01). That's why > keypadlinks work and switchlincs don't. I commented out this line (and > the associated } ) and everything seemed to update just fine. > > Looking through the subversion tree, it appears that this may have been > something specifically put in during version 1306. It seems that a > checkin was made in version 1635, but then was backed out in 1636. > Clearly there must have been some reason why this was backed out. I'm > not familiar enough with the code to tell what's the correct behavior. Are you running trunk (or the latest "official" release), or misterhouse/branches/insteon? If the former then note that the INSTEON code in the trunk is basically unmaintained. Some of us are running the "insteon" branch, which has a new implementation of the INSTEON code. It is not finished yet, though, and some things, like link table scanning and deletion of orphan links might not be working in all cases. But for simple control of switches I have found that it works really well. The only downside is that right now even the "insteon" branch is not being actively mantained since the only developer working on that code has been busy with other things. But, if you are going to go through the effort of reading the code to try to figure out why some things are not working as they should I think you'll be better off reading the code in the "insteon" branch. > P.S. Is this the right forum for reporting these programming bugs/issues? Yup, this is the right place, although, as I said, there is no one currently working actively on the INSTEON code, unfortunately. Cheers, Eloy Paris.- > > > On Tue, Sep 11, 2012 at 11:15 AM, Richard Zimmerman <rs...@gm... > <mailto:rs...@gm...>> wrote: > > Yeah, If I switch on test_one (using the toggle), it shows as ON in > the web page. If I switch on test_two, then it also shows as ON in > the web page. What doesn't work is the OTHER one showing up as ON. > > Here's a related, but even more odd problem: > I've got a KPL and a switchlinc. I've button E to control the > switchlinc, and correspondingly backlinked the switchlinc to turn > on/off the KPL button. Here's the mht: > IPLL,16.1F.98:01,test_two,All_lights|Blah,PLM, # 2476D > IPLL,0E.29.87:05,kpl1_button_e,All_lights|Blah,PLM, # KPL > SCENE_MEMBER, kpl1_button_e, test_two > SCENE_MEMBER, test_two, kpl1_button_e > > What happens here is very strange. The buttons work as planned (E > turns on and off the switchlinc, and the switchlink turns on and off > button E). The strange part is what MH thinks the state is. If I > press button E, MH will know that E /and/ the switchlinc are on. > However, if I turn on the switchlink with the paddle, it only > thinks that the switchlinc is on, and not the button E. Setting up > the surrogate stuff doesn't seem to make a difference. So it would > seem that MH knows about some links, but not others. Odd..... > > -Rich > > > > On Tue, Sep 11, 2012 at 10:45 AM, George Farris <fa...@gm... > <mailto:fa...@gm...>> wrote: > > On Tue, 2012-09-11 at 10:13 -0700, Richard Zimmerman wrote: > > You need to have your IPLL defined like so: > > > > IPLL, OD.B8.DD:01, test_one, All_Lights|Blah, PLM > > > > The :01 is the switch side of the equation so now you > can link > > in both > > directions. > > > > > > Thanks George. I tried that and it didn't seem to work. My > mht file > > is now: > > Format = A > > INSTEON_PLM, PLM, > > IPLL, 0D.B8.DD:01, test_one, All_lights|Blah, PLM, # 2476S > > IPLL, 16.1F.98:01, test_two, All_lights|Blah, PLM, # 2476D > > > > > > SCENE_MEMBER, test_one, test_two, 100%, 2s > > SCENE_MEMBER, test_two, test_one, 100%, 2s > > > > > > As before, the crosslinking works, but when I touch the paddle on > > test_one to turn it on, mh only thinks test_one is on and > doesn't know > > that test_two also went on. > > Right and do you have your devices linked to the PLM as well? > Switch as controller and PLM as responder? > > I've not tried crosslinking devices yet, guess I'll have to try it. > > George > > |