From: Brian W. <bra...@gm...> - 2012-11-21 03:02:12
|
With regards to the Insteon Thermostat, I have hit an issue that may require significant work to allow it to function with both the old and new versions of the adapter. I'm not certain which Insteon Engine version the original was running, but the one they replaced it with recently is an I2CS device. Not only does this require a link to the PLM before it will respond to any command, but it also requires any set commands to be extended messages with checksums. I believe the original version would function today with the changes in my tstat branch, but I cannot verify since I no longer have the hardware. I2CS devices also do not support the peek/poke style link management we do for everything other than the PLM (that I am aware of). Since we have code to write links using ALDB commands, it should not be difficult to overcome. We will need to differentiate the devices and I prefer to discover and store that info as opposed to define it. I will likely extend Insteon::BaseDevice to include an engine attribute and provide for an option to discover it for any device that has an undefined engine. That said, I have decided that I will not use the program modes of the Venstar to adjust temperatures as an incentive to get this work completed. I do miss waking to a warm house ;) -- Brian On Tue, Nov 20, 2012 at 5:38 PM, Eloy Paris <pe...@ch...> wrote: > Hi Lieven, > > I am now running branch_merge_phase2. So far so good, but I think that > is expected because I was running the "insteon" branch before and > branch_merge_phase2 is just the "insteon" branch on top of an up-to-date > trunk. > > By the way, regarding releasing what we have as 3.0 at some point in the > future, http://misterhouse.wikispaces.com/Insteon+Redux contains this > warning: > > "WARNING: Support for the Insteon thermostat and irrigation code has not > yet been ported. If you rely on this functionality, do NOT attempt to > use this code base until the corresponding code has been ported." > > I don't use any of these devices so I am not affected, but we will break > some installations if we make a new release without support for these > devices. I guess not upgrading until someone can finish the new INSTEON > stack is an option for these users... > > Cheers, > > Eloy Paris.- > > On 11/20/2012 03:47 PM, Lieven Hollevoet wrote: > > > Hello all, > > > > 2 weeks ago I brought the insteon branch up to date with the changes in > the master branch. > > > > Two people reported to the list that there were running the merged > branch without major problems. Thanks to the testers. Note: Jim noticed > that the default xAP hub is no longer enabled per default in mh.ini, that > is to me the only fluke we encountered. > > > > So I had the feeling the time was right to advance to stage 2. I just > merged the insteon branch into master. Of course, I did this in a separate > branch suitedly called 'branch_merge_phase2'. > > > > Before I apply the changes really into the master branch I would like to > request more testing of this new branch. If you are still doubting if it is > worth the effort to check out git: now it is the time to do so :-). This > new branch contains all of current master and all of current insteon, so > there should be goodies for everyone. > > > > Steps to get a copy of the merged branch for testing: > > > > git clone git://github.com/hollie/misterhouse.git mh_test_ph2 > > git checkout branch_merge_phase2 > > > > point your start script to point to the 'mh_test_ph2' folder and fire > her up! > > > > Comments and feedback are welcome, pull requests to fix the comments and > feedback are even more appreciated :-) If you want assistance on how to > contribute code, please have a look here: > https://github.com/hollie/misterhouse/wiki/Contributing > > > > If all goes well and no showstopping flaws are detected, I would like to > merge the changes to master, say in another two weeks from now. Then we can > make a new MH release (version 3.0?). > > > > Kind regards, > > Lieven. > > > > > > > ------------------------------------------------------------------------------ > > Monitor your physical, virtual and cloud infrastructure from a single > > web console. Get in-depth insight into apps, servers, databases, vmware, > > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > > Pricing starts from $795 for 25 servers or applications! > > http://p.sf.net/sfu/zoho_dev2dev_nov > > ________________________________________________________ > > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > > > > > ------------------------------------------------------------------------------ > Monitor your physical, virtual and cloud infrastructure from a single > web console. Get in-depth insight into apps, servers, databases, vmware, > SAP, cloud infrastructure, etc. Download 30-day Free Trial. > Pricing starts from $795 for 25 servers or applications! > http://p.sf.net/sfu/zoho_dev2dev_nov > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |