From: Kevin R. K. <ke...@kr...> - 2013-06-01 02:41:25
|
Another huge merge was done tonight. We now only have a few small issues remaining before we can push all of this to stable. If you could pull the master branch from hollie and run it this weekend, I would appreciate any bug reports that you have. I will be around all weekend and ready to handle any fires that may arise, although while large in scale, these merges did not alter much of the base MH code. They did add or update support for a few Insteon devices for those who are interested. Kevin |
From: Eloy P. <pe...@ch...> - 2013-06-01 04:25:49
|
Hi Kevin, Thanks for your hard work. What will become MisterHouse 3.0 is looking pretty good. I just updated and I'm running the latest. I'll report back if I run into any issues. Cheers, Eloy Paris.- On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > Another huge merge was done tonight. We now only have a few small issues > remaining before we can push all of this to stable. > > If you could pull the master branch from hollie and run it this weekend, > I would appreciate any bug reports that you have. > > I will be around all weekend and ready to handle any fires that may > arise, although while large in scale, these merges did not alter much of > the base MH code. They did add or update support for a few Insteon > devices for those who are interested. > > Kevin > |
From: Jim D. <ji...@du...> - 2013-06-02 14:59:59
|
On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > Another huge merge was done tonight. We now only have a few small issues remaining before we can push all of this to stable. > > If you could pull the master branch from hollie and run it this weekend, I would appreciate any bug reports that you have. Thanks for all the great Insteon enhancements. Really great stuff you've done for the project. I updated last night and all is working normally in my house. The merge went fine and no compile issues. Jim |
From: Edward B. <eb...@se...> - 2013-06-02 18:07:18
|
Hi Everyone, I pulled the master branch from holly and I don't seem to have an X10 support through my insteon PLM . At startup, I see my .mht being read, dummy interfaces being setup for each of the X10 objects, but when I attempt to turn on a lamp or appliance module, mh says trying to set state to on, but I see no X10 output, and no light. I reverted back to mh 2.105 R2023, and everything works again. Out of the gate, the insteon devices didn't work, but completing linking etc..and my insteon devices work, but no X10. I tried going back to one or two versions over the last two months I had pulled from git, and got the same results. Any thoughts on which direction I should go? Thanks, Edward -----Original Message----- From: Eloy Paris [mailto:pe...@ch...] Sent: Saturday, June 01, 2013 12:25 AM To: mis...@li... Subject: Re: [mh] MH Version 3.0 Nearly Finished Hi Kevin, Thanks for your hard work. What will become MisterHouse 3.0 is looking pretty good. I just updated and I'm running the latest. I'll report back if I run into any issues. Cheers, Eloy Paris.- On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > Another huge merge was done tonight. We now only have a few small > issues remaining before we can push all of this to stable. > > If you could pull the master branch from hollie and run it this > weekend, I would appreciate any bug reports that you have. > > I will be around all weekend and ready to handle any fires that may > arise, although while large in scale, these merges did not alter much > of the base MH code. They did add or update support for a few Insteon > devices for those who are interested. > > Kevin > ---------------------------------------------------------------------------- -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ________________________________________________________ To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 |
From: Dustin R. <du...@du...> - 2013-06-02 18:29:19
|
X10 is working for me. I just pulled master last night. Coming from 2.105 your mht file is going to need some heavy modification iirc. On Jun 2, 2013 2:09 PM, "Edward Brookhouse" <eb...@se...> wrote: > Hi Everyone, > > I pulled the master branch from holly and I don't seem to have an X10 > support through my insteon PLM . At startup, I see my .mht being read, > dummy interfaces being setup for each of the X10 objects, but when I > attempt > to turn on a lamp or appliance module, mh says trying to set state to on, > but I see no X10 output, and no light. > > I reverted back to mh 2.105 R2023, and everything works again. > > Out of the gate, the insteon devices didn't work, but completing linking > etc..and my insteon devices work, but no X10. > > I tried going back to one or two versions over the last two months I had > pulled from git, and got the same results. > > Any thoughts on which direction I should go? > > Thanks, > > Edward > > > -----Original Message----- > From: Eloy Paris [mailto:pe...@ch...] > Sent: Saturday, June 01, 2013 12:25 AM > To: mis...@li... > Subject: Re: [mh] MH Version 3.0 Nearly Finished > > Hi Kevin, > > Thanks for your hard work. What will become MisterHouse 3.0 is looking > pretty good. > > I just updated and I'm running the latest. I'll report back if I run into > any issues. > > Cheers, > > Eloy Paris.- > > On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > > > Another huge merge was done tonight. We now only have a few small > > issues remaining before we can push all of this to stable. > > > > If you could pull the master branch from hollie and run it this > > weekend, I would appreciate any bug reports that you have. > > > > I will be around all weekend and ready to handle any fires that may > > arise, although while large in scale, these merges did not alter much > > of the base MH code. They did add or update support for a few Insteon > > devices for those who are interested. > > > > Kevin > > > > > ---------------------------------------------------------------------------- > -- > Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free > troubleshooting tool designed for production Get down to code-level detail > for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |
From: Michelle D. <md...@oc...> - 2013-06-02 18:25:23
|
Has anyone made sure the Zwave stuff is in this version? I sent in a couple of files (missing from the ver 2 on git)...just want to ensure someone picked them up ________________________________________ From: Jim Duda [ji...@du...] Sent: Sunday, June 02, 2013 10:59 AM To: mis...@li... Subject: Re: [mh] MH Version 3.0 Nearly Finished On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > Another huge merge was done tonight. We now only have a few small issues remaining before we can push all of this to stable. > > If you could pull the master branch from hollie and run it this weekend, I would appreciate any bug reports that you have. Thanks for all the great Insteon enhancements. Really great stuff you've done for the project. I updated last night and all is working normally in my house. The merge went fine and no compile issues. Jim ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ________________________________________________________ To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 |
From: Lieven H. <li...@li...> - 2013-06-02 19:04:23
|
Hi Michelle, you can check that out in the file browser here: https://github.com/hollie/misterhouse/tree/master Just navigate and check the files are in. If they are not, a pull request is very welcome! More info on that is here: https://github.com/hollie/misterhouse/wiki/Contributing#developing-using-git Kind regards, Lieven. Op 2-jun.-2013, om 20:04 heeft Michelle Dupuis <md...@oc...> het volgende geschreven: > Has anyone made sure the Zwave stuff is in this version? > > I sent in a couple of files (missing from the ver 2 on git)...just want to ensure someone picked them up > > ________________________________________ > From: Jim Duda [ji...@du...] > Sent: Sunday, June 02, 2013 10:59 AM > To: mis...@li... > Subject: Re: [mh] MH Version 3.0 Nearly Finished > > On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: >> Another huge merge was done tonight. We now only have a few small issues remaining before we can push all of this to stable. >> >> If you could pull the master branch from hollie and run it this weekend, I would appreciate any bug reports that you have. > > Thanks for all the great Insteon enhancements. Really great stuff you've done for the project. > I updated last night and all is working normally in my house. The merge went fine and no compile issues. > > Jim > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |
From: Lieven H. <li...@li...> - 2013-06-02 19:41:11
|
Hi Kevin, I'm running master with lots of xPL devices, some custom hardware and a few Philips Hues. Works like a charm! Thank you for all the time and effort you have spent in updating the code and maintaining the codebase in general. A request/remark to all: before we go for MisterHouse 3.0, would it make sense to make a high-level overview of what was changed compared to the previous version? I don't mean listing up all commits separately, but something more helicopter-level e.g. 'Updated Insteon support for type X devices, supporting now this and that.'. This was already discussed on the list previously and I think it makes sense to have this. I tried to keep track of the changes I committed here: https://github.com/hollie/misterhouse/wiki/Changelog Is this useful? So we update this list with the Insteon changes/documentation changes/... so that we have a nice changelog for 3.0? Kind regards, Lieven. Op 1-jun.-2013, om 04:41 heeft Kevin Robert Keegan <ke...@kr...> het volgende geschreven: > Another huge merge was done tonight. We now only have a few small issues remaining before we can push all of this to stable. > > If you could pull the master branch from hollie and run it this weekend, I would appreciate any bug reports that you have. > > I will be around all weekend and ready to handle any fires that may arise, although while large in scale, these merges did not alter much of the base MH code. They did add or update support for a few Insteon devices for those who are interested. > > Kevin > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > |
From: Kevin R. K. <ke...@kr...> - 2013-06-02 21:43:42
|
On Sun, Jun 2, 2013 at 12:41 PM, Lieven Hollevoet <li...@li...> wrote: > A request/remark to all: before we go for MisterHouse 3.0, would it make > sense to make a high-level overview of what was changed compared to the > previous version? Yes, I think something like that would be worthwhile. I can start contributing to that. |
From: Kevin R. K. <ke...@kr...> - 2013-06-02 21:35:31
|
Edward, Yes, there were unfortunately some changes to the mht file structure since 2.105. First check out the Migration section: http://misterhouse.wikispaces.com/Insteon+Redux#Migration Then look at some example mht files: http://misterhouse.wikispaces.com/Insteon#Starting Misterhouse-Adding Insteon Devices to Misterhouse and if you have any questions, post them on the list. Kevin On Sun, Jun 2, 2013 at 10:48 AM, Edward Brookhouse <eb...@se...>wrote: > Hi Everyone, > > I pulled the master branch from holly and I don't seem to have an X10 > support through my insteon PLM . At startup, I see my .mht being read, > dummy interfaces being setup for each of the X10 objects, but when I > attempt > to turn on a lamp or appliance module, mh says trying to set state to on, > but I see no X10 output, and no light. > > I reverted back to mh 2.105 R2023, and everything works again. > > Out of the gate, the insteon devices didn't work, but completing linking > etc..and my insteon devices work, but no X10. > > I tried going back to one or two versions over the last two months I had > pulled from git, and got the same results. > > Any thoughts on which direction I should go? > > Thanks, > > Edward > > > -----Original Message----- > From: Eloy Paris [mailto:pe...@ch...] > Sent: Saturday, June 01, 2013 12:25 AM > To: mis...@li... > Subject: Re: [mh] MH Version 3.0 Nearly Finished > > Hi Kevin, > > Thanks for your hard work. What will become MisterHouse 3.0 is looking > pretty good. > > I just updated and I'm running the latest. I'll report back if I run into > any issues. > > Cheers, > > Eloy Paris.- > > On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > > > Another huge merge was done tonight. We now only have a few small > > issues remaining before we can push all of this to stable. > > > > If you could pull the master branch from hollie and run it this > > weekend, I would appreciate any bug reports that you have. > > > > I will be around all weekend and ready to handle any fires that may > > arise, although while large in scale, these merges did not alter much > > of the base MH code. They did add or update support for a few Insteon > > devices for those who are interested. > > > > Kevin > > > > > ---------------------------------------------------------------------------- > -- > Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free > troubleshooting tool designed for production Get down to code-level detail > for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |
From: Joel D. <jr...@pr...> - 2013-06-02 21:39:27
|
Kevin, Just to be sure, the changes to the mht file are only for folks using Insteon, correct? Those of us who're still in the dark ages and using only X10 don't have to make any changes? Thanks. Joel On Sun, 2 Jun 2013, it would appear that Kevin Robert Keegan wrote: > Edward, > > Yes, there were unfortunately some changes to the mht file structure since > 2.105. > > First check out the Migration section: > > http://misterhouse.wikispaces.com/Insteon+Redux#Migration > > Then look at some example mht files: > > http://misterhouse.wikispaces.com/Insteon#Starting Misterhouse-Adding > Insteon Devices to Misterhouse > > and if you have any questions, post them on the list. > > Kevin > > > On Sun, Jun 2, 2013 at 10:48 AM, Edward Brookhouse <eb...@se...>wrote: > >> Hi Everyone, >> >> I pulled the master branch from holly and I don't seem to have an X10 >> support through my insteon PLM . At startup, I see my .mht being read, >> dummy interfaces being setup for each of the X10 objects, but when I >> attempt >> to turn on a lamp or appliance module, mh says trying to set state to on, >> but I see no X10 output, and no light. >> >> I reverted back to mh 2.105 R2023, and everything works again. >> >> Out of the gate, the insteon devices didn't work, but completing linking >> etc..and my insteon devices work, but no X10. >> >> I tried going back to one or two versions over the last two months I had >> pulled from git, and got the same results. >> >> Any thoughts on which direction I should go? >> >> Thanks, >> >> Edward >> >> >> -----Original Message----- >> From: Eloy Paris [mailto:pe...@ch...] >> Sent: Saturday, June 01, 2013 12:25 AM >> To: mis...@li... >> Subject: Re: [mh] MH Version 3.0 Nearly Finished >> >> Hi Kevin, >> >> Thanks for your hard work. What will become MisterHouse 3.0 is looking >> pretty good. >> >> I just updated and I'm running the latest. I'll report back if I run into >> any issues. >> >> Cheers, >> >> Eloy Paris.- >> >> On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: >> >>> Another huge merge was done tonight. We now only have a few small >>> issues remaining before we can push all of this to stable. >>> >>> If you could pull the master branch from hollie and run it this >>> weekend, I would appreciate any bug reports that you have. >>> >>> I will be around all weekend and ready to handle any fires that may >>> arise, although while large in scale, these merges did not alter much >>> of the base MH code. They did add or update support for a few Insteon >>> devices for those who are interested. >>> >>> Kevin >>> |
From: Kevin R. K. <ke...@kr...> - 2013-06-02 21:46:09
|
Yes, that should be correct. For those on the list these are not "recent changes." The change in the mht has been part of the github source since November. The changes will affect those using the Insteon PLM. On Sun, Jun 2, 2013 at 2:39 PM, Joel Davidson <jr...@pr...> wrote: > Kevin, > > Just to be sure, the changes to the mht file are only for folks > using Insteon, correct? Those of us who're still in the dark > ages and using only X10 don't have to make any changes? > > Thanks. > > Joel > > On Sun, 2 Jun 2013, it would appear that Kevin Robert Keegan wrote: > > > Edward, > > > > Yes, there were unfortunately some changes to the mht file structure > since > > 2.105. > > > > First check out the Migration section: > > > > http://misterhouse.wikispaces.com/Insteon+Redux#Migration > > > > Then look at some example mht files: > > > > http://misterhouse.wikispaces.com/Insteon#Starting Misterhouse-Adding > > Insteon Devices to Misterhouse > > > > and if you have any questions, post them on the list. > > > > Kevin > > > > > > On Sun, Jun 2, 2013 at 10:48 AM, Edward Brookhouse <eb...@se... > >wrote: > > > >> Hi Everyone, > >> > >> I pulled the master branch from holly and I don't seem to have an X10 > >> support through my insteon PLM . At startup, I see my .mht being read, > >> dummy interfaces being setup for each of the X10 objects, but when I > >> attempt > >> to turn on a lamp or appliance module, mh says trying to set state to > on, > >> but I see no X10 output, and no light. > >> > >> I reverted back to mh 2.105 R2023, and everything works again. > >> > >> Out of the gate, the insteon devices didn't work, but completing linking > >> etc..and my insteon devices work, but no X10. > >> > >> I tried going back to one or two versions over the last two months I had > >> pulled from git, and got the same results. > >> > >> Any thoughts on which direction I should go? > >> > >> Thanks, > >> > >> Edward > >> > >> > >> -----Original Message----- > >> From: Eloy Paris [mailto:pe...@ch...] > >> Sent: Saturday, June 01, 2013 12:25 AM > >> To: mis...@li... > >> Subject: Re: [mh] MH Version 3.0 Nearly Finished > >> > >> Hi Kevin, > >> > >> Thanks for your hard work. What will become MisterHouse 3.0 is looking > >> pretty good. > >> > >> I just updated and I'm running the latest. I'll report back if I run > into > >> any issues. > >> > >> Cheers, > >> > >> Eloy Paris.- > >> > >> On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > >> > >>> Another huge merge was done tonight. We now only have a few small > >>> issues remaining before we can push all of this to stable. > >>> > >>> If you could pull the master branch from hollie and run it this > >>> weekend, I would appreciate any bug reports that you have. > >>> > >>> I will be around all weekend and ready to handle any fires that may > >>> arise, although while large in scale, these merges did not alter much > >>> of the base MH code. They did add or update support for a few Insteon > >>> devices for those who are interested. > >>> > >>> Kevin > >>> > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |
From: Jim D. <ji...@du...> - 2013-06-11 00:13:35
|
On 06/02/2013 10:59 AM, Jim Duda wrote: > On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: >> Another huge merge was done tonight. We now only have a few small issues remaining before we can push all of this to stable. >> >> If you could pull the master branch from hollie and run it this weekend, I would appreciate any bug reports that you have. > > Thanks for all the great Insteon enhancements. Really great stuff you've done for the project. > I updated last night and all is working normally in my house. The merge went fine and no compile issues. > > Jim > I'm having some problems after doing this big update. My PLM doesn't have any records in it. I've tried doing a scan link table and sync links on devices which should interface with it, but nothing seems to work. I have an insteon motion sensor which doesn't get messages to the PLM anymore. I've had this trouble in the past, and doing a PLM scan link table and sync links on the motion sensor resolved it in the past, it put the responder records back in the PLM. I've done a sync all link at the PLM a few times. I have two KeyPadLincs with surrogates which I use to update the paddle lamp state, but that isn't working either after the update. What might be wrong? Regards, Jim 06/10/13 08:05:47 PM Running: PLM scan link table 06/10/13 08:05:47 PM [Insteon_PLM] $PLM completed link memory scan: status: empty 06/10/13 08:05:47 PM [Insteon::ALDB_PLM] Link table health: empty 06/10/13 08:06:00 PM: Saving object states ... done 06/10/13 08:06:00 PM [Insteon::BaseObject] $front_walk::set(on, $light_front_walk) 06/10/13 08:06:00 PM [Insteon::BaseObject] $surrogate_kpl_button_D::set(100%, ) 06/10/13 08:06:00 PM [Insteon::BaseObject] received command/state acknowledge from $front_walk: on and data: ff 06/10/13 08:06:00 PM [Insteon_PLM] WARN: PLM memory does not contain link for: obj=$surrogate_kpl_button_D; command=on; extra=FF 06/10/13 08:06:10 PM Running: up bath sensor sync links 06/10/13 08:06:10 PM [Insteon::AllLinkDatabase] WARN The link table for $up_bath_sensor is out-of-sync. 06/10/13 08:06:10 PM [Insteon::AllLinkDatabase] WARN: Link NOT added, please rescan this device and sync again. 06/10/13 08:06:10 PM $up_bath_sensor completed sync links 06/10/13 08:06:15 PM Running: PLM scan link table 06/10/13 08:06:15 PM [Insteon_PLM] $PLM completed link memory scan: status: empty 06/10/13 08:06:15 PM [Insteon::ALDB_PLM] Link table health: empty > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite > It's a free troubleshooting tool designed for production > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap2 > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > > |
From: Kevin R. K. <ke...@kr...> - 2013-06-11 00:22:08
|
Jim, I can see the motion sensor errors in the log. The initial problem is that MH doesn't know the status of the motion sensor's link table. (I can look into ignoring deaf devices.) In the mean time, the following should work: 1. Put the Motion Sensor in Awake Mode (hold the set button for 4 seconds.) 2. Run Scan Link Table on the Motion Sensor 3. Run Sync Links on the Motion Sensor That should fix it, as for the keypadlincs, it looks like your PLM lost all link entries so you likely need to run sync links for them. If you have tried this and they are not linking, it is likely because MH doesn't know the state of their link tables. The following should work: 1. Run "Scan Changed Link Tables" under the PLM 2. Run "Sync Links" On Mon, Jun 10, 2013 at 5:13 PM, Jim Duda <ji...@du...> wrote: > On 06/02/2013 10:59 AM, Jim Duda wrote: > > On 05/31/2013 10:41 PM, Kevin Robert Keegan wrote: > >> Another huge merge was done tonight. We now only have a few small > issues remaining before we can push all of this to stable. > >> > >> If you could pull the master branch from hollie and run it this > weekend, I would appreciate any bug reports that you have. > > > > Thanks for all the great Insteon enhancements. Really great stuff > you've done for the project. > > I updated last night and all is working normally in my house. The merge > went fine and no compile issues. > > > > Jim > > > > I'm having some problems after doing this big update. My PLM doesn't have > any records in it. > I've tried doing a scan link table and sync links on devices which should > interface with it, but nothing seems to work. > I have an insteon motion sensor which doesn't get messages to the PLM > anymore. I've had this trouble in the past, and doing a PLM scan link > table and sync links on the motion sensor resolved it in the past, it put > the responder records back in the PLM. > I've done a sync all link at the PLM a few times. > I have two KeyPadLincs with surrogates which I use to update the paddle > lamp state, but that isn't working either after the update. > > What might be wrong? > > Regards, > > Jim > > 06/10/13 08:05:47 PM Running: PLM scan link table > 06/10/13 08:05:47 PM [Insteon_PLM] $PLM completed link memory scan: > status: empty > 06/10/13 08:05:47 PM [Insteon::ALDB_PLM] Link table health: empty > 06/10/13 08:06:00 PM: Saving object states ... done > 06/10/13 08:06:00 PM [Insteon::BaseObject] $front_walk::set(on, > $light_front_walk) > 06/10/13 08:06:00 PM [Insteon::BaseObject] > $surrogate_kpl_button_D::set(100%, ) > 06/10/13 08:06:00 PM [Insteon::BaseObject] received command/state > acknowledge from $front_walk: on and data: ff > 06/10/13 08:06:00 PM [Insteon_PLM] WARN: PLM memory does not contain link > for: obj=$surrogate_kpl_button_D; command=on; extra=FF > 06/10/13 08:06:10 PM Running: up bath sensor sync links > 06/10/13 08:06:10 PM [Insteon::AllLinkDatabase] WARN The link table for > $up_bath_sensor is out-of-sync. > 06/10/13 08:06:10 PM [Insteon::AllLinkDatabase] WARN: Link NOT added, > please rescan this device and sync again. > 06/10/13 08:06:10 PM $up_bath_sensor completed sync links > 06/10/13 08:06:15 PM Running: PLM scan link table > 06/10/13 08:06:15 PM [Insteon_PLM] $PLM completed link memory scan: > status: empty > 06/10/13 08:06:15 PM [Insteon::ALDB_PLM] Link table health: empty > > > > > > > > ------------------------------------------------------------------------------ > > Get 100% visibility into Java/.NET code with AppDynamics Lite > > It's a free troubleshooting tool designed for production > > Get down to code-level detail for bottlenecks, with <2% overhead. > > Download for free and get started troubleshooting in minutes. > > http://p.sf.net/sfu/appdyn_d2d_ap2 > > ________________________________________________________ > > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |
From: Jim D. <ji...@du...> - 2013-06-11 00:20:14
|
On 06/10/2013 08:13 PM, Jim Duda wrote: > > What might be wrong? Well, after sending this post, I went downstairs and power cycled the PLM. I then did a scan link table on the PLM, and they all came back. Why would the PLM report an empty link table, then have a full link table after power cycle? Regards, Jim 06/10/13 08:12:07 PM Running: PLM scan link table 06/10/13 08:12:16 PM [Insteon_PLM] $PLM completed link memory scan: status: good 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] Link table health: good 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $living_room_ceiling(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $kpl_button_A(03) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $kpl_button_B(04) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $kpl_button_C(05) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $kpl_button_D(06) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a0) record to $kpl_button_A (d1=01, d2=00, d3=03) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a1) record to $kpl_button_B (d1=01, d2=00, d3=04) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a2) record to $kpl_button_C (d1=01, d2=00, d3=05) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a3) record to $kpl_button_D (d1=01, d2=00, d3=06) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $backdoor(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $frontdoor(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $up_bath_sensor(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $courtyard_stairs(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $courtyard_button_A(03) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $courtyard_button_B(04) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $courtyard_button_C(05) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $courtyard_button_D(06) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a4) record to $courtyard_button_A (d1=01, d2=00, d3=03) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a5) record to $courtyard_button_B (d1=01, d2=00, d3=04) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a6) record to $courtyard_button_C (d1=01, d2=00, d3=05) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(a7) record to $courtyard_button_D (d1=01, d2=00, d3=06) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $kitchen(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $courtyard_flood(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $courtyard_post(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $garage_door(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $basement(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $bathroom_ceiling(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(10) record to $bathroom_ceiling (d1=01, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $bathroom_closet(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] responder record to $bathroom_hallway(01) (d1=00, d2=00, d3=00) 06/10/13 08:12:16 PM [Insteon::ALDB_PLM] cntlr(10) record to $bathroom_hallway (d1=01, d2=00, d3=00) > > Regards, > > Jim > > 06/10/13 08:05:47 PM Running: PLM scan link table > 06/10/13 08:05:47 PM [Insteon_PLM] $PLM completed link memory scan: status: empty > 06/10/13 08:05:47 PM [Insteon::ALDB_PLM] Link table health: empty > 06/10/13 08:06:00 PM: Saving object states ... done > 06/10/13 08:06:00 PM [Insteon::BaseObject] $front_walk::set(on, $light_front_walk) > 06/10/13 08:06:00 PM [Insteon::BaseObject] $surrogate_kpl_button_D::set(100%, ) > 06/10/13 08:06:00 PM [Insteon::BaseObject] received command/state acknowledge from $front_walk: on and data: ff > 06/10/13 08:06:00 PM [Insteon_PLM] WARN: PLM memory does not contain link for: obj=$surrogate_kpl_button_D; command=on; extra=FF > 06/10/13 08:06:10 PM Running: up bath sensor sync links > 06/10/13 08:06:10 PM [Insteon::AllLinkDatabase] WARN The link table for $up_bath_sensor is out-of-sync. > 06/10/13 08:06:10 PM [Insteon::AllLinkDatabase] WARN: Link NOT added, please rescan this device and sync again. > 06/10/13 08:06:10 PM $up_bath_sensor completed sync links > 06/10/13 08:06:15 PM Running: PLM scan link table > 06/10/13 08:06:15 PM [Insteon_PLM] $PLM completed link memory scan: status: empty > 06/10/13 08:06:15 PM [Insteon::ALDB_PLM] Link table health: empty > >> >> >> ------------------------------------------------------------------------------ >> Get 100% visibility into Java/.NET code with AppDynamics Lite >> It's a free troubleshooting tool designed for production >> Get down to code-level detail for bottlenecks, with <2% overhead. >> Download for free and get started troubleshooting in minutes. >> http://p.sf.net/sfu/appdyn_d2d_ap2 >> ________________________________________________________ >> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 >> >> > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > > |
From: Kevin R. K. <ke...@kr...> - 2013-06-11 00:23:54
|
On Mon, Jun 10, 2013 at 5:16 PM, Jim Duda <ji...@du...> wrote: > Well, after sending this post, I went downstairs and power cycled the PLM. > I then did a scan link table on the PLM, and they all came back. > Why would the PLM report an empty link table, then have a full link table > after power cycle? > Odd. It is possible the PLM got itself into some odd state. I don't think I have encountered this before, but at this stage I will chalk it up as one of the many oddities of the PLM. If it keeps happening let me know. |