| Author |
|
k2zs
Senior Member
Joined: October 22 2009
Location: United States
Online Status: Offline
Posts: 113
|
| Posted: July 25 2012 at 18:03 | IP Logged
|
|
|
Hello everyone,
I have a few questions about mixing in some of the new
2477 dual band switches.
Currently running PH v2.1b with a 2412S PLM. If I start
mixing in some 2477DH switches will they work and provide
better communications through the wireless? I've already
had the electrician swap a 2476DH with a 2477DH and all I
did was an address update for the device. It seems to be
working as defined as a 2476DH, will it work that way?
Should I try auto-detecting the next device swapped to
get a definition into PH or doesn't that matter?
I do have a 2413S modem on hand but I'm a little leery of
making that swap. With around 300 devices on the network
I don't want to screw anything up...
Any thoughts?
__________________
Scott, K2ZS
Home Automation Ideas
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: July 25 2012 at 18:44 | IP Logged
|
|
|
Switching to Dual Band devices is transparent except for one important area. SmartLabs started introducing I2CS (enhanced Insteon protocol) devices after March of 2012. Most were of the Relay type but there has been a report of a ToggleLinc Dimmer now being I2CS. That means it will not be long before all the Dimmers come as I2CS devices.
Powerhome does not yet have support for I2CS devices. This means that no programmatic linking of I2CS devices is possible for now.
The PLM does not make any difference except that it does not participate in the RF side of the Insteon Mesh Network. The one exception about the PLM is the 2413 support approx 1000 link records where the 2412 supports 2000+ link records.
Edited by grif091 - July 25 2012 at 18:45
__________________
Lee G
|
| Back to Top |
|
| |
k2zs
Senior Member
Joined: October 22 2009
Location: United States
Online Status: Offline
Posts: 113
|
| Posted: July 25 2012 at 18:58 | IP Logged
|
|
|
Thanks Lee,
So what does that mean for the the time being? I just
completed an order for 8-2477DH, 6-2477D, and 6-2477S
devices.
While I was on-line I found that SmartHome doesn't even
offer the non-dual band devices any longer except for the
2476D's
Are we going to have to manually link/cross-link devices
for the time being or isn't that even an option?
Edited by k2zs - July 25 2012 at 18:59
__________________
Scott, K2ZS
Home Automation Ideas
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: July 25 2012 at 19:20 | IP Logged
|
|
|
The SwitchLinc Relay is I2CS and will have to be linked/cross-linked using manual methods. The Dimmers are an unknown. SmartLabs has published nothing regarding what devices on what schedules. For months there has been the separation between Relay and Dimmer devices. All the new Relay type devices are coming with I2CS firmware and none of the Dimmers had I2CS. In the last week or two one user has reported a ToggleLinc Dimmer with symptoms that match using an I2CS device without I2CS support. Once the first Dimmer (ToggleLinc Dimmer) has shown up with I2CS firmware the other Dimmers are sure to follow. Just have no idea on what schedule.
This is a list of known I2CS devices
Motion Sensor (2420M)
FanLinc (2475F)
SwitchLinc (2476S)
LampLinc (2457D2)
ApplianceLinc (2456S3) Rev 4.6 Firmware v.42
OutletLinc Relay (2473S) Rev4.7 Firmware v.42
ToggleLinc Relay (2466S) Firmware v.41
I/O Linc (2450)
240V N/O Load Controller (2477SA1)
InLineLinc Relay w/sense (2475S2)
Thermostat (2491T7E)
Thermostat (2441TH)
ToggleLinc Dimmer (2466D) this is the first dimmer reported to have I2CS
The 0x0F (dec 15) command can be issued to determine if a given device has I2CS firmware. If the ACK response cmd2 value is 02 or FF the device is I2CS.
EDIT: Dave posted back in April I think he is working on an update that will have I2CS support. There is no target date for this update.
Edited by grif091 - July 25 2012 at 19:22
__________________
Lee G
|
| Back to Top |
|
| |
judetf
Senior Member
Joined: January 23 2008
Online Status: Offline
Posts: 234
|
| Posted: July 27 2012 at 11:07 | IP Logged
|
|
|
Does this mean that until the new PH version comes out we can't use PH to create PLM-based links to the I2CS devices? And that, therefore, we can't do things like create triggers to catch the I2CS devices?
Thanks
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: July 27 2012 at 11:14 | IP Logged
|
|
|
Links involving I2CS devices cannot be done programmatically until an updated PH2 with I2CS support is released.
Whatever links are needed will have to be done with the Set button.
__________________
Lee G
|
| Back to Top |
|
| |
k2zs
Senior Member
Joined: October 22 2009
Location: United States
Online Status: Offline
Posts: 113
|
| Posted: July 27 2012 at 18:36 | IP Logged
|
|
|
Would that involve linking to any/all devices in that group
or only to the PLM and then the PLM would handle the
control of cross linked devices?
__________________
Scott, K2ZS
Home Automation Ideas
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: July 27 2012 at 19:31 | IP Logged
|
|
|
Sorry, I don't follow the question.
Perhaps this will cover it. If not please add some additional detail. The link that cannot be created is between an I2CS device and any other device you want to link to it. The I2CS device cannot be linked to the PLM. The I2CS device cannot be linked to some other device.
I2CS does not change the way devices are physically linked together. As devices needed to be linked yesterday, they need to be linked the same way tomorrow. However you would link the device if it was not I2CS, it needs to be linked the exact same way when it is an I2CS device. The concept of linking and cross-linking is not different because an I2CS device is involved.
What cannot be done today is programmatically create a link or cross-link where an I2CS device is involved. All the links where an I2CS is the Controller or the Responder can only be done with Set button linking.
Stated another way, think of the device as non-I2CS. What links are needed to accomplish the desired effect are not different because the device is I2CS. The only difference today is PH2 cannot create the link when an I2CS device is on one end of the link.
__________________
Lee G
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: July 27 2012 at 20:05 | IP Logged
|
|
|
Stated in non-technical terms, an I2CS device cannot be referenced in the Links tab nor the PLM Groups tab.
Edited by grif091 - July 27 2012 at 20:05
__________________
Lee G
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: August 21 2012 at 12:08 | IP Logged
|
|
|
See link for I2CS support on 2.1.4
I2CS support for 2.1.4
__________________
Lee G
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Migrating to dual band devices?
