From: Edward B. <eb...@se...> - 2012-11-24 22:31:03
|
Hi Everyone, A quick .02 from a bystander user - been using MH for a while, simple motion activation (occupancy monitoring) type stuff. I had just switched to the Insteon branch a month or so ago, and I love the idea of the merge. Having said that I grabbed a copy with git clone git://github.com/hollie/misterhouse.git mh - adjusted my mht file after reading a bit, and so far I have gotten it to run without complaint, but the X10 and Insteon stuff I have setup doesn't work. A little debug and I see insteon is being seen, but none of my simple stuff seems to work. A simple motion sensor timer never sees motion. I tried a few different state_now matches for Basement_Motion (i.e. on vs. motion) nothing so far. <code> # noloop=start my $Basement_Motion_timer = new Timer; # noloop=end if(state_now $Basement_Motion eq "motion") { set $Basement_Motion_timer 120; print_log "Setting Basement_Motion Timer to 120"; print_log "$Basement_Motion"; if(state_now $Basement_Motion eq "motion") { speak ("Someone is on the basement stairs"); print_log "Basement Stairwell Activity"; } else { speak "All clear on the Basement stairwell"; } } if(expired $Basement_Motion_timer) { print_log(" Timer expired for Basement Motion"); } </code> Using an mht of: Format = A INSTEON_PLM, PLM INSTEON_MOTIONSENSOR, 11.A6.6A, Basement_Motion, Sensors, 1000 When the insteon motion sensor is tripped I see this with insteon debug on - but the code example above doesn't see it ... 11/24/12 10:26:56 AM [Insteon::BaseInterface] command:on; type:alllink; group: 01 11/24/12 10:26:56 AM [Insteon::BaseInterface] command:on; type:alllink; group: 01 11/24/12 10:27:00 AM: Saving object states ... done 11/24/12 10:27:56 AM [Insteon::BaseInterface] command:off; type:alllink; group: 01 11/24/12 10:27:56 AM [Insteon::BaseInterface] command:off; type:alllink; group: 01 As far as X10 goes, no X10 was working at all ..using an mht like: X10I,A1,Basement_Light_Overhead, Lights|Basement, X10MS,C3,FrontDoor_Motion, Sensors, X10MS,C4,StairWell_Motion, Sensors, X10I,C5,Basement_Light, Lights|Basement, X10I,C6,Basement_Office_Light, Lights|Basement, X10I,C2,Basement_Light2, Lights|Basement, X10MS,C1,Garage_Motion, Sensors, X10A,D9,App_Fan, Appliances|Basement, Makes MH startup create dummy interfaces and lots of broken blanks...i.e.: 11/24/12 09:05:31 AM [Insteon_PLM] setting default xmit delay to: 0.15 11/24/12 09:05:31 AM [Insteon_PLM] setting x10 xmit delay to: 0.5 Warning: Dummy_Interface #0: Creating dummy interface for id=A1, state= and interface=. Warning: Dummy_Interface #1: Creating dummy interface for id=, state= and interface=. 11/24/12 09:05:31 AM [X10_Sensor] Calling Serial_match_add_hook Warning: Dummy_Interface #2: Creating dummy interface for id=, state= and interface=. Warning: Dummy_Interface #3: Creating dummy interface for id=C5, state= and interface=. Warning: Dummy_Interface #4: Creating dummy interface for id=C6, state= and interface=. Warning: Dummy_Interface #5: Creating dummy interface for id=C2, state= and interface=. Warning: Dummy_Interface #6: Creating dummy interface for id=, state= and interface=. Warning: Dummy_Interface #7: Creating dummy interface for id=D9, state= and interface=. 11/24/12 09:05:31 AM [Insteon_PLM] setting default xmit delay to: 0.15 11/24/12 09:05:31 AM [Insteon_PLM] setting x10 xmit delay to: 0.5 Warning: Dummy_Interface #8: Creating dummy interface for id=A1, state= and interface=. Warning: Dummy_Interface #9: Creating dummy interface for id=, state= and interface=. Warning: Dummy_Interface #10: Creating dummy interface for id=, state= and interface=. Warning: Dummy_Interface #11: Creating dummy interface for id=C5, state= and interface=. Warning: Dummy_Interface #12: Creating dummy interface for id=C6, state= and interface=. Warning: Dummy_Interface #13: Creating dummy interface for id=C2, state= and interface=. Warning: Dummy_Interface #14: Creating dummy interface for id=, state= and interface=. Warning: Dummy_Interface #15: Creating dummy interface for id=D9, state= and interface=. I am going through things like read_table_A.pl and stuff like lib/Insteon/AllLinkDatabase.pm and BaseInterface.pm to try to see if I just have bad syntax in my .mht or.... :) Just some thoughts - thanks to everyone for keeping this list and project alive - Edward -----Original Message----- From: Eloy Paris [mailto:pe...@ch...] Sent: Saturday, November 24, 2012 10:27 AM To: mis...@li... Subject: Re: [mh] Branch merge phase 2: let's git rid of that separate insteon branch! Hi Jim, On 11/24/2012 09:53 AM, Jim Duda wrote: > On 11/24/2012 09:35 AM, Jim Duda wrote: >> >> >> Thank you. I need to choose a different default port for android other than 4444. > > After further review, 4444 is no different than any other default. Each installation > needs to manage their ports. The default for server_proxy_port has traditionally been > 8085. I guess 4444 was just a coincidence? > > By removing server_android_port in mh.ini, this should resolve the issue for others. I have not followed this discussion regarding server_android_port and mh.ini but now I'm curious... Is(was) the problem that the default mh.ini includes a server_android_port entry? If so, does this mean that a server was getting started by default (without any user configuration)? Cheers, Eloy Paris.- ---------------------------------------------------------------------------- -- 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 |