Bert2013

I use the ISY REST interface to set variables about 30 times per hour. This REST call times out (after 5 sec) several times per day. I subscribe to the ISY events and monitor the 'system status' (i.e. busy/not busy). That shows me 40 times per day, the ISY is 'busy' for more than 5 sec. Of these 40 times, 4 were even 1 min long. What I see is both events are correlated. REST message timeout when the ISY is busy. I have an EISY and a POLISY and it happens on both of them. Neither of them is overloaded, I actually have very few programs. My questions: - Why is the ISY busy for so long? - Why is the ISY seemingly single-threaded? - Is there anything I can do to avoid this situation (besides setting the REST timeout to 5 min or so)? Thanks, Bert

My node server gets this warning log message. This started 3 days ago without any changes from my end. What could be the problem? 2023-09-12 18:16:44,273 Thread-33 udi_interface WARNING myqapi:_oAuthRequest: Network/server error logging into MyQ service: 403 Client Error: Forbidden for url: https://partner-identity.myq-cloud.com/connect/authorize?client_id=IOS_CGI_MYQ&code_challenge=G6nQmC3d3SAvmBmk7mBjq3IdwXWrwJ-LKLP-JNGYk5Q&code_challenge_method=S256&redirect_uri=com.myqops%3A%2F%2Fios&response_type=code&scope=MyQ_Residential+offline_access

I resolved my problem with the Portal. It turned out that my DHCP server supplied 3 DNS servers, but the first one didn't work. Normally, that doesn't matter because these other DNS servers did work. However, it seems like the ISY only tries the first DNS server. So my ISY did not resolve 'my.isy.io' and failed to connect to the Portal. I can only speculate why the DNS errors in the ISY log didn't cause problems in the past, but I guess that it reused the IP address it got a long time ago. It would be nice if the ISY behaved better from a networking point of view. As an other example, I tried to install certificates on my ISY but my ISY didn't return the root certificate. Normally, that is not a problem, but my client didn't have root certificates pre-loaded. Regards, Bert

Thanks for the replies and educating me how Portal subscriptions work. Given that new knowledge, I can't think of anything I could have done to cause the portal not to connect anymore. The Admin Console Configuration -> Portals simply says "Offline/Registered". It continues to say that even after I delete my ISY from the Portal webpage. It makes me believe that my ISY somehow cannot talk to the Portal at all. Note that the Mobilinc app still can talk to my ISY and control devices. I did punch a hole in my firewall for that (and that was what I referred to as the external URL in my first post). Note also that, via the ISY Finder, I can connect the Admin Console via http and https, via an internal URL and via and external URL. So incoming traffic works. Also, there is an exclamation mark next to "NTP Server pool.ntp.org" in the Admin Console Configuration -> System. Not sure what that means. Below is the error log starting from a reboot, I think. There are lots of "[Network-DNS][Task=22] Failed DNS 11/rc=6 my.isy.io " errors, but they have been going on for at least 3 months, much earlier than my current Portal problem. It would be interesting to know what these errors mean though. Sat 2020/05/23 09:44:11 PM System -5 Start Sat 2020/05/23 09:44:13 PM System -110022 /CONF/INSTENG.OPT Sat 2020/05/23 09:44:13 PM System -110012 /CONF/INSTENG.OPT Sat 2020/05/23 09:44:19 PM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Sat 2020/05/23 09:44:25 PM System -7123 ID 0022 :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:25 PM System -7123 ID 0023 :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:25 PM System -7123 ID 0026 :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:25 PM System -7123 ID 0027 :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:25 PM System -7123 ID 0028 :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:25 PM System -7123 ID 0029 :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:25 PM System -7123 ID 002B :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:25 PM System -7123 ID 002C :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:26 PM System -7123 ID 003D :err=0, tag='control', num=6, nest=4, o Sat 2020/05/23 09:44:32 PM System -170001 [Network] Established Sat 2020/05/23 09:44:32 PM System -60001 pool.ntp.org Sat 2020/05/23 09:44:32 PM System -140000 my.isy.io Sat 2020/05/23 09:44:32 PM System -140000 api.aerisapi.com Sat 2020/05/23 09:44:32 PM System -60001 pool.ntp.org Sat 2020/05/23 09:44:37 PM System -140000 api.aerisapi.com Sat 2020/05/23 09:44:42 PM System -140000 api.aerisapi.com Sat 2020/05/23 09:44:57 PM System -140000 my.isy.io Sat 2020/05/23 09:45:32 PM System -140000 my.isy.io Sat 2020/05/23 09:46:07 PM System -140000 my.isy.io Sat 2020/05/23 09:46:42 PM System -140000 my.isy.io Sat 2020/05/23 09:46:48 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:46:48 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:46:58 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:46:58 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:46:58 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:00 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:47:09 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:09 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:12 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:47:12 PM System -170001 UDQ:Queue Full: VAR : Task[13] HTTP_3 HTTP-Get pty=21 Sat 2020/05/23 09:47:19 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:19 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:23 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:47:30 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:30 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:33 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:47:40 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:46 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:47:50 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:50 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:47:17 PM System -170001 [Network-DNS][Task=22] Failed DNS 11/rc=6 Sat 2020/05/23 09:47:17 PM System -140000 my.isy.io Sat 2020/05/23 09:47:52 PM System -170001 [Network-DNS][Task=22] Failed DNS 12/rc=6 Sat 2020/05/23 09:47:52 PM System -140000 my.isy.io Sat 2020/05/23 09:48:00 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:00 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:03 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:48:11 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:11 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:14 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:48:21 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:31 PM System -170001 UDQ:Queue Full: VAR : Task[13] HTTP_3 HTTP-Get pty=21 Sat 2020/05/23 09:48:31 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:31 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:32 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:48:42 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:48:42 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:42 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:46 PM System -170001 UDQ:Queue Full: VAR : Task[13] HTTP_3 HTTP-Get pty=21 Sat 2020/05/23 09:48:53 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:48:27 PM System -170001 [Network-DNS][Task=22] Failed DNS 13/rc=6 Sat 2020/05/23 09:48:27 PM System -140000 my.isy.io Sat 2020/05/23 09:49:02 PM System -170001 [Network-DNS][Task=22] Failed DNS 14/rc=6 Sat 2020/05/23 09:49:02 PM System -140000 my.isy.io Sat 2020/05/23 09:49:03 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:03 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:03 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:49:13 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:16 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:49:25 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:25 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:25 PM System -170001 UDQ:Queue Full: VAR : Task[13] HTTP_3 HTTP-Get pty=21 Sat 2020/05/23 09:49:33 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:49:35 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:35 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:45 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:49:45 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:46 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:47 PM System -170001 UDQ:Queue Full: VAR : Task[13] HTTP_3 HTTP-Get pty=21 Sat 2020/05/23 09:49:56 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:50:03 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:50:06 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:49:37 PM System -170001 [Network-DNS][Task=22] Failed DNS 15/rc=6 Sat 2020/05/23 09:49:37 PM System -140000 my.isy.io Sat 2020/05/23 09:50:12 PM System -170001 [Network-DNS][Task=22] Failed DNS 16/rc=6 Sat 2020/05/23 09:50:12 PM System -140000 my.isy.io Sat 2020/05/23 09:50:16 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:50:16 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:50:16 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:50:26 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:50:33 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:50:37 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:50:37 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:50:43 PM System -170001 UDQ:Queue Full: MP : Task[8] SOCKZW SOCK-PROC pty=25 Sat 2020/05/23 09:50:47 PM System -170001 UDQ: Queue(s) Full, message ignored Sat 2020/05/23 09:50:47 PM System -170001 [Network-DNS][Task=22] Failed DNS 17/rc=6 Sat 2020/05/23 09:50:47 PM System -140000 my.isy.io Sat 2020/05/23 09:51:05 PM System -170001 [Network-DNS][Task=29] Failed DNS 18/rc=6 Sat 2020/05/23 09:51:05 PM System -60001 pool.ntp.org Sat 2020/05/23 09:51:35 PM System -170001 [Network-DNS][Task=30] Failed DNS 19/rc=6 Sat 2020/05/23 09:51:35 PM System -50010 mail.universal-devices.com Sat 2020/05/23 09:51:35 PM System -170001 [Network-DNS][Task=29] Failed DNS 20/rc=6 Sat 2020/05/23 09:51:35 PM System -60001 pool.ntp.org Sat 2020/05/23 09:51:40 PM System -170001 [Network-DNS][Task=22] Failed DNS 21/rc=6 Sat 2020/05/23 09:51:40 PM System -140000 my.isy.io Sat 2020/05/23 09:51:40 PM System -170001 [Network-DNS][Task=30] Failed DNS 22/rc=6 Sat 2020/05/23 09:51:40 PM System -50010 mail.universal-devices.com Sat 2020/05/23 09:51:40 PM System -170001 [Network-DNS][Task=29] Failed DNS 23/rc=6 Sat 2020/05/23 09:51:40 PM System -60001 pool.ntp.org Sat 2020/05/23 09:51:45 PM System -170001 [Network-DNS][Task=29] Failed DNS 24/rc=6 Sat 2020/05/23 09:51:45 PM System -60001 pool.ntp.org Sat 2020/05/23 09:51:45 PM System -60006 Stopping retries/next cycle Sat 2020/05/23 09:52:00 PM System -170001 [Network-DNS][Task=22] Failed DNS 25/rc=6 Sat 2020/05/23 09:52:00 PM System -140000 my.isy.io Sat 2020/05/23 09:52:35 PM System -170001 [Network-DNS][Task=22] Failed DNS 26/rc=6 Sat 2020/05/23 09:52:35 PM System -140000 my.isy.io Sat 2020/05/23 09:52:51 PM System -170001 [UDSockets] RSub:21 error:6 Sat 2020/05/23 09:52:56 PM System -170001 [UDSockets] RSub:21 error:6 Sat 2020/05/23 09:53:01 PM System -170001 [UDSockets] RSub:21 error:6 Sat 2020/05/23 09:53:06 PM System -5012 28 Sat 2020/05/23 09:53:10 PM System -170001 [Network-DNS][Task=22] Failed DNS 27/rc=6 Sat 2020/05/23 09:53:10 PM System -140000 my.isy.io

Hi, I changed the external url from my ISY; I switched domain names. Now The Portal says "Offline since ...", The Admin console says "Offline/Registered". Alexa says "plug in the power...". I don't see any way to specify or change the URL. I tried to delete and re-add my ISY in the portal but the only thing it wants is my MAC address. Help! Bert

Teken, About my experience with all-lights-on events. It comes in burst for me. In the worst case, 2 per day. In bad weeks, 3 per week. What I feel is that , if all the Insteon devices are programmed clean (i.e. no errors, no differences between the device link table and the ISY view of the links) all-lights-on does not happen very often. That is the reason I wish there was an implemented SOAP (or REST) message to 'restore device'; it would allow me to restore devices blindly every night. Or even better, a way to check if the device's link table is corrupted. Of course, the root cause of why the link table of my devices get clobbered would be nice to know... I have replaced my PLM at least 2 times, and after replacement, things work a lot better. Of course, that might be because the device link tables are all re-created... My system recovers automatically from an all-lights-on event. I get important input from the GEM data which I make the GEM send to my app-server. My app-server interprets the amps of a few chosen channels, it basically looks for high-amp usage which might indicate an all-lights-on event. My app-server then checks the ISY if it thinks the lights on that GEM channel are on. If the ISY thinks the lights are on, it is not an all-lights-on event and it is ignored. If the ISY thinks the lights are not on, then it is an all-lights-on event and my app-server instruct the ISY to turn lights on and then off (via running a program via REST). Thanks for pointing me to the UDI wiki again. I'm evaluating what parts are relevant to me. I already have deployed almost 10 FilterLinc and a few Access Points. One thing I encounter regularly is an ERR which seems to clear (the ISY clears it) after 10-20 seconds. I already replaced the on/off switch once with no change in behavior... I see these things more clearly now that I use the SOAP event trace of events from the ISY... Recently, my (wireless) RemoteLinc 2 keypad failed. I cannot "restore device" it anymore. I'm guessing that it probably was degrading for a while and might cause havoc on the power line... Lastly, I don't know much about "smart hop", "send cleanup messages". I also don't know about "With respect to (newer) Insteon hardware they offer confirmation of signal sent and received. It also offer the ability to know if there was an error while other features are turning on / off RF & Power Line signaling.". Can you point to something to read about it? Thank you for always being ready to answer questions and help people out. Bert

Teken, I guess you mean that I could program any controller to control any receiver and watch the white or red blinking LEDs as to what the result was... One thing that the Diagnostic Keypad does in addition is report on "corrupt messages" due to "collisions/noise". It does that by beeping in "report" mode. Unfortunately, I cannot conclude if these "corrupt messages" are normal due to motion sensor collisions, or if it is really a corrupt message or really noise potentially causing havoc. That is where my question about beeps came from. In my particular case, I have a lot of havoc going on: - I encounter regular all-lights-on events. Luckily, I automatically recover from it by combining info from my GreenEye Energy Monitor and the ISY. - the link table of devices is getting corrupted on a regular basis. I found that out when things misbehave, or when I comnpare the device link table with the ISY's link table. So I have to use the ISY to "restore the device". I would like to automatically "restore devices" but, from what I found out so far, the RestoreDecive SOAP command is not implemented in the ISY (I'm using Peter Shipley's python code for that). - my IOLinc turns on or off unexpectedly at least once a day. (It is controlling the opening and closing of a catfeeder... so cats go hungry and skunks get fat). Luckily, I have a program that checks the state of the IOLinc throughout the day and corrects it if needed. Because of the above, I have no time for fun new stuff and instead worry about how to find the (probably several) bugs in my system. I have done the usual stuff: - put FilterLinc on a log to devices - disabled my PowerLine Phase coupler (I know that Teken doesn't like these couplers...) - disabled my whole-house surge protector - replaced suspected bad switches (they were not bad...) - go around and test with an old X10 appliance link to see if my ISY's plm signals can control the appliance link properly. - I try to interpret the ISY event log, but it is hard to conclude much from that because there is not enough information in it. When an error is encountered, it just says ERR without the reason... Thanks, Bert

Hi, I have an "Insteon Diagnostic Keypad 2993-xx2". I would like to add this device to the ISY so I can program the Diagnostic Keypad to control certain lights and then walk around with the Diagnostic Keypad and troubleshoot. Unfortunately, the ISY does not want to link the Diagnostic Keypad. Errors are: "Cannot determine Insteon Device type". Is the only way to push these set buttons in the right order? Very painful... Also, my Diagnostic Keypad in "Traffic" mode beeps a lot. The documentation says that beeping means "corrupt message" due to "collisions/noise". I do have many dual-band devices and a number of motion sensors, so I conclude that "collisions" are possible, and even likely. That makes this "traffic" mode not very useful... What has been your experience? Thanks, Bert

I own an EXFLORA and I have bought the Irrigtion module. But I have a hard time figuring out how to use these two together. In this topic, I see bipto's programs that use "Module 'Climate' Irrigation Requirement >= 0.18 inches" but bipto also irrigates all the zones. (Just using Bipto and an example) My lawn needs more frequent water than my fruit trees. The "irrigation requirement" is different for the different zoes. The "crop coefficient/plant type" is differrent in the different zones, but the irrigation module only has one "crop coefficient/plant type". I understand that I can adjust the amount of water for each zone, but that is a hack. My fruit trees don't need nor do they want water every 2 days but my lawn does. Moreover, after irrigation, I'm suppose to "reset" the "irrigation required" via "cycle complete". This further enforces that all zones have to be treated the same. Am I missing he magic of the "irrigation module"? Thanks, Bert

I did buy an EZIO8SA after all and it is working great. I use it to control and monitor my "water system": well pump, pressure pump, pressure sensors, float switches... So it is pretty "mission critical" and a lot of damage can be done when it misbehaves. But I have enough redundancy built in so that it has not burned up my pumps... I like that it is "self contained", it does not need Insteon communication nor a working ISY to do its job. This is also a reason why the suggested "Din Relays" would not work well for my application. I use the ISY to monitor and to identify potential issues (such as "the pump is running too long", or "the pump has not run for a long time"). The ISY cannot be used to program the EZIO8SA, so I needed a PLM connected to my computer to run the SmartHome Utility software to do that. This is where I had the most problems, but mostly because my Insteon connection to the EZIO8SA was bad and the first PLM I used was giving a "weak" Insteon signal. So overall, I'm happy with the product. I actually don't know of any similar products that have so many input and outputs (In my application I used all the relays and 4 of the 7 inputs). Bert

Thanks Teken, I placed my order

Teken, I'm getting closer to invest (buy a new toy) into a Brultech energy monitor. Unfortunately, Brultech doesn't allow me to register for their forum without a "valid" name of an energy monitor. Thus I'm asking it here: Is it advisable to put a CT on the incoming power lines? Mine are big aluminum wires that require a big expensive CT. After all, I will have CTs on all breaker wires... I plan on getting a GreenEye monitor and a dashbox. I have not decided yet on Zigbee and I also don't know how easy it is to upgrade my existing ISY994i with ZigBee. After seeing the pictures of your setup, I'm jealous since my breaker box is build in a shear wall with taped sheetrock. I have a box next to my breaker box, but it is a metal box Thanks, Bert

Thanks Teken, In the mean time, I found and read your posts on the Brultech forum. Thanks for all the details. You wrote: "I have with the tremendous help of Brultech come up with a method which allows you to use the DB to send State Variables for all channels: Energy, Temperature, Pulse, Voltage, NET metering, etc to the ISY." Do you see this as a good alternative to ZigBee between the ISY and the GEM? If so, I'm interested! Since you have such an extensive setup and experience, let me ask you an unrelated question... I have a good generator (Honda ES6500) but when the phases are unevenly loaded, the heavily loaded phase voltage drops. This is what the regulator correctly does to avoid over voltage on the lightly loaded phase. What I wish I could do is to let the ISY control the load when I switch to the generator after a power failure; e.g. turn off the laster printers, furnaces, refrigerators, pumps because they will all draw power at the same time when I switch to the generator. Of course, I cannot do that because I have no power; while I have my electronics and the network on UPSs, my Insteon switched and outlets are not (of course). What would solve this is a device that turns off after loosing power and stays off after the power comes back. Any advice? Besides buying a much bigger (Generac ) generator? Thanks Bert

Thanks Teken for his detailed information about energy monitoring. Some questions: A technical question. You mentioned that your setup can show you voltage (and I have seen your other voltage fluctuation charts elsewhere). How can the device deduce voltage from a CT sensor? CT sensors measure flux from the AC current through the wire... Do you have something additional? A second technical question: Your voltage fluctuation charts imply that the voltage is sampled pretty high (did I read 10kHz or so?). That is a lot of data... And you send all that to GEM? Even the dashbox, which doesn't have a rotating disk, must fill up fairly quickly. A Zigbee question... From what I gather, your GEM communicates via zigbee to your dashbox and your dashbox communicates to SEG (via TCP/IP). Does your GEM also communicate the same data to your ISY via zigbee? Since I'm new to zigbee, how far does the zigbee signal travel? Would I be stuck creating a zigbee mesh of at least a couple zigbee devices? Also, the GEM has "options" for ethernet and Xbee (assume the latter is zigbee). I assume you have both options on your GEM? Thanks Bert

Since we can't measure the signal strength of the Insteon messages because there is no tool for it, and since our houses are filled with appliances, UPSs, power adapters, power strips, surge suppressors, would it make sense to put anything that might produce noise or cause problems on a Insteon FilterLinc? One RF reliability question. Does the RF signal and the PL signals get initiated/travel in parallel? E.g. I have many dual band devices in my house and if my controller and responder both are dual band devices, wouldn't the Insteon signal be able to travel solely on RF? I understand that RF can be interfered with also, but from all the descriptions, I tend to conclude that the powerline is much dirtier than RF. Thanks Bert