Menu
▾
▴
[mh] Misterhouse vs Insteon 2413U: Help request
|
From: <jr...@jr...> - 2012-02-10 23:41:52
|
From: Neil Cherry <nc...@li...>
Date: Fri, 10 Feb 2012 18:04:13 -0500
Can we see a sample of an insteon device from the insteon.mht file?
Here's the whole thing:
----------------------------------------------------------------
Format = A
# -*- mode: perl-mode; -*-
#
# See mh/lib/read_table_A.pl for definition of Format=A items
#
# added by jrd from http://misterhouse.wikispaces.com/Insteon
# My Insteon PLM Interface
INSTEON_PLM, PLM,
# A switchLinc module for my PLM to control
# PLM 09.D9.EE
# 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,
# IPLD for applicancelink and lamplinc / IPLL for switchlinks and keypadlinc
IPLL, 0F.05.06:01, mbr_lamp1, All_Lights|mbr_both, PLM, # v4.0 switchlink dimmer
IPLL, 0F.B7.05:01, mbr_lamp2, All_Lights|mbr_both, PLM, # v4.2 switchlink dimmer
IPLL, 0F.23.02:01, br2_sw, All_Lights, PLM, # v4.1 switchlink relay
IPLD, 0F.71.94, br2_lamp, All_Lights, PLM, # v4.3 lamplink
IPLL, 0F.27.36:01, gar_mast, All_Lights|gar_both|out_lights, PLM, # v4.1 switchlink relay
IPLL, 0F.26.87:01, gar_slav, All_Lights|gar_both|out_lights, PLM, # v4.1 switchlink relay
IPLL, 0F.05.4E:01, fmr_mast, All_Lights|fmr_both, PLM, # v4.0 switchlink dimmer
IPLL, 0F.0F.2A:01, fmr_slav, All_Lights|fmr_both, PLM, # v4.0 switchlink dimmer
IPLL, 10.94.88:01, fmr_outside, All_Lights|out_lights, PLM, # v4.1 switchlink relay
IPLL, 0F.0F.9A:01, lvr_dmr, All_Lights|LVR, PLM, # v4.0 switchlink dimmer
IPLD, 0A.99.E5, lvr_lamp, All_Lights|LVR, PLM, # v4.0 icon lamplink
IPLD, 0F.83.2F, kitch_appl, Appliances, PLM, # v4.1 appliance link
IPLD, 0F.82.87, yard_lights, All_Lights, PLM, # v4.1 appliance link
# http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#toc3
IPLD, 11.8E.1C, gar_mos1, Sensors, PLM,1001 # v1.1
# Keypadlincs, see nice config file:
# http://www.nabble.com/Insteon-Scene-Problem-td17286990.html
# http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#toc2
IPLL, 0A.39.D1:01, rlink_blk1_1, buttons, PLM,0005 # v1.0
IPLL, 0A.39.D1:02, rlink_blk1_2, buttons, PLM,
IPLL, 0A.39.D1:03, rlink_blk1_3, buttons, PLM,
IPLL, 0A.39.D1:04, rlink_blk1_4, buttons, PLM,
IPLL, 0A.39.D1:05, rlink_blk1_5, buttons, PLM,
IPLL, 0A.39.D1:06, rlink_blk1_6, buttons, PLM,
# 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)
IPLL, PLM:10, both_fmr_scene, all_scenes, PLM
SCENE_MEMBER, fmr_mast, both_fmr_scene, 100%, 2s
SCENE_MEMBER, fmr_slav, both_fmr_scene, 100%, 2s
IPLL, PLM:11, gar_both_scene, all_scenes, PLM
SCENE_MEMBER, gar_mast, gar_both_scene, 100%, 2s
SCENE_MEMBER, gar_slav, gar_both_scene, 100%, 2s
IPLL, PLM:12, all_out_scene, all_scenes, PLM
SCENE_MEMBER, gar_mast, all_out_scene, 100%, 2s
SCENE_MEMBER, gar_slav, all_out_scene, 100%, 2s
SCENE_MEMBER, fmr_outside, all_out_scene, 100%, 2s
IPLL, PLM:13, mbr_both_scene, all_scenes, PLM
SCENE_MEMBER, mbr_lamp1, mbr_both_scene, 100%, 2s
SCENE_MEMBER, mbr_lamp2, mbr_both_scene, 100%, 2s
IPLL, PLM:14, fmr_lvr_scene, all_scenes, PLM
SCENE_MEMBER, fmr_mast, fmr_lvr_scene, 100%, 0.4s
SCENE_MEMBER, fmr_slav, fmr_lvr_scene, 100%, 0.4s
SCENE_MEMBER, lvr_lamp, fmr_lvr_scene, 100%, 0.4s
SCENE_MEMBER, lvr_dmr, fmr_lvr_scene, 100%, 0.4s
IPLL, PLM:15, fmr_lvr_scene_slow, all_scenes, PLM
SCENE_MEMBER, fmr_mast, fmr_lvr_scene_slow, 100%, 2s
SCENE_MEMBER, fmr_slav, fmr_lvr_scene_slow, 100%, 2s
SCENE_MEMBER, lvr_lamp, fmr_lvr_scene_slow, 100%, 2s
SCENE_MEMBER, lvr_dmr, fmr_lvr_scene_slow, 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
|