simonw

Migration from 99 to 994 completed very smoothly. Thanks to all for their encouragement. Simon

Greetings My attempt to migrate from 99i to 994i hasn't gone entirely smoothly and I wondered if the strange things I've seen are normal or not. I'd like to know how the migration should be done. Apologies if I missed a thread on this topic. I bought a 994i/PRO in preparation for using the secure connection to my Elk. I am looking to cut over from my 99i/PRO with as little downtime as possible. My 99i and 994i are now both at firmware 3.3.10. The 99i is connected to the PLM and active. The 994i is on my local network but not connected to a PLM. Onto the 994i I restored a fresh backup from the 99i which mostly looked OK in that my programs and variables were all there. No configuration tabs for my various modules (Elk, Climate, Network) but I figured this is normal since I have not yet contacted UD to transfer the modules from the 99i to the 994i. What next? How far can I get with setting up the 994 while the modules aren't copied over? Does the 99i die once the 994i modules go live or is there a transition grace period? What about the PLM? Will it just unplug from the 99i and plug into the 994i? Lastly, a problem with variables not being restored from the backup: Maybe this is to be expected, but although my integer variables reloaded from the backup the state variables did not, at least the init values. Typing them all in would be a pain. Is this inevitable? Or am I missing a trick or seeing a backup bug? Thanks in advance for any pointers or tips, Simon

For the record, I want to conclude this thread by saying that a very helpful tech support session with Michel revealed that the problem is something to do with the SMTP mail server. The problem goes away by using gmail. Simon

Michel, By the way, my scheduled heartbeat emails sent with unspecified default content arrive daily with multiple lines of text, so I'm sure there is no email reader client problem. My only problem is with the entries in the customization tab. Simon

Hi Michel, Thanks for your input. I was afraid you were going to say that! I'm sorry to say it still looks like a real problem here, even using and despite switching from my usual service to the default ISY SMTP server. A message customization that looks like this: Hello World ! comes through in the delivered email via the default SMTP server looking like Hello World! All on one line. If it's not a reproducible bug then it still seems to be something biting me, some corrupted component? What to try? Re-install the firmware? Cheers, Simon

Greetings, I have made a bunch of "meter" programs as described by Rod last year, and want to email the results periodically in a custom email. Everything works great if I have a one-line body, I can email something like "floodlight runtime ${var.1.36}" and all is well. Problem comes when I try to make multi-line emails consisting of multiple such statements - I can't seem to get a line break to appear in the emails even though it looks find in the customization editor. Everything piles up into one unbroken text line. I'm on a Mac, does that matter? I've tried , all the opt/alt/ctrl/cmd/shift flavors of , but no luck. I can't see a special character menu to pick from ... what am I doing wrong? Thank you for your help in advance! Shout-outs to LeeG and apostolakisl for a couple of good tips earlier today. Cheers, Simon

Perfect - thank you, Lee. This also explains why I have had puzzling results debugging program chains using "disable" ... Have a great day, Simon

Greetings I am spinning a web with dozens of programs acting as occupancy sensors and countdown timers and running time meters, and so far so good, this is great and I appreciate the valuable ideas and tips here on the forum. Sometimes I want program A (something that determines occupancy, say) to call an If statement in program B (like turn lights on of they're not already on and it's dark outside), - but - I don't want program B If evaluated unless I call it from another program. In practice it seems like Program B just does its sweet thing and so my approach is useless. Could Folder Conditions be made to help somehow?? I welcome suggestions about the right "ISY way" to go about this sort of task. Thanks in advance, Simon

Thanks for clarifying that!

Hello, I'm using the Elk module to turn on Elk outputs with an off timer, typically 1800s (minutes or hours would nice!). Can anybody please explain how I duplicate the Elk rule feature "restart timer when running", which I find very useful. Thanks! Simon

For the record, all is working fine now, the menus have a long list of the % levels etc. Must have been a strange glitch in the java app on the Mac or whatever. Thanks.

Thanks, Lee. Yes, for dimmers, of course. I just don't get the % levels showing up, I'll try interacting with the drop-down and see if they appear. Relieved to hear that they at least are supported! Simon

Greetings, I'm migrating many Elk rules including lighting programs to the ISY-99. Firmware and GUI 3.1.17 official release. I feel like I must be missing a simple trick, but I can't see how to directly program the ISY to turn a light on at, say, 20% brightness. I know I could make and use Scenes, but I have wrestled with scenes too often to find them attractive alternatives to simple commands for single lights. I see Action/Insteon/Set whateverlight "On", "FastOn" etc., even "Bright" (what does that do in a program? sounds close to what I want), but I can't seem to get a menu or dialog box where I can enter the desired light level (power level, dim setting or whatever you want to call it). This is easy on the Elk, and since that just sends commands to the ISY I feel sure there must be an easy way to make the ISY do it directly. Can somebody tell me what I'm doing wrong, or confirm it can't be done? If it can't, can it go on the feature request list please? Simon

Just wondering ... Is there any particular time I should run the "manage modules" command? With new firmware builds there is some announcement here that one has been released and I know to go install 3.1.14 (!) or whatever. But what changes are made to the Elk module, for example, that would need me to update the module as opposed to the firmware? We got some fixes already and they work for me, but I always get the "modules are up to date message" , so is the module updating automatic or irrelevant because the fixes are done in the firmware itself? Cheers, Simon

Getting rid of SWL v35 did help my system. In the summer of 2010 I changed out 5 or 6 v35 SwitchLincs that were maybe 6 months old at that point, clearly still under warranty - they did check the purchase dates, which was easy since I had purchased directly from SH. I just asked to exchange them "because they were V35" and I was using them with an ISY-99i. Nobody challenged this or suggested I try a bunch of factory resets or whatever, they were very good and just cross-shipped newer units. My comm problems basically disappeared. SH seemed very reasonable to me, much as I wish they were more pro-active about notifications (some people apparently had Venstar V2 thermostat problem notifications; not me, but mine's in the junk pile now and I'm not going back ) Simon