johnnyt

I'm interested in this as well to activate a heated mat and roof cable, Ideally it would report a "it's snowing now" state, which admittedly is probably too much to ask for. I was thinking I might need a personal weather station with a rain gauge and heater to melt snow but can that info get back to ISY? How quickly?

I ended up visiting my in-laws in Florida for March break so had the devices shipped there (bought the webswitch in 2013 and the din relay this year). Have not had to deal with company for warranty issues so can't confirm or deny any problems on that front but fwiw I did ask a question once and got the answer in good time. Maybe they only answer the easy 'no skin off their back' questions, which is a bit disappointing to learn. Sent from my iPad using Tapatalk

I have the iOS app and it controls both my webswitch and DIN relay fine. They are great, rock solid devices. App is quite rudimentary. I use it to override some hvac dampers that ISY controls. Avoids having to do all kinds of ISY programming to allow for the overriding. Sent from my iPad using Tapatalk

I had an a-bus amp/volume control in a regular switch outlet until I pulled in out just this weekend in favour of a sonos amp. Check out http://www.hometoys.com/emagazine/2013/ ... trong/2101. It was okay but I much prefer my sonos setup. For one thing I couldn't control my abus from anything other than the physical volume control. Sent from my iPad using Tapatalk

I have a sonos amp running a boston acoustics "rock" stereo speaker. Someday soon I'll re-read the sonos thread on sending commands to sonos from ISY. Sent from my iPad using Tapatalk

huh? My close to 2 yr old PLMs are v.9B. I keep one as a backup and I've swapped them twice since getting them to spread the load around and (last time) to check that the PLM wasn't causing a problem I was having. Should I be doing something to them? I did have an all on occurrence twice (in ~4 yrs) but both times I had pressed a button (fast on in one case) Sent from my iPad using Tapatalk

I import my iTunes playlists into my sonos system. If you search this forum for sonos you can find posts on making calls to sonos from ISY. Sent from my iPad using Tapatalk

Am new to the climate module and running firmware 4.2.3, which is pointing to the new HamWeather service. I'd like to store some climate data in a variable so I can track changes/max/min and send some of the data by email. I don't see an action that allows me to choose it. I also looked in the "variable" action but didn't see anything there. My search of the wiki didn't provide the answer. I know the data is available through a REST call but don't think I can have ISY make that call to itself and store it in a variable, can I? Is there a way to do this using ISY (without another computer)?

I don't have eventghost but FWIW my homeseer plugin timeouts every now and again; and almost always when I'm making heavy use of the admin console. Fortunately it has a watchdog timer that most of the time fixes the problem but sometimes the watchdog timer is running every 30 mins or so long after I'm done fiddling with the admin console. I have to stop and start the plugin or homeseer to fix when it gets into that loop. I'm hoping to be able to get rid of HS soon. I think it's too demanding for the ISY processing power. DSCLink also sometimes can't update a variable. Sent from my iPad using Tapatalk

I just checked and the online "brochure" says lamplincs still have local sense functionality. http://www.smarthome.com/2457D2/LampLin ... Pin/p.aspx I hope so and might get one in case they stop supporting it because I need (...well, my wife needs, therefore I need) to be able to turn the light on manually. Sent from my iPad using Tapatalk

For only an handful of relays an IOLinc works pretty well except for: 1) the weaknesses of insteon (YMMV) and 2) this issue for me viewtopic.php?f=25&t=10356 that I haven't seen anyone else report that happened again as recently as a few months ago and has not been resolved. I had many issues when using 11 IOLincs for a bunch of HVAC things (here was my now outdated setup viewtopic.php?f=48&t=10174) but I think it's because I needed to query them regularly (due to issue #1) to ensure reliability. An IOLinc query returns two answers: one for the relay and one for the sensor. My network and ISY would get overwhelmed and countless issues arose, including, I believe, this completely unrelated and otherwise unresolved one viewtopic.php?f=27&t=11873 that has not re-occurred since I reduced my IO Lincs to 4. Here's a list of other relevant posts: viewtopic.php?f=27&t=5116 viewtopic.php?f=7&t=7768 (that turned out to be partly - but not entirely, IMO, problems related to querying my IOLincs) viewtopic.php?f=27&t=10499 (this one was fixed if you have a 994i, i.e in 4.x) viewtopic.php?f=27&t=11907 At first I tried an EZIO8SA to reduce the IOLincs down to 4 but I do not recommend it. It is poorly documented for a product that's been around so long and has a number of significant bugs that should at least be documented given that Smartenit is not planning to fix them. They include this one viewtopic.php?f=27&t=13528&start=30#p109383 that took me countless hours over 2 months before I learned what the problem was. Read the whole post if you want to know what can happen. There are a number of other qwerks. I plan to update the post soon based on whether or not I get my money back from Smartenit, as they promised I would but haven't done yet about a month after I returned it. My suggestion is to consider this http://digital-loggers.com/din.html (thanks to Xathros for suggesting it to me). It's been rock solid (like the http://digital-loggers.com/lpc.html, which I also own). It does, however, need the network module and you can't query it - at least not yet; I've heard a two way network module is in the works but not sure if/how it would work with this. I keep track of relay status (for program triggers) using variables or X10 devices (I have the X10 module too) to track states.

I think you meant to say : It was me that spent two months and countless hours trying to make the EZIO8SA work only to find out scenes don't work and had been the reason for all the grief I was getting. The thread I posted earlier has all the gory details of what can happen if anyone is interested. FWIW, I ended up shipping the EZIO8SA back and am using this http://digital-loggers.com/din.html (thanks to Xathros for the suggestion). I'm planning to update the other thread with more info once I get my refund from Smartenit (the check's in the mail, apparently - a delay, I'm told, because I was past the 15 day return period. Am waiting to see if they're going to make good on their commitment before posting about my experience)

Sorry, it looks like my attempt to point to the one post I wanted to (from Tapatalk) didn't work. Try this. viewtopic.php?f=27&t=13528&start=30#p109383 it's a post from Michel saying putting multiple ezio relays in a scene doesn't work. I mean you can do it (add them to the scene), but it won't do what you expect the scene to do.

viewtopic.php?t=13528#p109383 Sent from my iPad using Tapatalk

You can't put more than one relay per scene. An undocumented feature I learned the hard way. Sent from my iPad using Tapatalk

I'm going to add my voice to a h/w platform that offers better performance. I need something that can handle peak demands, not average or low demands. In my experience, once you hit more than about 300-400 programs and you have more than a few external systems subscribed to ISY, stuff starts to happen that is, IMO, performance related. While you could argue better programming on the part of the user might solve some of the problems, more power would solve most of them more cheaply in most cases. ( from having worked 20 years in IT) Sent from my iPad using Tapatalk

Thanks for your insights, ELA and IndyMike, I may spend a little time focusing on potential signal suckers I've overlooked. I already have about a dozen filters on various loads, including computers, UPS'es, amplifiers (sonos, powered sub, AV equipment), motors (fridge, HRV freezer, dehumidifier, microwave oven) but I've left a few wall warts alone (2 cordless phone charging cradles and an ipad charger come to mind right now). As I don't have any spare filters handy, what existing filters might be worth sacrificing to isolate the phone/ipad chargers? I know I'm stealing from Peter to pay Paul but is there a chance I don't really need filters on one or more of my fridge, freezer, HRV, microwave, and dehumidifier? I think I was doing it to filter out noise more than signal sucking, particularly since they are on their own circuits (except for dehumidifer). I don't have a way to test for noise so was only guessing they might be a source of problems in the first place. I also recently heard that induction motors, often used in fridges and HVAC equipment (like HRV?), are not a major source of noise... ELA, I can't find the great post you had on signal suckers. (Of course, you've had a few great posts on comms issues but I'm thinking of the one where you provided a list of signal suckers and their relative signal sucking ability.) Would you be able to point me to it? Finally, it's my understanding filters are signal suckers too and, therefore should only be used on something that is a known (worse) signal sucker or noise maker. Is that valid?

Thanks, LeeG. I may just use i2 when I need to read/restore devices that support it. Earlier today I removed all but 2 Access Points and there are still duplicate messages. In fact I noticed what looks like two duplicates in one case. See attached screenshot. I may try to unplug or pull the air gap out of all my dual band devices and pull out all a phase coupling AP to see if it goes away then add in one DB device at a time...

One downside of using the "Device Reported" setting for i2 support and the fact that it can't be set at the device level is that it doesn't work with my Icon devices when reading device links table. ISY ends up using i2 and sending extended messages, which doesn't work. I guess it's not a big deal to change it back and forth when I'm reading device links table given it's not something I do often. However is it safe to say this inability to truly know the i2 compatibility of the device affects things when setting/changing scenes with devices that ISY interprets as i2 compatible even though they're not? Also, can someone clarify whether the i1/i2 setting impacts - positively or negatively - the day-to-day use of my devices, i.e. just turning them on/off and executing scenes. I will say things certainly do work much better with i2 for devices that support it when it comes to reading device links table. Turns a 20+ minute process for my KPLs that sometimes has to be restarted into a 5 min affair.

what's the downside or risk of using i2? why is it not recommended? is there any chance of device corruption that can't be fixed with a return to i1 and a restore?

Thanks, LeeG. The problem is not limited to the Icon Relay. I've attached event viewer logs for device link query of a v41 i2CS KPL and a v.36 KPL. While not on the same circuit both occasionally suffer from not doing what they're told although less often. The v.36 KPL seems to struggle just as much as the Icon Relay here while the v41 KPL doesn't seem to struggle as much with hops left but there are a number of unexpected responses. Things certainly finish faster with the i2CS device. It's quite painful waiting for a 70-80 link KPL to get through it's table - and with the problems I'm having it usually needs more than one attempt in order to get through it. To compare, I also queried the device links table of an v36 IOLinc that is about 30 feet away from the PLM on the same phase and not in what I consider a problematic area of the house. A few hops left=0 are seen but they appear to be related to the echo / duplicate commands that occur. Another thing I noticed as I check device links tables is that most I've checked so far end up with record mismatches when compared to the ISY links tables. I went through a round of device updates about a year ago after finding mismatches in a number of devices that I never got to the bottom of and just let go. I might revive that thread with some up to date info (viewtopic.php?f=27&t=10577). I'm wondering, though, if it wasn't/isn't related to this issue and perhaps if I can fix this the other problem won't happen. The reference to metal junction boxes was just to say that any hard wired dual band devices I have, such as the v41KPL I queried for this, do not add (or benefit) notably, if at all, to the RF portion of my insteon network. Not saying it adds anything; just putting it out there as I know this scenario is not common in the US. ISY-Events-Log.v4.1.2__IOLincv36.ClosetoPLM.txt ISY-Events-Log.v4.1.2__KPLv4.1DeviceLinksQuery.txt ISY-Events-Log.v4.1.2__KPLv36DeviceLinksQuery-partial.txt

I'm trying to understand event viewer entries a little better in the hope it will help me understand comm problems and potential fixes better. The trace below is an excerpt from the attached file that was created by doing a Show Device Links Table for an Icon Relay (the value brand version of the ApplianceLinc that's no longer being sold) with address 16.AB.AF. It is in a place where it doesn't always do what it's told. I can see that there are comms issues with Max Hops=3, Hops Left=0 and these happen even when I put an access point on the same circuit. Q1: Shouldn't an access point fix that? Q2: Why would the commands alternate so consistently between hops left=2 and hops left=0, i.e. perfect one time and terrible the next? Wouldn't things be more clearly one way (hops left=2) or the other (hops left=0)? why no hops left=1 sometimes? Q3: It also looks to me like a number of commands are duplicates or an echo of a previous command - is that right? If so, are they from the RF insteon signal, which I think I read somewhere are a half second (or is it half a Hz) after the powerline signal? Q4: Generally speaking, can/should I just add more Access Points or can/will they make things worse sometimes? Should I stick to the minimum needed, i.e. one per phase and only where needed for RF only devices. Currently I have 5 access points installed, 2 on one phase and 3 on the other. I sometimes use a spare PLM I keep as a backup as an access point for testing (I assume it works fine for that purpose, is that right?). I have very few dual band devices and metal junctions boxes that render all but the wall wart variety (Lamplinc and IOLinc) useless. Any info would be appreciated. Tue 04/15/2014 06:43:14 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 28 0F Tue 04/15/2014 06:43:14 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 28 0F 06 SET-MSB(0F) Tue 04/15/2014 06:43:14 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:14 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:14 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 2B F8 Tue 04/15/2014 06:43:15 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 2B F8 06 PEEK (F8) Tue 04/15/2014 06:43:15 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:15 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:15 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 2B A2 PEEK (A2) Tue 04/15/2014 06:43:15 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:15 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 28 0F Tue 04/15/2014 06:43:15 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 28 0F 06 SET-MSB(0F) Tue 04/15/2014 06:43:15 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 2B A2 PEEK (A2) Tue 04/15/2014 06:43:15 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:15 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 2B A2 PEEK (A2) Tue 04/15/2014 06:43:15 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:15 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:15 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:15 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 2B F9 Tue 04/15/2014 06:43:15 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 2B F9 06 PEEK (F9) Tue 04/15/2014 06:43:15 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:15 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:16 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 2B 00 PEEK (00) Tue 04/15/2014 06:43:16 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:16 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 28 0F Tue 04/15/2014 06:43:16 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 28 0F 06 SET-MSB(0F) Tue 04/15/2014 06:43:16 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:16 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:16 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 2B FA Tue 04/15/2014 06:43:16 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:16 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:16 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:16 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:16 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 2B FA 06 PEEK (FA) Tue 04/15/2014 06:43:17 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 2B 1E PEEK (1E) Tue 04/15/2014 06:43:17 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:17 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 28 0F Tue 04/15/2014 06:43:17 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 2B 1E PEEK (1E) Tue 04/15/2014 06:43:17 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:17 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 28 0F 06 SET-MSB(0F) Tue 04/15/2014 06:43:17 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:17 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:17 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 2B FB Tue 04/15/2014 06:43:17 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 2B FB 06 PEEK (FB) Tue 04/15/2014 06:43:18 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 2B 48 PEEK (48) Tue 04/15/2014 06:43:18 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:18 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 28 0F Tue 04/15/2014 06:43:18 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 2B 48 PEEK (48) Tue 04/15/2014 06:43:18 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:18 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 2B 48 PEEK (48) Tue 04/15/2014 06:43:18 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:18 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 28 0F 06 SET-MSB(0F) Tue 04/15/2014 06:43:18 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:18 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:18 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 2B FC Tue 04/15/2014 06:43:18 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 2B FC 06 PEEK (FC) Tue 04/15/2014 06:43:19 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 2B AD PEEK (AD) Tue 04/15/2014 06:43:19 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:19 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 28 0F Tue 04/15/2014 06:43:19 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 28 0F 06 SET-MSB(0F) Tue 04/15/2014 06:43:19 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:19 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:19 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 2B FD Tue 04/15/2014 06:43:19 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:19 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:19 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 2B FD 06 PEEK (FD) Tue 04/15/2014 06:43:20 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 2B FF PEEK (FF) Tue 04/15/2014 06:43:20 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:20 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 28 0F Tue 04/15/2014 06:43:20 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 2B FF PEEK (FF) Tue 04/15/2014 06:43:20 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:20 PM : [iNST-ACK ] 02 62 16.AB.AF 0F 28 0F 06 SET-MSB(0F) Tue 04/15/2014 06:43:20 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 2B 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:20 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 04/15/2014 06:43:20 PM : [iNST-TX-I1 ] 02 62 16 AB AF 0F 2B FE Tue 04/15/2014 06:43:20 PM : [ Time] 18:43:22 1(0) Tue 04/15/2014 06:43:20 PM : [iNST-SRX ] 02 50 16.AB.AF 1E.48.AD 23 28 0F SET-MSB(0F) Tue 04/15/2014 06:43:20 PM : [std-Direct Ack] 16.AB.AF-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 04/15/2014 06:43:20 PM : [uNKNOWN ] 02 AF ISY-Events-Log.v4.1.2__Tue 2014.04.15 06.44.18 PM.txt

Oh yeah, thanks for mentioning that, Jim, I hadn't thought of it. I went ahead and created programs that report true if variable-to-monitor = 1, false otherwise and made them favorites. Unless I'm missing something, though, I have to have 2 programs/favorites per device, one to see the status and one to change it, which starts to make things a little crowded on my favorites screen. For now, I'm mostly interested in being able to see the state at a glance so I'll use it just for that. If I end up really wanting the full functionality before virtual devices are implemented, maybe I'll just go ahead and use X10 devices and hope the extra traffic doesn't interfere with real commands. Thanks again for posting.

Is there a way to create a status only (virtual) device that shows up in My Lighting? For example, in HomeSeer, which I now only use for its access to forecast data, I have a bunch of virtual X10 devices using house code "z" (and others above "P"). I tried doing this with ISY (I have the X10 module) but it doesn't work. The first time I tried (using "z1") I got an error message and the next two times (using "X1") nothing happened - no message and no device created. Yes, I know I could create a device with a valid X10 address but I'd rather not add unneeded "noise" to my power line if I can avoid it. Ultimately, I'm looking to set a device linked to a variable (0 or 1) such that Mobilinc shows it in it's device "tab" because it currently doesn't present variables very effectively, IMO. For example, I can't set a variable to be a "favorite", and I would very much like to be able to more easily set a variable (to 0/1) when in Mobilinc, i.e. like using a switch. I realize I may need to ask Mobilinc to make a change but I thought the easier route to get to what I wanted was being able to use some sort of virtual device in ISY that doesn't end up involving the PLM and adding unnecessary traffic to my insteon network. (I assume collision avoidance doesn't exist for X10 in the ISY PLM but is that true? - maybe I don't need to worry about it...) Any info or suggestions would be appreciated.

Yes, I realize that (thanks to you and your post early in the thread). I guess I was wondering two things. 1. Why doesn't the event viewer show something like this when queried? Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 1] ST 0 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 2] ST 0 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 3] ST 0 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 4] ST 0 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 5] ST 0 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 6] ST 0 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 7] ST 0 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 8] ST 0 2. Does a program with one of the relays 2-8 evaluate when node 1 is queried The first one certainly would have helped my troubleshooting and would have avoided some questions and logical conclusions I drew. For number 2, I just created a test program with only status of relay 2 as the trigger and it works fine. I guess I knew this since when things worked well (i.e. no problems caused by multi-device scenes being called) programs with relays 2-7 did work fine. So I take the 2nd question in my last post back...