johnnyt

I upgraded to 3.3.4 RC1 and my IOlincs started getting changed to momentary A from latching. It started (that I noticed) with the addition of a new 2 week old IOLinc, which showed latching but behaved in a momentary fashion. It wasn't until I queried the options that momentary A showed up. I changed it to latching and all was fine after. But then one of my other older IOLinc's began behaving as though it was configured momentary ON. It had been operating in latching mode for about 2 years until now. It also showed latching until I did a query and it changed to momentary A. I changed it no problem and decided to check all my other IO Lincs and sure enough the same thing happened - showed latching, queried, showed momentary A, changed it, all seems to be fine now. A bug? A known issue? What's the risk this will happen again? Have attached the relevant section of my event viewer log output set to level 3. Lots of new xml-type stuff I've not seen in event viewer before... (ignore the variables being set along the way - they stream in from some temp sensors via an Autelis RS232-to-ISY converter but it's too hard to go through what comes out as a single line txt file in Notepad to find and delete them out) ISY-Events-Log.v3.3.4__Wed 2012.11.28 03.50.48 PM.rar

I meant what are the hardware specs? CPU, RAM, real time clock?

What's in the 99ir? Sent from my iPod touch using Tapatalk

I will also confess that part of my performance problems are because HomeSeer is subscribed to ISY and every time I make a programming change, I have to wait while ISY updates HomeSeer of what seems to be everything all over again. I hope to one day get rid of HomeSeer but I will need ISY to support a wired thermostat (even if I have to buy a new one.) I don't really want a wireless thermostat because my furnace is on a UPS and I need to be able to send it commands when the power is out. Plus I don't trust wireless for this mission critical function.

Hi Michel,When I copy a file using my high powered computer I get throughput of about 60MB/sec. A 155KB file would take a fraction of a second but that's not, in fact, my expectation. I will, however, admit that my expectation is closer to that than 3 minutes. I like - make that love - that ISY is rock solid at doing the stuff I program it to do - and doesn't need regular reboots to keep going. There's also great support for it, as well as support for other insteon/electrical issues that frankly are Smarthome/other issues. I also find its impeccable logic refreshing. Once one has figured out it's nuances, it's amazingly powerful and predictable, although it does often require writing multiple programs to do one thing, making it a bit hard to follow and dangerous to mess with a year or more later. It was only after the ELK stuff was added (3.1.x) - even though I don't use it - and that I had reached about 300 programs that I did kind of hit my annoyance threshold for the time it takes to make a quick change, and to do backups when I'm doing more than quick changes. Anyway, that's just me. Obviously if no one else is complaining, I'm just going to have to keep sucking it up. Everything comes with a trade off, doesn't it? Thanks for the effort you do put into making ISY a solid product and addressing your community's interests.

I just updated to 3.3.4 RC1 from 3.2.6 and a backup now takes 20 seconds longer (~13%) and adds about 4KB (compressed) for a throughput of about 56KB/min, or 0.94KB/sec. I don't know if it's all or mostly because of the file locking being done but would storing the data uncompressed make things notably faster? I'm not worried about disk space. I can always put the files in a compressed folder and let the core i7 in my system do the compression in milliseconds. My system backup solution also does compression. If asked to chose only one, I'd pick a fast backup over an automated one since I do backups as I'm programming, which is when waiting close to 3 minutes seems like forever.

So will the query all that runs at 3 AM and on a reboot reset a low bat? I ask because I've had them happen then disappear then a month later - maybe longer - the motion sensor stops working. The notifications were a bit premature, never happened again and I don't remember ever query them since I knew they wouldn't respond. Have kind of given up counting on them... Am hoping one day ISY will provide a last changed time stamp on devices for this and other reasons. Sent from my iPod touch using Tapatalk

Hi Michel, Thanks for the question. With a day job and 3 kids, I typically do my ISY programming in chunks of time over 3-4 days. Am currently migrating more stuff off HomeSeer (details here viewtopic.php?f=78&t=9840&p=74640#p74640) so working almost weekly in that fashion. With 484 programs, 103 variables, 135 nodes, 71 scenes, and 13 network resources, I've had many chunks of 3-4 days or more of work over the past couple of years, each time running a backup that takes over 2.5 minutes (throughput of about 62KB/sec). An automatic daily ISY backup, or an automatic backup on exit (with a way to turn it on/off?) would help if more processing speed (what I'd really like viewtopic.php?f=7&t=7768) is not an option. At 155KB per backup am not worried about wasting space on the days I'm not making changes. I might also point out that I do backups of 4 computers and 4-5 VMs on a daily basis and don't change stuff on them every day. Don't worry about a debate around incremental backups. That would only be of notable benefit if disk space was an issue, IMO. edit typo: throughput is 62KB/min (1.0333 KB/sec)

but once you get to a few hundred programs, it's painfully slow (like loading programs). I'd like to be able to schedule a nightly backup - or better yet, be able to buy a faster processor and/or gigabit network speed.

I had this problem as well as the same error when I tried to change toggle mode. The KPL in question was one I had done a "replace with", which I learned can cause problems intermittently. I ended up having to reconfigure the KPL manually from scratch. Or to be more accurate, I plugged in a spare I keep and built it up to match the problematic one (don't forget the programs) then removed the problematic one from ISY and physically swapped the h/w. Sent from my iPod touch using Tapatalk

I have a program that runs every 3 mins after it last ran but on Sunday morning it stopped running at 1:58 AM, 2 mins before DST kicked in... Sent from my iPod touch using Tapatalk

How does one send a REST command to ISY from a DOS batch file? How do I do it from a VB Script? I did browse the wiki but found nothing on how to actually make a REST call. (I did figure out that I can do it using firefox but I can't call FF from a DOS box.) Maybe I just didn't look in the right places? Any info would be appreciated.

With a scene only one insteon command is sent over the power line and all devices in that scene respond. Very clean. If you want to do it the other way, i.e. one device at a time, then you would need to add a wait between commands to give the command a chance to work otherwise you're just flooding the power line / airwaves with commands. Sent from my iPod touch using Tapatalk

I suggest you put all the devices in a scene and just set the scene fast off/on. Sent from my iPod touch using Tapatalk

I've read somewhere (not this forum) that Java7 has (and has had) some serious security issues that are not getting fixed in a timely manner. To the point where experts and organisations are recommending a downgrade to Java 6. Just google "Java 7 security downgrade"... Sent from my iPod touch using Tapatalk

Do you have a sense of the source of the wait? Is it the result of a delay between the initial motion sensing and resultant action, or due to the performance of the motion sensor, itself? My perception is that a good portion of the wait is simply due to the performance of the motion sensor. And this will remain regardless of whether one takes a scene-based approach or programmatic one. I think it's a combination of the motion sensor delay and the delay in getting the message (by the program) to the light switch. It was worse with X10 (and HomeSeer) then with Insteon and ISY. It's less (as I recall it) if I link the motion sensor to the switch directly in a scene (through ISY, of course) rather than by triggering it after I received the on conditioned ("control is switched on") but I prefer the program route because it gives me more flexibility. For example I don't set the wait time for OFF in the sensor, I set it in ISY. Also I can disable auto on and auto off by having another program that when I double click the affected switch on/off it disables the on/off program. I want the flexibility to be able to leave the light on/off, regardless of motion. Now in fairness the delay is worse where, in the case of the bathroom, motion is actually sensed by a detector attached to my DSC Alarm Panel (on a partition that doesn't trip the alarm). In that case there's the added delay of getting the DSC panel to tell DSCLink (which has to run on my 24/7 file server) to tell ISY that motion is sensed... I think my basement sensor (an Insteon motion sensor, not a DSC connected sensor) is quicker.

I have a bathroom light that is activated by a program triggered by a motion sensor and my wife always uses the switch because she can't (well, won't) wait. I confess the wait between my entering a room and the light going on was an early disappointment for me with this HA stuff in general but I'm used to it now. And my kids grew up with it. At least I didn't have to go turn the bathroom (and other) lights on for them every time before they could reach the switch. Now if I could just get my impatient wife to stop double clicking switches that cause other things to happen she didn't intend. Sent from my iPod touch using Tapatalk

Doesn't the adjust scene have the issue of wearing out the nvram, especially if one does an adjustment twice a day or every time motion is sensed? Sent from my iPod touch using Tapatalk

Well look at that. It does show up when there is more than one condition. I guess it's the first time (in two years of ISY use) that I went to add parentheses before putting in the conditions I wanted to group instead of adding them after I put in all my conditions...

The AND and OR parentheses buttons are not there on my Win 7 Java 6 update 33 machine running firmware 3.2.6 and UI 3.2.6. See attached screenshot. They do show up on my Win 7 64bit Java 6 update 35 machine (UI also 3.2.6). Have tried clearing the cache. No go.

Hi IndyMike, Yes, a mistake was made and clarified a few posts back (copied here). I did purchase the module and it does work fine. Really!? Yet when I attempted to create a test program (to provide confidence in earlier responses), it appeared to allow such a condition. I wonder if this suggest that the condition is a placebo, or that I missed something. My bad. You should listen to oberrkc. X10 devices added using the X10 module states can be used as Conditions. oberkc, do you know what is returned from a status request? Is it a regular X10 command? I lack experience with X10

turns out the answer is (from UDI): The ISY listens for X10 signals and bases the state of a device (On/Off) on those. You cannot use X10 states as conditions in a program. You can use X10 signals as program conditions without the module.

I do have two way x10 modules that will respond to status request. What I'm not clear on is whether ISY will hear the response and update the status it tracks. Do I understand that it will as long as the devices are from Smarthome and/or do not use extended codes in their response? Sent from my iPod touch using Tapatalk

Just to ask for clarification on one or two things if I may: 1. Does the X10 module include keeping track of x10 device status and being able to use it in a program condition, i.e. does this work? if status MyX10DeviceName is ON or is it truly only "cosmetic" in that it simply allows one to send/listen for x10 by name rather than by code, i.e. if X10 MyX10DeviceName is Received 2. If yes to 1, can it track responses to X10 status requests?

Some routers (like the Linksys BEFVP41) send updates regularly, like every 10 mins, even if there has been no IP address change. If you have a free DynDNS account, that's considered abusive and you'll get cut off. If your router does this or doesn't have DDNS option, you can use this software http://www.kanasolution.com/products/dy ... -download/. Another reason to use this software is that it can be configured to send an email when the IP address changes. I have it send me an email at work so I have my latest IP address there because the corporate firewall blocks dyndns web addresses. Note that you do need a computer on your LAN to be running for this to work.