kipplitz Posted September 5, 2017 Posted September 5, 2017 I am definitely new to this so bear that in mind... While I started adding devices I got to one and then I am now getting a constant stream of Status Requests. Is this normal? Tue 09/05/2017 02:06:13 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:13 PM : [ X10] J14/Status Request (10) Tue 09/05/2017 02:06:15 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:15 PM : [ X10] J14/Status Request (10) Tue 09/05/2017 02:06:15 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:15 PM : [ X10] J14/Status Request (10) Tue 09/05/2017 02:06:16 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:16 PM : [ X10] J14/Status Request (10) Tue 09/05/2017 02:06:17 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:17 PM : [ X10] J14/Status Request (10) Tue 09/05/2017 02:06:18 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:18 PM : [ X10] J14/Status Request (10) Tue 09/05/2017 02:06:19 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:19 PM : [ X10] J14/Status Request (10) Tue 09/05/2017 02:06:22 PM : [X10-RX ] 02 52 FF 80 Tue 09/05/2017 02:06:22 PM : [ X10] J14/Status Request (10) Thanks, Kip
stusviews Posted September 5, 2017 Posted September 5, 2017 Try rebooting the ISY (Configuration, bottom of System panel).
Brian H Posted September 5, 2017 Posted September 5, 2017 No that is not normal. Do you have any X10 devices? Do you have an X10 Coupler Repeater between the two incoming power lines or a Smarthome BoosterLinc? If you do what have a Coupler Repeater. Try turning it Off. Many of them misread the tail end of an Insteon command as an X10 one and try to repeat it. BoosterLincs have also been reported to be problems sometimes. Even with the later ones said to be Insteon friendly. Do you have the A10/X10 firmware add on for the ISY994i?
kipplitz Posted September 6, 2017 Author Posted September 6, 2017 Update, I just got home from work and left the diagnostic window up and running, It has been sending this command out all day up to and including now. I will try a reboot after I post this. I tried sending on/off commands to a couple switches that were already in the system and you could see those commands intertwined with that same repeating data. I am too new at this to know what caused it or why so thank you all for your input. I do not have a single X10 device in the entire Shouse (Shop/House) and it is fairly simple. All brand new items just ordered in the last 90 days and installed this weekend. About 12 Insteon Dimmers, 4 Insteon Switches, 5 - 6 button controllers and 1 - 8 button controller. Using the ISY/PLM combo from Smarthome plugged in to a dedicated circuit back to the main panel. All devices are Dual Band. There are no couplers or repeaters installed at this point although I do have the passive Insteon coupler from Smarthome but did not get to it yet. I was saving that panel work for last. I will try to get it installed one night this week. I did not purchase A10/X10 upgrade, do I need to? I simply got the ISY994i ZW/IR Pro. Got the Zwave model as I do have three Schlage Zwave deadbolts to add eventually. Here are a few excerpts from the log: Tue 09/05/2017 07:30:11 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:12 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:12 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:13 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:13 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:13 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:13 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:13 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:13 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:15 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:15 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:16 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:16 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:17 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:17 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:17 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:17 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:18 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:18 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:18 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:18 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:19 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:19 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:19 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:19 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:20 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:20 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:21 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:21 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:21 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:21 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:22 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:22 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:22 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:22 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:22 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:22 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:23 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:23 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:23 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:23 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:25 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:25 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:26 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:26 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:30:27 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:27 PM : [ X10] J/Status Request (10) Tue 09/05/2017 03:56:47 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 03:56:48 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 03:56:48 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:06:48 PM : [ Time] 16:06:49 0(0)Tue 09/05/2017 04:15:38 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:38 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:15:41 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:41 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:15:42 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:42 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:15:45 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:45 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:15:47 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:47 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:15:49 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:49 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:15:50 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:50 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:15:55 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:15:55 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:16:00 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:16:00 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:16:01 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:16:01 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:16:03 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:16:03 PM : [ X10] J14/Status Request (10)Tue 09/05/2017 04:16:08 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 04:16:08 PM : [ X10] J14/Status Request (10) Thank you everyone again for your time and insight. Kip
kipplitz Posted September 6, 2017 Author Posted September 6, 2017 Rebooted as per suggestion. Opened back up Admin Console and the devices I have entered (3 of them) all show red exclamation points and pop up boxes saying no communication. Did a manual queary and they all came back. Now, same thing going on in Event Viewer as before. Excerpt Tue 09/05/2017 07:51:22 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:23 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:23 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:24 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:25 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:26 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:26 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:27 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:27 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:30 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:30 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:32 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:32 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:33 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:35 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:35 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:36 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:36 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:37 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:38 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:39 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:40 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:40 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:40 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:42 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:43 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:44 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:47 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:48 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:49 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:51 PM : [ 3A 30 F6 1] ERR 0Tue 09/05/2017 07:51:51 PM : [ 3A 30 F6 1] ST 0Tue 09/05/2017 07:51:51 PM : [ 3A 30 F6 1] OL 255Tue 09/05/2017 07:51:51 PM : [ 3A 30 F6 1] RR 28Tue 09/05/2017 07:51:52 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:53 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:57 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:51:58 PM : [ 3A 31 11 1] ERR 0Tue 09/05/2017 07:51:58 PM : [ 3A 31 11 1] ST 255Tue 09/05/2017 07:51:58 PM : [ 3A 31 11 1] OL 255Tue 09/05/2017 07:51:58 PM : [ 3A 31 11 1] RR 28Tue 09/05/2017 07:51:58 PM : [ 44 80 71 1] ERR 0Tue 09/05/2017 07:51:58 PM : [ 44 80 71 1] ST 0Tue 09/05/2017 07:51:58 PM : [ 44 80 71 1] OL 255Tue 09/05/2017 07:51:58 PM : [ 44 80 71 1] RR 28Tue 09/05/2017 07:51:59 PM : [ 44 80 71 2] ST 0Tue 09/05/2017 07:51:59 PM : [ 44 80 71 3] ST 0Tue 09/05/2017 07:51:59 PM : [ 44 80 71 4] ST 0Tue 09/05/2017 07:51:59 PM : [ 44 80 71 5] ST 0Tue 09/05/2017 07:51:59 PM : [ 44 80 71 6] ST 0Tue 09/05/2017 07:51:59 PM : [ 44 80 71 7] ST 0Tue 09/05/2017 07:51:59 PM : [ 44 80 71 8] ST 0Tue 09/05/2017 07:52:00 PM : [ 45 AB CD 1] ERR 0Tue 09/05/2017 07:52:00 PM : [ 45 AB CD 1] ST 0Tue 09/05/2017 07:52:00 PM : [ 45 AB CD 1] OL 255Tue 09/05/2017 07:52:00 PM : [ 45 AB CD 1] RR 28Tue 09/05/2017 07:52:01 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:02 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:02 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:03 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:04 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:05 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:05 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:06 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:07 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:07 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:08 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:09 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:10 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:10 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:11 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:12 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:12 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:13 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:52:14 PM : [ X10] J/Status Request (10) After sending a command from Agave. The lights did function as expected but a little laggy to be honest. Tue 09/05/2017 07:55:41 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:55:46 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:55:47 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:55:55 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:55:56 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:56:16 PM : [ 45 AB CD 1] ST 255Tue 09/05/2017 07:56:23 PM : [ 45 AB CD 1] ST 0Tue 09/05/2017 07:56:30 PM : [ 3A 30 F6 1] ST 255Tue 09/05/2017 07:56:33 PM : [ 3A 30 F6 1] ST 0Tue 09/05/2017 07:56:35 PM : [ 3A 31 11 1] ST 0Tue 09/05/2017 07:56:38 PM : [ 3A 31 11 1] ST 255Tue 09/05/2017 07:57:12 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:57:25 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:57:37 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:57:41 PM : [ X10] J/Status Request (10)Tue 09/05/2017 07:57:43 PM : [ X10] J/Status Request (10)
Brian H Posted September 6, 2017 Posted September 6, 2017 Thank you for the added information. As you have no X10 in the installation at all. You definitely do not need the A10/X10 firmware add on. This looks like a signal received over the power lines or RF not sent by the ISY994i. 02 52 is the message sent from the PLM to the ISY994i. For an X10 message received. Tue 09/05/2017 07:30:21 PM : [X10-RX ] 02 52 FF 80Tue 09/05/2017 07:30:21 PM : [ X10] J/Status Request (10) I don't have some of the features you are using. I hope someone can add information for you.
larryllix Posted September 6, 2017 Posted September 6, 2017 Have you factory reset every Insteon device before linking them to ISY?
Brian H Posted September 6, 2017 Posted September 6, 2017 Good Point. Factory reset is a good thing to do. We have seen strange things in new modules from factory tests and not removed before shipping. You may also want to open the Event Viewer in Level 3 and do nothing but monitor the incoming messages. If you still see the firestorm. Something is making some noise. Real long shot here. Do you by chance have a TED power monitoring system? They communicate on the power line with a constant 132KHz message stream. At the Zero Crossing point in the power cycle. Insteon is 131.65KHz. They do a number on an X10 120KHz signal. I am sure it would also do a number on Insteon.
paulbates Posted September 6, 2017 Posted September 6, 2017 I don't believe its your ISY or your PLM. This can be caused by something on the powerline that's not X10, but the PLM interprets as X10. Something on the powerline that's making noise. The fact that its housecode J and status request is telling. In an X10 message, House code J is all address bits set Status Request is all function bits set In my X10 days, Housecode J was to be avoided and not assigned for this reason. Any changes to your power system? A new power meter, electical work.. or a new device like a motor? Paul
kipplitz Posted September 6, 2017 Author Posted September 6, 2017 Update, First, sincerely, thank you for your input and help. I hope to get to the point I can share and help from a knowledge base on this as all of you have done. Two Thumbs Up! Ok, so I did a complete reset on each Insteon device, PLM and ISY and started from scratch. Before I started adding devices I monitored the console and that stream of status requests was still there. Soooo...I picked up the PLM and ISY, unplugged them and moved to a completely new location in the shop. Plugged in and monitored for about 30 minutes and saw no activity. Added all devices back in, setup a few scenes and programs, tested and went to bed. Woke up this morning and it is still working like a champ and not a single x10 J Status request. Looks like noise on the power line as was suggested in this thread. The location I was using was a dedicated line back to the panel sharing it with a home theater receiver, Sonos, wifi router, cable modem and Ethernet switch. Basically an area in a closet to hide all this stuff. I will get some noise filters and see if I can go back to using that location. If not, it will be happy in its current home. Thank you all, Kip
Brian H Posted September 6, 2017 Posted September 6, 2017 Thank you for the update. The equipment you mentioned can cause power line noise. Though most have an internal filter on the AC to prevent it. Filters made for Insteon/X10 should help. Some generic filters and power line conditioners. May absorb the Insteon/X10 power line signals as noise.
Teken Posted September 7, 2017 Posted September 7, 2017 I would love to see the OP follow up as to the outcome by unplugging one single device in that previous location while monitoring the level 3 error logs to identify which device has caused this specific J14 code. I honestly don't think anyone has ever posted such a X-10 problem before so am very curious to learn what it is. Sent from my iPhone using Tapatalk
kipplitz Posted September 8, 2017 Author Posted September 8, 2017 Teken, When I get a free moment this weekend I will run that test and report back what I find. The good news is just moving the ISY/PLM to another circuit further away has appeared to make it stable and noise free. I have a couple Insteon switches acting weird but that is a question for another Forum or Thread! Kip
Teken Posted September 8, 2017 Posted September 8, 2017 Hello Kip, Just to clarify my request in case I was unclear. Once the system is back exactly where it was please clear the logs and then active the level 3 logs. Once open, unplug one single device from the circuit until the X-10 command stops appearing in the level 3 error log. Very eager to read and learn how many devices have to be unplugged before this issue goes away. It should be noted you may find multiple devices are contributors in this problem. Once found please add back each single device one at a time in reverse order to validate the root cause. I thank you and have a wonderful weekend! Sent from my iPhone using Tapatalk
Recommended Posts
Archived
This topic is now archived and is closed to further replies.