From: peter <p.w...@gm...> - 2011-07-07 00:14:44
|
Thanks for your input Marc, Responses embedded. On 7/6/2011 1:30 AM, Marc MERLIN wrote: > On Tue, Jul 05, 2011 at 02:37:03AM -0400, peter wrote: >> What should I be using for SVN version that will be fairly stable and >> that dosen't break any of the hardware I plan to use? Any input on version? Note to self: Get a clearer concept of how SVN is supposed to work... >> Should I ditch the CM11a and get a 2413U or 2412N now? My CM11a has >> been a bit finicky so I dont want to spend much time on it if I have >> another viable option > A 2413 S or U should do anything a CM11 can do and much more. > Note that the 2412 isn't being sold by smarthome anymore, but the 2413 > should work fine. > > I would avoid the 2412N, reda the comments: > http://blog.smarthome.com/2010/07/28/5448/ > http://www.mvlug.org/JoePfeiffer/SlowGetWithSmartLinc > > Also, I do not believe the 2412N works with mh currently. > > My interest in the "N" is based on this https://sourceforge.net/mailarchive/message.php?msg_id=27230647 thread... I would always opt for the dual band hardware - unless there were problems that came with it of course. I know the "N" version is power only which also goes against it. Were it to have support and both bands, it would be possible to locate the PLM in a spot more optimal for the RF side without a lot of fuss (in my case) which was one of the reasons for considering it. The other was that I understood that using it directly could simplify some setup tasks with insteon devices. >> Should I be installing MH in /opt/mh or another spot? > Up to you. > I use /var/local/src/misterhouse/mh and have mh be a symlink to the tree I > want to use (mh, mh-insteon, etc...). > Processing... >> In the short term I need: >> # To be able to control a handful of X-10 devices already on hand and >> installed. >> # Ability to monitor and control via web. This is kind of a given and >> dosen't seem to be an issue ATM. > mh will do this fine. There is a caveat with insteon though, insteon > commmands aren't fire and forget, you have to wait for the ack. > The mh web interface does not deal with that and therefore shows the old > state of the device because the ACK hasn't been received yet (refresh fixes > this). > Good to know... >> # To utilize 1-wire for temp, humidity (have humichrons - hope they are >> supported by now), and possibly some slow I/O - initially to control > I use 1-wire as you know I do not have humichrons, so I can't comment on > them. > Anyone else??? They are supported by owfs and readable with owhttpd ( I think). I didn't do any special config or startup options and my humidity is showing -31.2052. It may be correct but I doubt our RH is 31% now... I now need to understand how best to get MH to read and write to the devices I am wanting to use and revisit the configuration options for the OWFS and related programs... > Marc Again, thanks for speaking up Marc, Peter |