Xathros

I did as you suggested and still have the same issue with the program tabs however, the status bar now shows "Ready" or "System busy" correctly. I guess this is a step in the right direction. For the moment, I have rolled back to 2.7.6 and all is working as it did before. No other changes to my system other than the isy version change. 2.7.7 is doing something different that Ubuntu does not agree with. One thing I have noticed during this testing: The first time a program tab is selected on a functioning console, there is a "Loading Programs" dialog with a progress bar that pops up. In the non working console, I never see that dialog. I do see other dialogs that pop up during queries and such just fine. Also, during my testing with 2.7.7, I didn't see anything that would allow me to add X10 devices into the tree. I do own the X10 module. Is that feature still included in 2.7.7 or has that been pushed out to a future version ? Let me know if there is anything I can provide to help shed some light on this issue and thanks for all of your help. -Xathros

Well, it works from Firefox on Win XP. Does not work on Firefox on Ubuntu running Java 6.16 Any thoughts ? Thanks. -X

Same result with those. Well 2 and 3 anyway - the first does not find my isy. Also, same result on 3 different systems now. Going to test from a Windows XP VM next. Thanxks. -X

Yes. Closed the browser, cleared the java cache, relaunched the browser, clear it's cache and closed/relaunched again. Still the same. Looks like the 2.7.6 console works for me and the 2.7.7 does not. I can now tell the difference as the 2.7.7 has a blank toolbar icon for new folder that the 2.7.6 console does not have. When 2.7.7 loads, there is a long (15-20 second) delay before the login box displays. 2.7.6 displays the logon and other screens quickly. I have no firewall running and no AV deamon running. The 2.7.7 statusbar always says system busy. What next. TIA -X

A little more info: If I access using the universal-devices/99i url - all seems fine except that I don't see anything new in 2.7.7 there. Using my IP address, I seem to get the old admin console and program tabs are nut functional. Also the status bar shows System Busy the whole time when I know its not. I can use the udi link when I'm home but how do I access this what I'm not home ? I have my port forwards all set up and they work - I just get the wrong console. I'm using Firefox 3.5 on Ubuntu 9.10. All worked fine until I updated to 2.7.7 this morning. About returns Ver 2.7.7 regardless of which console I use. Should I just rollback to 2.7.6 ? I purchased the X10 module and have been waiting for 2.7.7 to try it out. Thanks. -X

Just upgraded my 99i from 2.7.6 to 2.7.7 this morning. Cleared my java cache and browser cache. When I log into the admin console, I can see the Main and Config tabs just fine but if I click either of the program tabs I get a blank screen. I tried rebooting the ISY but got the same result. Where do I go from here ? TIA -X

Excellent. This is what I was hoping for. I assume the folder method would also work but for this task I like the disabled program idea better. Thanks. -X

Lets say I have a program that monitors the status of a lamp module, AND has a From-To timeframe but I only want it to run and evaluate the IF when called by another program and not any old time that the IF conditions are true. Can I simply disable the program and run(if) from another program to exec when needed or do I need to enable it and bury it in a folder with a permanently false condition on the folder ? Does calling a disabled program ie: Run(if) override the disabled flag ? I hope that made sense. Thanks in advance. -X

Michel- No problem. I bought the IES screen from Smarthome and rather than trying to swap it out, I'll just use it for now and plan on upgrading to the PoE version sometime down the road. Cross linking doesn't sound feasible so I'll continue for now with the X10 messenger method. I have simplified it a bit already by creating a query scene for each room or area and trigger those queries via X10 when the IES sets a scene. This way I don't need to query discreet devices but rather small groups of devices. Kind of a trade off between moderate network traffic or lots of work. The PoE screen sounds like the perfect solution. Just wish I had done better research before I bought the Tabletop version. Thanks again for your input on this. -X

Add me to the list of those wanting MVars to work with. I have a whole program folder called "Status" that contains kludgy workarounds for the lack of MVars. I agree they are not "Necessary" BUT boy would they make life much easier in the ISY world. -X

Hi Walter. I would be looking at the difference between status and control. If one is on then the other comes on I think it would work like this: Prog 1: If status Trigger Link is On AND Control Motion Sensor is switched on Then Run I'm Home (then) Prog 2: If status Motion Sensor is on AND control Trigger link is switched on Then Run I'm leaving (then) You don't really need the I'm Home and I'm Leaving programs. You can just add what you need to the then side of the test programs. I just like to keep my stuff modular for reuse elsewhere. Hope this helps. -X

Thanks Michael. I was afraid that would be the answer. I think I'll keep what I have for now until I can afford to buy another touchscreen. I'm sure I'll be able to resell this screen/PLM as a standalone controller sometime down the road. For the moment, the X10 messages are doing the job. Just makes my programs more complex and I have to keep track of the HU codes and their definitions on both the ISY and IES devices. Can you give an example of what you mean by cross linking. If its not overly complex, I may try that with a few of the more critical devices. Since we are sort of on topic here, do you have any recommendations for PoE power injectors ? Thanks. -X

I have 2 PLMs on my network. 1 for the ISY-99i and another connected to an IES Tabletop touchscreen. I'm looking for the best way to get the ISY to see status changes on my network when the IES touchscreen changes a device's status. Right now I have the IES send an X10 command when a Scene is activated and have traps in the ISY to act on those X10 commands but this seems like an ugly workaround. Is the a way to add the IES PLM to the ISY device tree or some way to link the PLMs so the status changes are seen by both? Thanks in advance for any help anyone can offer. -X

Yikes! If there are more than one or two cabinet doors, that will get very expensive. I think the IOLinc with a bunch of cheapo N/C reed switches (open in proximity of magnet) wired in parallel would be the way to go. One or more doors open, ramp up the lights. All doors closed, lights fast off. I love the TriggerLinc for remote door locations but it seems a bit excessive for this application. Either solution will work. -X