Re: [mh] Upgrading an Insteon 2412S to a 2413U for reliability due to dual-band

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Using an extension cord, I found that plugging the PLM into any outlet
in my basement, blocked full communication to the switches on the
first floor.

I moved the extension cord to the first floor and the switches worked fine.

So back to my original question.. How well does the Dual-Band of the
2413U PLM and the 2477S/D switches.  I really dislike having the chase
down signal suckers.. I thought Insteon was more immune to them.

thanks,
tom

On Wed, Jan 14, 2015 at 6:06 PM, Tom <tom...@gm...> wrote:
> yes.. and when I do, the PLM sees it..   retries a few times then fails.
>
> -----------------------------------------------------------------------
>
> 01/14/15 06:04:22 PM Running: breakfast light link to interface
>
> 01/14/15 06:04:22 PM [Insteon_PLM] DEBUG2: Sending
> obj=$breakfast_light; command=off; extra=00 incurred delay of 117.51
> seconds; starting hop-count: 3
>
> 01/14/15 06:04:22 PM [Insteon_PLM] DEBUG3: Sending  PLM raw data:
> 02620a6d200f1300
>
> 01/14/15 06:04:22 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>
> 01/14/15 06:04:22 PM [Insteon_PLM] DEBUG3: Received PLM raw data:
> 02620a6d200f130006
>
> 01/14/15 06:04:22 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>         PLM Response: (06) ACK
>
>
> 01/14/15 06:04:22 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge:
> obj=$breakfast_light; command=off; extra=00
>
> 01/14/15 06:04:24 PM [Insteon::BaseMessage] WARN: now resending
> obj=$breakfast_light; command=off; extra=00 after 1 attempts.
>
> 01/14/15 06:04:24 PM [Insteon_PLM] DEBUG2: Sending
> obj=$breakfast_light; command=off; extra=00 incurred delay of 119.55
> seconds; starting hop-count: 3
>
> 01/14/15 06:04:24 PM [Insteon_PLM] DEBUG3: Sending  PLM raw data:
> 02620a6d200f1300
>
> 01/14/15 06:04:24 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>
> 01/14/15 06:04:24 PM [Insteon_PLM] DEBUG3: Received PLM raw data:
> 02620a6d200f130006
>
> 01/14/15 06:04:24 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>         PLM Response: (06) ACK
>
>
> 01/14/15 06:04:24 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge:
> obj=$breakfast_light; command=off; extra=00
>
> 01/14/15 06:04:26 PM [Insteon::BaseMessage] WARN: now resending
> obj=$breakfast_light; command=off; extra=00 after 2 attempts.
>
> 01/14/15 06:04:26 PM [Insteon_PLM] DEBUG2: Sending
> obj=$breakfast_light; command=off; extra=00 incurred delay of 121.58
> seconds; starting hop-count: 3
>
> 01/14/15 06:04:26 PM [Insteon_PLM] DEBUG3: Sending  PLM raw data:
> 02620a6d200f1300
>
> 01/14/15 06:04:26 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>
> 01/14/15 06:04:26 PM [Insteon_PLM] DEBUG3: Received PLM raw data:
> 02620a6d200f130006
>
> 01/14/15 06:04:26 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>         PLM Response: (06) ACK
>
>
> 01/14/15 06:04:26 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge:
> obj=$breakfast_light; command=off; extra=00
>
> 01/14/15 06:04:28 PM [Insteon::BaseMessage] WARN: now resending
> obj=$breakfast_light; command=off; extra=00 after 3 attempts.
>
> 01/14/15 06:04:28 PM [Insteon_PLM] DEBUG2: Sending
> obj=$breakfast_light; command=off; extra=00 incurred delay of 123.62
> seconds; starting hop-count: 3
>
> 01/14/15 06:04:28 PM [Insteon_PLM] DEBUG3: Sending  PLM raw data:
> 02620a6d200f1300
>
> 01/14/15 06:04:28 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>
> 01/14/15 06:04:28 PM [Insteon_PLM] DEBUG3: Received PLM raw data:
> 02620a6d200f130006
>
> 01/14/15 06:04:28 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>         PLM Response: (06) ACK
>
>
> 01/14/15 06:04:28 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge:
> obj=$breakfast_light; command=off; extra=00
>
> 01/14/15 06:04:30 PM [Insteon::BaseMessage] WARN: now resending
> obj=$breakfast_light; command=off; extra=00 after 4 attempts.
>
> 01/14/15 06:04:30 PM [Insteon_PLM] DEBUG2: Sending
> obj=$breakfast_light; command=off; extra=00 incurred delay of 125.65
> seconds; starting hop-count: 3
>
> 01/14/15 06:04:30 PM [Insteon_PLM] DEBUG3: Sending  PLM raw data:
> 02620a6d200f1300
>
> 01/14/15 06:04:30 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>
> 01/14/15 06:04:30 PM [Insteon_PLM] DEBUG3: Received PLM raw data:
> 02620a6d200f130006
>
> 01/14/15 06:04:30 PM [Insteon_PLM] DEBUG4:
>
>          PLM Command: (0262) insteon_send
>
>               To Address: 0a:6d:20
>
>            Message Flags: 0f
>
>                 Message Type: (000) Direct Message
>
>               Message Length: (0) Standard Length
>
>                    Hops Left: 3
>
>                     Max Hops: 3
>
>          Insteon Message: 1300
>
>                        Cmd 1: (13) Light OFF
>
>                        Cmd 2: 00
>
>         PLM Response: (06) ACK
>
>
> 01/14/15 06:04:30 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge:
> obj=$breakfast_light; command=off; extra=00
>
> 01/14/15 06:04:32 PM [Insteon::BaseInterface] WARN: number of retries
> (5) for obj=$breakfast_light; command=off; extra=00 exceeds limit.
> Now moving on...
>
> On Wed, Jan 14, 2015 at 12:38 PM, Greg <gr...@gm...> wrote:
>> I'm still kind of a newbie, but from "Browse Insteon", did you do
>> "link to interface" on the switches? I think you might need to do that
>> for each switch to know about the PLM.
>>
>> On Wed, Jan 14, 2015 at 8:32 AM, Tom <tom...@gm...> wrote:
>>> Could I simply be linking incorrectly?  What is the proper way to link
>>> my switches to the PLM?
>>> thanks,
>>> tom
>>>
>>> On Sun, Jan 11, 2015 at 10:11 PM, Tom <tom...@gm...> wrote:
>>>> I currently have a 2412S and a few days ago it stopped controlling my
>>>> 2476D and 2476S switches.  MH communicates with the PLM but the PLM
>>>> doesn't seem to communicate with the switches.  It does communicate
>>>> with my X10 switches
>>>>
>>>> I reset the PLM and tried relinking the switches to no avail.
>>>>
>>>> results from link scan
>>>> -------------------------------------------
>>>> 01/11/15 09:38:44 PM [Insteon_PLM] DEBUG3: Received PLM acknowledge:
>>>> obj=$breakfast_light; command=set_address_msb; extra=0F
>>>>
>>>> 01/11/15 09:38:48 PM [Insteon::BaseInterface] WARN: number of retries
>>>> (5) for obj=$breakfast_light; command=set_address_msb; extra=0F
>>>> exceeds limit.  Now moving on...
>>>>
>>>> 01/11/15 09:38:48 PM [Insteon::BaseInterface] WARN: Message Timeout:
>>>> Now calling callback: &Insteon::_get_next_linkscan_failure(1)
>>>>
>>>> 01/11/15 09:38:48 PM [Scan all link tables] WARN: failure occurred
>>>> when scanning $breakfast_light.  Moving on...
>>>> -------------------------------------------
>>>>
>>>> Now the troubleshooting begins...
>>>>
>>>> I recently moved a bunch of things around the house so it may be
>>>> something I plugged in to a different outlet.
>>>>
>>>> When I press the switch, I don't see anything in the MH logs (I have
>>>> debug turned on to 4... debug=insteon:4)
>>>>
>>>> Would the 2413U (and 2477D/S switches) help with reliability issues?
>>>> For the most part, Insteon works fine but when it doesn't, it's a pain
>>>> to track down the issue. It seems to be very susceptible to issues on
>>>> the power line.  I also have the 2442 Signal Enhancer, but I don't see
>>>> any benefit from it.
>>>>
>>>> thanks,
>>>> tom
>>>
>>> ------------------------------------------------------------------------------
>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>> http://p.sf.net/sfu/gigenet
>>> ________________________________________________________
>>> To unsubscribe from this list, go to: https://lists.sourceforge.net/lists/listinfo/misterhouse-users
>>>