Page 1 of 156 1231151101 ... LastLast
Results 1 to 10 of 1553

Thread: Insteon PLM Component

  1. #1
    Join Date
    Jun 2008

    Default Insteon PLM Component

    Hi All,

    I put together an Insteon PLM Component. The PLM (firmware version .63) is very robust relative to the PLC. Only 1 lockup over many months of use. The component supports a wide range of Insteon devices including support for both I1 and I2 engines (ie extended command devices).

    The component has been in development for a little over 3 years and now is about 25000 lines of code!

    Brief PDF Help file

    Version .836

    Bug fixes for smoke sensor

    Version .834

    Smoke Bridge early support
    Micro On/Off support

    Version. 824

    T stat fixes

    Version .821

    Fixes for leak sensor
    Venstar T Stat changes ? maybe fixes?

    Version .818

    Leak sensor support

    Version .815

    Added window coverings devices
    Added 2 wire switchlinc

    Version .811

    Fix for dual band dimmers

    Version .804

    Added work around for ApplianceLincs that do not follow the Insteon protocol correctly.
    Additions thermostat support.

    Version .802

    Bug fix for Keypadlinc and setting toggle/non toggle modes
    Bug fix for PLM AllLink command result reporting

    Version .800

    thermostat and rf small bug fixes

    Version .797

    Small Radio device fix.

    Version .796

    Support for latest thermostats
    Support for Insteon light bulb

    Version .782

    Support for new Insteon I2CS devices
    Misc bug fixes.

    Version .768
    dui bug fix for Globals page

    Version .764

    EZUIRT support
    Added ability to easily replace failed devices. On the devices tab, see Replace. This will copy all settings from the old device to the new for DevCat 1 and 2 devices, including all keypadlinc settings. Big time saver for replacing bad devices
    Misc bug fixes

    Version .754

    More improvements in link read/writing
    Updated support for new devices

    Unzip into the Girder\luascript\component directory. Restart Girder. Goto the Component Manager, Enable, See Under the Lighting tab on the left.

    Please post comments and problems to this thread.
    Last edited by Mike C; June 11th, 2014 at 09:43 PM.

  2. #2
    Join Date
    Aug 2006
    North Carolina


    Hey Mike, good to hear from you could you explain what this PLM Component will do for me?

  3. #3
    Join Date
    Jun 2008


    Quote Originally Posted by jmbraben View Post
    Hey Mike, good to hear from you could you explain what this PLM Component will do for me?

    The primary feature is reliability. The PLM is much more solid than the PLC/SDM combo.

    In terms of the component design it offers greater flexibility and support for current and future devices including both the Insteon 1 and 2 Engines. You can download and look at the plugin without PLM to see the various options etc.

    I haven't compiled a feature list... in short there really is no comparison between the 2. For the first time, I have actually been happy with the Insteon devices in my home.

  4. #4
    Join Date
    Aug 2005



    Great work. I'll try out your plug-in as soon as I can get a PLM from smarthome.


  5. #5
    Join Date
    Mar 2007


    Thank You!!

    Just ordered the PLM. I'll be so happy to get rid of SDM and it's lock ups every 3-4 days.

  6. #6
    Join Date
    May 2004


    This news makes my day. I can't wait to order a PLM.
    Beware of the robot.

  7. #7
    Join Date
    Jun 2008


    quick features list.

    Works with PLM only. Firmware version .63 is recommended.

    Designed to allow for future powerline interfaces with minimal work.

    Supports greater than 1 powerline interface (not extensively tested at this time)

    Comprehensive link management including support for I1 and I2 remote record/link retreival, editing, and addition. Easy group/scene management and setup.

    Sophisticated error recover when trying to read/write remote records. Ability to restart and recover failed device writing even between Girder restarts.

    Easy ability to rebuild lost links as the component tracks all links that it discovers or builds.

    Autofail over for I2 to I1 reading/writing when extended data commands fail (happens when an I2 device is > 2 hops from the sending device)

    Comprehensive device monitoring which can be set for each device.

    Autodevice discovery and spidering of new devices from existing links.

    Command throttling and paring for rapid commands for changing light levels - automatically scaled to the device location in the network.

    Device command hop and transaction time monitoring - to allow seeing how well each device on your network is receiving commands from the PLM, and to allow you to see how changing location of network bridges and/or noise filters changes powerline communication.

    Comprehensive setup of Keypadlinc devices, including button configuration etc. Note: may need some work with newest firmware keypadlincs and changes as these devices start using the I2 engines.

    Sending Alllink Commands can be set to wait for all cleanup messages to be completed or can interupt these for greater speed.

    Remotelinc programming and control. Ie. can setup remotelincs to send heartbeat messages, LED settings, Beep settings etc.

    Tracks load presence/absense for devices that have this functionality.

    Extensible archiecture to make add new devices fast and easy.

    Group/Scene state tracking for all devices.

    Integration for the G5 Device Manager (all device and group control is done this way).

    I am sure there are a few other things in there as well...

  8. #8
    Join Date
    Aug 2005



    Fantastic feature list. I ordered a PLM and am really looking forward to this new component.


  9. #9
    Join Date
    Jun 2008


    Quote Originally Posted by vitello View Post

    Fantastic feature list. I ordered a PLM and am really looking forward to this new component.

    Great... it better work well for you then

  10. #10
    Join Date
    Jun 2008


    at 10 posts, so some screenshots are attached.

    First tab shows the transports (ie powerline interfaces in available to the component).

    On this page, you specify

    1. the default interface to use for send commands to/from devices.

    2. the default group to autolink devices as responders. default is group 254. so sending an alllink command to group 254 controls all of these devices. you do not need to autolink if you do not want to.

    3. autolink devices as controllers allows the component to receive instant updates when the devices change states (with some exceptions most notably the lamplincs etc).

    this tab is used to configure PLM's. you need to name each PLM you want to attach and select the correct serial port. no other settings here but you can see the PLM's ID, and link state - ie. if you press the SET button to enter link mode.

    on this tab you can sell all of your devices and their status (ie ok or not). you also set the component to automatically get their status when the component starts. global device monitoring is set here and the rate (in seconds) is also configurable. spidering of device links means that new device's discovered in another devices link database are automatically added to the components device list.

    the device tab is one of the most important. it gives you an comprehensive look at a device's status and in particular performance of the device on the insteon network. you can see reliability, average hops, average transaction times and number of transactions. this gives you the opportunity to play with noise filters and signal bridges to improve device performance. you also can see the device specific device categories and insteon engine. a list of all links in the device's database is also shown. unwanted links can be removed. the status of the components read of the database is shown. you can request the database to be updated using the update records database. this is done automatically if a device's link delta (also shown) changes. note: if the link database status is in error, then the component will not attempt a reread - you have to manual request the database be updated.

    the update button rereads the device type and any specific device settings. mostly this should not be required. the ping button can be used to test a device and to see how it responds.

    source is how the device was found by the component.

    interface selects which powerline interface to use to communicate with the device - as mentioned above, the use of the component with > 1 PLM has not been extensively tested.

    monitor is used to select the frequency a device is polled.
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	PLM-16.jpg 
Views:	4167 
Size:	42.6 KB 
ID:	4881   Click image for larger version. 

Name:	PLM-15.jpg 
Views:	4129 
Size:	19.1 KB 
ID:	4882   Click image for larger version. 

Name:	PLM-14.jpg 
Views:	4130 
Size:	58.5 KB 
ID:	4883   Click image for larger version. 

Name:	PLM-13.jpg 
Views:	4158 
Size:	68.0 KB 
ID:	4884   Click image for larger version. 

Name:	PLM-10.jpg 
Views:	490 
Size:	72.1 KB 
ID:	4885  

    Last edited by Mike C; July 1st, 2008 at 08:40 PM.

Page 1 of 156 1231151101 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts