Marcs insteon.mht The Historical Example

The following is a sample insteon.mht file from Marc Merlin. This file has long served as the primary example for new users.

Format = A
# -*- mode: perl-mode; -*-
#
# See mh/lib/read_table_A.pl  for definition of Format=A items
#

# My Insteon PLM Interface
INSTEON_PLM,   PLM #Cir 9

# mapping X10 commands
# See http://misterhouse.wikispaces.com/MhtFile for syntax
# X10I(tem/outlet) X10MS(motion sensor) X10SL(switchlink/remote) X10A(ppliance)
X10A,   A1,             garage_doors,   All_X10_lights|All_X10,         PLM,
# you want to use SL for a remote as mh will see 'on' and 'off'
X10SL,  A2,             remote_motion,  All_X10,                        PLM,
# whereas MS sends motion sensor results as 'motion'/'still' and 'bright'/'dark'
X10MS,  A3,             kitch_motion,   Sensors_X10|All_X10,            PLM,
X10SL,  A4,             kitch_light,    Sensors_X10|All_X10,            PLM,
# http://kbase.x10.com/wiki/Comparison_of_All_Motion_Sensors
X10MS,  A15,            garage_motion,  Sensors_X10|All_X10,            PLM,
# PLM X10 syntax doesn't support returning bright/dark, but SL will return ON/OFF
X10SL,  A16,            daylight,       Sensors_X10|All_X10,            PLM,

X10SL,  L2,             mbr_both_x10,   All_X10_lights|All_X10,         PLM,
X10SL,  L3,             mbr_lamp1_x10,  All_X10_lights|All_X10,         PLM,
X10SL,  L4,             mbr_lamp2_x10,  All_X10_lights|All_X10,         PLM,
X10SL,  L5,             br2_sw_x10,     All_X10_lights|All_X10,         PLM,
X10SL,  L6,             br2_lamp_x10,   All_X10_lights|All_X10,         PLM,
X10SL,  L9,             mus_on_pause,   All_X10_lights,                 PLM,
X10SL,  L10,            mus_vol,        All_X10_lights,                 PLM,
X10SL,  L11,            mus_prev_next,  All_X10_lights,                 PLM,
X10SL,  L12,            mus_line_vol,   All_X10_lights,                 PLM,
X10SL,  L16,            fmr_lightx10,   All_X10_lights|All_X10,         PLM,


# Switchlincs
INSTEON_SWITCHLINC,    1C.9E.E6,    f_fm_lt_ma,    All_Lights #2477D v6.5 1152 Cir 13
INSTEON_SWITCHLINCRELAY,    0B.B8.56,    f_kt_ov_lt_ma,    Kitchen  #2476s  v2.5 05190 0739 Cir 16

# Keypadlincs, see nice config file:
# http://www.nabble.com/Insteon-Scene-Problem-td17286990.html
# http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#toc2
INSTEON_KEYPADLINC,  0E.2A.3E:01, f_kt_pantry_lt_ma, All_Lights  #2486DWH6 v1.8 1719  Cir 16
INSTEON_KEYPADLINC,  0E.2A.3E:03, f_kt_pantry_lt_ma_a, Mon_Downstairs  #2486DWH6 v1.8 1719  Cir 16
INSTEON_KEYPADLINC,  0E.2A.3E:04, f_kt_pantry_lt_ma_b, All_Lights  #2486DWH6 v1.8 1719  Cir 16
INSTEON_KEYPADLINC,  0E.2A.3E:05, f_kt_pantry_lt_ma_c, All_Lights  #2486DWH6 v1.8 1719  Cir 16
INSTEON_KEYPADLINC,  0E.2A.3E:06, f_kt_pantry_lt_ma_d, All_Lights  #2486DWH6 v1.8 1719  Cir 16

##Motion Sensors
INSTEON_MOTIONSENSOR,  14.36.0F,  g_st_mt,  Sensors  #2420M V2.0 1910


## SCENES
# define relationship between switches (one to one, or scenes) for sync all functionality
# see http://misterhouse.wikispaces.com/Insteon+Linking+and+Scenes

# These are effectively 'PLM scenes'. PLM scenes are broadcast and can
# only be initiated by the PLM via mh.
# this is a bit confusing: both_fmr_scene is an mh scene, but cannot be
# assigned to any controller, it only has meaning within mh.

# PLM Scenes are stored in the PLM and responders are told about them, you
# can assign numbers after 1 (1 is reserved)
INSTEON_ICONTROLLER, 10, both_fmr_scene, all_scenes
SCENE_MEMBER, fmr_mast, both_fmr_scene, 100%, 2s
SCENE_MEMBER, fmr_slav, both_fmr_scene, 100%, 2s

INSTEON_ICONTROLLER, 11, gar_both_scene, all_scenes
SCENE_MEMBER, gar_mast, gar_both_scene, 100%, 2s
SCENE_MEMBER, gar_slav, gar_both_scene, 100%, 2s



# Whereas those are Inter Device Scenes from switch to target switch to
# switch or switch to device links.
# These scenes definitions are important because they're the only way for
# mh to know that when you depress fmr_slav, the link switches fmr_mast too,
# and if you setup all your pairings in mh, you can sync them from your mh
# config file to all your switches a *lot* faster than you would program the
# switches directly by hand.
#
# 3 way switches, each switch it linked to the other one
SCENE_MEMBER, fmr_slav, fmr_mast, 100%, 2s
SCENE_MEMBER, fmr_mast, fmr_slav, 100%, 2s

SCENE_MEMBER, gar_slav, gar_mast, 100%, 2s
SCENE_MEMBER, gar_mast, gar_slav, 100%, 2s

# here a switch is linked to a lamplinc
SCENE_MEMBER, br2_lamp, br2_sw, 100%, 2s

# this motion sensor controls both garage switches
#SCENE_MEMBER, gar_mast, gar_mos1, 100%, 2s
#SCENE_MEMBER, gar_slav, gar_mos1, 100%, 2s


# A target for insteon initiators has to be a list
# of devices, you cannot have a PLM scene as a target.
# I.e. you can't do this:
#SCENE_MEMBER, gar_both_scene, rlink_blk1_1, 100%, 2s
# you need to do that:
SCENE_MEMBER, gar_mast, rlink_blk1_1, 100%, 2s
SCENE_MEMBER, gar_slav, rlink_blk1_1, 100%, 2s
SCENE_MEMBER, yard_lights, rlink_blk1_2, 100%, 2s
SCENE_MEMBER, lvr_dmr, rlink_blk1_3, 100%, 2s
SCENE_MEMBER, lvr_lamp, rlink_blk1_4, 100%, 2s
SCENE_MEMBER, fmr_mast, rlink_blk1_5, 100%, 2s
SCENE_MEMBER, fmr_slav, rlink_blk1_5, 100%, 2s
SCENE_MEMBER, fmr_outside, rlink_blk1_6, 100%, 2s