islandguy642 Posted October 24, 2016 Posted October 24, 2016 Hi; After searching the forum without success for a solution to my problem I've decide to make this post. I'm attempting to install a 2842-222 Motion Sensor but I'm getting this error but also the can't determine insteon engine error. Fri 10/21/2016 11:41:15 AM : [37 9D 72 ] Added to list of devices to link to ISY Fri 10/21/2016 11:41:15 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 0D 00 Fri 10/21/2016 11:41:15 AM : [iNST-ACK ] 02 62 37.9D.72 0F 0D 00 06 (00) Fri 10/21/2016 11:41:17 AM : [iNST-SRX ] 02 50 37.9D.72 2B.50.C9 23 0D 02 (02) Fri 10/21/2016 11:41:17 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 10/21/2016 11:41:17 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 10 00 Fri 10/21/2016 11:41:17 AM : [iNST-ACK ] 02 62 37.9D.72 0F 10 00 06 ID-REQ (00) Fri 10/21/2016 11:41:26 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 10 00 Fri 10/21/2016 11:41:26 AM : [iNST-ACK ] 02 62 37.9D.72 0F 10 00 06 ID-REQ (00) Fri 10/21/2016 11:41:35 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 10 00 Fri 10/21/2016 11:41:35 AM : [iNST-ACK ] 02 62 37.9D.72 0F 10 00 06 ID-REQ (00) Fri 10/21/2016 11:41:39 AM : [37 9D 72 0 ] Calibrating engine version Fri 10/21/2016 11:41:39 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 10/21/2016 11:41:39 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 10/21/2016 11:41:48 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 10/21/2016 11:41:48 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 10/21/2016 11:41:57 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 10/21/2016 11:41:57 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 10/21/2016 11:42:01 AM : [37 9D 72 0 ] Failed to add device, reason 9 Fri 10/21/2016 11:42:01 AM : [All ] Writing 0 bytes to devices Could the logical position of my access points be the reason?
larryllix Posted October 24, 2016 Posted October 24, 2016 Welcome to the forum! All battery devices must be in linking mode, enabled by holding the linking button down for about 5-6 seconds until the flashing LED is seen. This is to save battery life while sitting idle at other times. Make sure you factory reset all new Insteon devices beofre attempting to do anything with them in ISY. Out f my 11 about 5 of them did really nasty things that will drive you crazy seemingly impossible. Make sure you have set your dip switches for software programming and then you resostats inside mean nothing. Most of us use send ON only as the off consumes batteries faster and confuses your ISY programming. I don't use an access points with Insteon. I do, however have many dual band devices that repeat and strengthen my Insteon network.
PhanTomiZ Posted October 24, 2016 Posted October 24, 2016 Make sure you have set your dip switches for software programming and then you resostats inside mean nothing. Most of us use send ON only as the off consumes batteries faster and confuses your ISY programming. I don't use an access points with Insteon. I do, however have many dual band devices that repeat and strengthen my Insteon network. I have many motion sensors. I use both "on" and "Off" commands. If you have your sensors set to ON only then how do you use these sensors in "scenes"? For every scene, you would need a resulting program to turn devices off?
Techman Posted October 24, 2016 Posted October 24, 2016 (edited) I have many motion sensors. I use both "on" and "Off" commands. If you have your sensors set to ON only then how do you use these sensors in "scenes"? For every scene, you would need a resulting program to turn devices off? The motion sensors will time out after a preset time. In your program use STATUS not CONTROL in your IF clause to trigger your scenes. When the sensor turns off then so will your scene as the status is no longer true. Edited October 24, 2016 by Techman
oberkc Posted October 24, 2016 Posted October 24, 2016 I have many motion sensors. I use both "on" and "Off" commands. If you have your sensors set to ON only then how do you use these sensors in "scenes"? For every scene, you would need a resulting program to turn devices off? Yes, if you intend to use motion sensors in scenes to turn on/off other devices, then on and off both need to be enabled. Scenes also tend to be a little quicker responding and work even if the ISY fails. Als, you can use a combination (scenes to turn on, programs to turn off) if that suits your needs. I have found that, for me, I want to apply more contraints on motion sensors than available internally (such as the ability to override) so I tend to use programs.
PhanTomiZ Posted October 24, 2016 Posted October 24, 2016 I thought the general rule of thumb was to use Scenes as much as possible and programs secondary. So if the ISY craps out, then your program will no longer have control of this device; therefore, if the MS is "On only" then the device or devices it is controlling will stay in the last state for as long as the ISY is down. That being said, my ISY has been chugging along for 62.5 days since my last update and has not crashed. Come to think of it, it has only crashed once in the last year or since installing ... Of all my MS, only one is setup where it is "On only" in the settings as I wish to adjust the timeout via another program.
Teken Posted October 24, 2016 Posted October 24, 2016 I thought the general rule of thumb was to use Scenes as much as possible and programs secondary. So if the ISY craps out, then your program will no longer have control of this device; therefore, if the MS is "On only" then the device or devices it is controlling will stay in the last state for as long as the ISY is down. That being said, my ISY has been chugging along for 62.5 days since my last update and has not crashed. Come to think of it, it has only crashed once in the last year or since installing ... Of all my MS, only one is setup where it is "On only" in the settings as I wish to adjust the timeout via another program. Generally speaking its best practice to use scenes where ever possible. The reliance on programs for complex scene management will leave the home in a unknown state should there ever be a power issue. Even though the bulk of the members here aren't geared to think about their home as a system. Its always best practice to plan and assume for the worst case scenario. Failure to do so will impact the home, family, and the over all WAF - Assuming it matters to you!
islandguy642 Posted October 24, 2016 Author Posted October 24, 2016 Sorry for not responding earlier. This is not my first motion sensor install just my first outside of my home network. I don't entirely understand how the motion sensors connect to the ISY. There are no dual-band devices other than the wireless routers(3). Oh I'm still getting reason 9 or reason 3 as an error depending on where i stand.
Teken Posted October 24, 2016 Posted October 24, 2016 (edited) Sorry for not responding earlier. This is not my first motion sensor install just my first outside of my home network. I don't entirely understand how the motion sensors connect to the ISY. There are no dual-band devices other than the wireless routers(3). Oh I'm still getting reason 9 or reason 3 as an error depending on where i stand. Almost all Insteon devices being sold today are dual band. If the place of residence has no dual band hardware than a AP / RE must be in place to translate the MS RF signal to the 2413S PLM. NOTE: This assumes the 2413S PLM is not with in the RF distance of the motion sensor. Edited October 24, 2016 by Teken
islandguy642 Posted October 24, 2016 Author Posted October 24, 2016 I'm not using a 2413S PLM..I'm using a hub pro modded to work as a PLM. There are dual band 2477d switches all over.
Teken Posted October 24, 2016 Posted October 24, 2016 I'm not using a 2413S PLM..I'm using a hub pro modded to work as a PLM. There are dual band 2477d switches all over. OK, let's start with some basics here shall we . . . 1. Where do you live? Canada, USA, Other? 2. What exact model motion sensor are you using provide a direct link from SH. 3. What is the power / frequency your area uses?
islandguy642 Posted October 24, 2016 Author Posted October 24, 2016 1) Barbados 2) http://www.smarthome.com/insteon-2842-222-wireless-motion-sensor.html 3) 50hz 110v
Teken Posted October 24, 2016 Posted October 24, 2016 (edited) 1) Barbados 2) http://www.smarthome.com/insteon-2842-222-wireless-motion-sensor.html 3) 50hz 110v Is the modified HUB using the same 915 Mhz carrier wave? If not it won't work as its on a totally different frequency. If your modified HUB is in fact using the same 915 Mhz frequency it may very well be the device is not supported in the HUB. This was seen on another modified HUB by a member here . . . NOTE: If the HUB is operating on 50 Hz power line its almost a given the RF frequency won't be 915 Mhz. Edited October 24, 2016 by Teken
islandguy642 Posted October 24, 2016 Author Posted October 24, 2016 I believe the hub is using the same carrier wave. I have the same exact setup home and the motion sensor added with no problems. There was an ESR300 WAP in the room where the motion was...
stusviews Posted October 25, 2016 Posted October 25, 2016 WiFi is an entirely different band than Insteon RF. No chance of interference from the EnGenius Router.
islandguy642 Posted October 25, 2016 Author Posted October 25, 2016 Okay..so it must be something wrong with that network configuration because the same motion sensor added at home. Tue 10/25/2016 08:02:03 AM : [37 9d 72 ] Added to list of devices to link to ISY Tue 10/25/2016 08:02:03 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 0D 00 Tue 10/25/2016 08:02:03 AM : [iNST-ACK ] 02 62 37.9D.72 0F 0D 00 06 (00) Tue 10/25/2016 08:02:12 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 0D 00 Tue 10/25/2016 08:02:12 AM : [iNST-ACK ] 02 62 37.9D.72 0F 0D 00 06 (00) Tue 10/25/2016 08:02:13 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 0D 02 (02) Tue 10/25/2016 08:02:13 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:13 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 10 00 Tue 10/25/2016 08:02:13 AM : [iNST-ACK ] 02 62 37.9D.72 0F 10 00 06 ID-REQ (00) Tue 10/25/2016 08:02:21 AM : [iNST-TX-I1 ] 02 62 37 9D 72 0F 10 00 Tue 10/25/2016 08:02:21 AM : [iNST-ACK ] 02 62 37.9D.72 0F 10 00 06 ID-REQ (00) Tue 10/25/2016 08:02:23 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 23 10 00 ID-REQ (00) Tue 10/25/2016 08:02:23 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 10/25/2016 08:02:23 AM : [iNST-SRX ] 02 50 37.9D.72 10.01.44 8B 02 44 (44) Tue 10/25/2016 08:02:23 AM : [std-Broadcast] 37.9D.72-->10.01.44, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:23 AM : [37 9D 72 0 ] Calibrating engine version Tue 10/25/2016 08:02:23 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 10/25/2016 08:02:23 AM : [iNST-ACK ] 02 62 00.00.00 00 00 00 15 (00) Tue 10/25/2016 08:02:32 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 10/25/2016 08:02:32 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 10/25/2016 08:02:33 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 2F 00 (00) Tue 10/25/2016 08:02:33 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:34 AM : [iNST-ERX ] 02 51 37 9D 72 32 B1 BC 12 2F 00 00 01 0F FF 01 E2 01 2B 50 C9 03 00 00 97 Tue 10/25/2016 08:02:34 AM : [Ext-Direct ] 37.9D.72-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Tue 10/25/2016 08:02:34 AM : [37 9D 72 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Tue 10/25/2016 08:02:34 AM : [37 9D 72 1 ] Start : Adding device to ISY Tue 10/25/2016 08:02:34 AM : [37 9D 72 1 ] Finish : Adding device to ISY was Successful Tue 10/25/2016 08:02:34 AM : [37 9D 72 1 ] Link 0 : 0FF8 [E20132B1BC010001] Saving [E20132B1BC010001] Tue 10/25/2016 08:02:34 AM : [37 9D 72 2 ] Start : Adding device to ISY Tue 10/25/2016 08:02:34 AM : [37 9D 72 2 ] Finish : Adding device to ISY was Successful Tue 10/25/2016 08:02:34 AM : [37 9D 72 2 ] Link 1 : 0FF0 [E20232B1BC010002] Saving [E20232B1BC010002] Tue 10/25/2016 08:02:34 AM : [37 9D 72 3 ] Start : Adding device to ISY Tue 10/25/2016 08:02:34 AM : [37 9D 72 3 ] Finish : Adding device to ISY was Successful Tue 10/25/2016 08:02:34 AM : [37 9D 72 3 ] Link 2 : 0FE8 [E20332B1BC010003] Saving [E20332B1BC010003] Tue 10/25/2016 08:02:34 AM : [37 9D 72 0 ] Successfully added device Tue 10/25/2016 08:02:34 AM : [All ] Writing 24 bytes to devices Tue 10/25/2016 08:02:35 AM : [37 9D 72 1 ] Link 0 : 0FF8 [E20132B1BC010001] Writing [E20132B1BC010001] Tue 10/25/2016 08:02:35 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 02 0F FF 08 E2 01 32 B1 BC 01 00 01 35 Tue 10/25/2016 08:02:35 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 02 0F FF 08 E2 01 32 B1 BC 01 00 01 35 06 (00) Tue 10/25/2016 08:02:35 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 2F 00 (00) Tue 10/25/2016 08:02:35 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:35 AM : [MNG-LNK-RSP ] 02 6F 41 A2 01 37 9D 72 10 01 44 06 Tue 10/25/2016 08:02:35 AM : [PLM ] Group 1 : Writing Responder Link matching [37 9D 72 1 ] Link 0 : 0FF8 [E20132B1BC010001] Tue 10/25/2016 08:02:36 AM : [37 9D 72 1 ] Link 1 : 0FF0 [E20232B1BC010002] Writing [E20232B1BC010002] Tue 10/25/2016 08:02:36 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 02 0F F7 08 E2 02 32 B1 BC 01 00 02 3B Tue 10/25/2016 08:02:36 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 02 0F F7 08 E2 02 32 B1 BC 01 00 02 3B 06 (00) Tue 10/25/2016 08:02:36 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 2F 00 (00) Tue 10/25/2016 08:02:36 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:37 AM : [MNG-LNK-RSP ] 02 6F 41 A2 02 37 9D 72 10 01 44 06 Tue 10/25/2016 08:02:37 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 23 2F 00 (00) Tue 10/25/2016 08:02:37 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 10/25/2016 08:02:37 AM : [PLM ] Group 2 : Writing Responder Link matching [37 9D 72 1 ] Link 1 : 0FF0 [E20232B1BC010002] Tue 10/25/2016 08:02:37 AM : [37 9D 72 1 ] Link 2 : 0FE8 [E20332B1BC010003] Writing [E20332B1BC010003] Tue 10/25/2016 08:02:37 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 02 0F EF 08 E2 03 32 B1 BC 01 00 03 41 Tue 10/25/2016 08:02:37 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 02 0F EF 08 E2 03 32 B1 BC 01 00 03 41 06 (00) Tue 10/25/2016 08:02:37 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 2F 00 (00) Tue 10/25/2016 08:02:37 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:38 AM : [MNG-LNK-RSP ] 02 6F 41 A2 03 37 9D 72 10 01 44 06 Tue 10/25/2016 08:02:38 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 23 2F 00 (00) Tue 10/25/2016 08:02:38 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 10/25/2016 08:02:38 AM : [iNST-DUP ] Previous message ignored. Tue 10/25/2016 08:02:38 AM : [PLM ] Group 3 : Writing Responder Link matching [37 9D 72 1 ] Link 2 : 0FE8 [E20332B1BC010003] Tue 10/25/2016 08:02:38 AM : [37 9D 72 1 ] Link 3 : 0FE0 [0000000000000000] Writing [00..............] Tue 10/25/2016 08:02:38 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 Tue 10/25/2016 08:02:38 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00) Tue 10/25/2016 08:02:39 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 2F 00 (00) Tue 10/25/2016 08:02:39 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:39 AM : [37 9D 72 1 ] Link 4 : 0FD8 : Writing High Water Byte Tue 10/25/2016 08:02:39 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 Tue 10/25/2016 08:02:39 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00) Tue 10/25/2016 08:02:39 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 2F 00 (00) Tue 10/25/2016 08:02:39 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 10/25/2016 08:02:40 AM : [iNST-ERX ] 02 51 37 9D 72 32 B1 BC 12 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1 Tue 10/25/2016 08:02:40 AM : [Ext-Direct ] 37.9D.72-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Tue 10/25/2016 08:02:40 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 Tue 10/25/2016 08:02:40 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00) Tue 10/25/2016 08:02:43 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2F 2F 00 (00) Tue 10/25/2016 08:02:43 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Tue 10/25/2016 08:02:44 AM : [iNST-ERX ] 02 51 37 9D 72 32 B1 BC 12 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1 Tue 10/25/2016 08:02:44 AM : [Ext-Direct ] 37.9D.72-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Tue 10/25/2016 08:02:44 AM : [iNST-TX-I2CS] 02 62 37 9D 72 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 Tue 10/25/2016 08:02:44 AM : [iNST-ACK ] 02 62 37.9D.72 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 06 (00) Tue 10/25/2016 08:02:45 AM : [iNST-SRX ] 02 50 37.9D.72 32.B1.BC 2B 2F 00 (00) Tue 10/25/2016 08:02:45 AM : [std-Direct Ack] 37.9D.72-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 It's not like the ISY(at other location) can't see the motion sensor..communication fails. Note I was as far as I could be from the ISY when I tested the same motion sensor home
Teken Posted October 25, 2016 Posted October 25, 2016 Can you better describe the entire Insteon network that exists in the new home? What type of ISY and firmware are you using at the new home? Have you confirmed proper coupling / bridging via the 4 tap beacon test as outlined in the full users manual? Also have you indeed confirmed the frequency the modified HUB is using vs the MS you have in hand? Perhaps some photo's of the controller, HUB, MS showing their stickers would help here.
Brian H Posted October 25, 2016 Posted October 25, 2016 (edited) I believe there is another thread here. Where reason 9 was the device did not provide its starting Link Database address. I do see some responses from the sensor in the starting post. So it must be communicating with the problem network. At least somewhat. Edited October 25, 2016 by Brian H
islandguy642 Posted October 25, 2016 Author Posted October 25, 2016 I'm going to abandon the motion sensor install until I can test the electrical side of things or get 2443 access point. Until then thanks for the replies.
Teken Posted October 25, 2016 Posted October 25, 2016 I'm going to abandon the motion sensor install until I can test the electrical side of things or get 2443 access point. Until then thanks for the replies. If your area uses 110 VAC @ 50 Hz you can not use a AP / RE. As they operate on 60 Hz hence why I am asking for your confirmation as to the hardware in use and their specifications.
islandguy642 Posted October 27, 2016 Author Posted October 27, 2016 Update: It's fairly possible that the majority of problems I'm encountering are because the electrical system I'm working with here is three phase while home is single phase. I'm not too well versed in the electrical side as yet but this is progress.
Teken Posted October 27, 2016 Posted October 27, 2016 Update: It's fairly possible that the majority of problems I'm encountering are because the electrical system I'm working with here is three phase while home is single phase. I'm not too well versed in the electrical side as yet but this is progress. Once again what does the modified HUB indicate as the RF frequency in use?!? If the HUB indeed uses 50 Hz the RF sending frequency more than likely won't be 915 MHz. Keeping in mind this assumes you purchased items for the EU. If you purchased NA parts directly from SH there are quite a few insteon devices which support 50/60 Hz and offer 100-277 VAC. If that is the case your first step is to confirm proper coupling / bridging via the 4 tap beacon test outlined in the full users manual. Since the home is 3 phase this is paramount to couple all three phases.
Recommended Posts