larryllix

Just as aside, I always try to avoid house code "A" and in particular code "A1". Almost all units, when new, were shipped with A1 as the default device code. Any neighbour buying some X10 devices online may be interfering with your "A1" addressed device.

I have the X10 module and have defined a phoney unit called "Vacation Mode" which I turn On and Off from inside the ISY. Mobilinc can see it as a device in My Favourites.

That's what I was thinking but after reading the statement I got overthinking it and started doubting what I thought I knew. Thanks!

Lee, for my own clarity. While what you stated would be true when only the time frame trigger is installed in the "If" but when the time frame is used as a condition (used with another trigger) would the time constraint not be evaluated each time that other trigger even was incurred? So as an example: If Control from Motion Sensor is Switched On and From 10:00PM to 6:00AM Then Do It Else - Would the time parameters not also be examined for true or false (inside/outside the frame ) each time 'Control from Motion Sensor is Switched On' is triggered?

Twofold. The from-to construct acts as triggers at each time node as well as it can act as a condition filter for other triggers. If . Control from Motion Sensor is Switched On and . From 10:00PM . to 6:00AM Then . Turn Driveway Lights on . Wait 1 hour . Turn Driveway Lights off Else . - It is generally a good policy to avoid the else with multiple triggers/conditions as every false result of the complex logic will trigger it. Many don't like this aspect of the 'if' section conditions and would like an option in future versions that could eliminate the trigger from any conditional line of code.

Programme needs to be split into two as all the negatives will trigger the else code. Namely .4:00 PM or .Program 'IsSabbathOrHoliday' is NOT True or .Program 'IsOnVacation' is NOT False or 10:00 AM and another status is false. Two programmes, one disabled, can separate statuses conditions and stop them from initiating triggers.

I have the v.0D firmware version in use for the last few weeks now and it appears to work fine. - The Humidity updates every 60 seconds regularly. - Temperature (current) and reports by exception ie. every change - Heat and Cool (soft contacts) calls report by exception. - ISY contains actions that do not (and possibly cannot) work with 2441WTH version alone. ie. Synchronise Time, Setpoint Up/Down 1 deg. - I tried the unit with a 5.7vdc and 5.0vdc adapters and can detect no reporting or feature/frequency of reporting difference. - Wireless (only) range is really good even through a shop, in a separate building, completely covered by metal roof and foil coated insulation (joints foil taped). Commercial radio reception is almost impossible there. Three windows need to be near line-of-site. I have since added a LampLinc as a powerline repeater for the flakey MS communications that have a worse wireless range. - Local temperature only displays integer degrees with no Celsius option despite sending 0.5 F resolution. Peeve: temperature reporting exceptions are not always on 0.5 degree change. **ISY Feature request: temperature store into variables and setpoint(s) set from variables **

This may give you some help with this. Read down to Xathros posts He has a good grip on this stuff. viewtopic.php?f=27&t=13564 Do a search. You will many discussions on this basic motion to light control usage.

This sounds like more arguments for more system variable user access in programmes. There must be something in the internal system flags to indicate a failure to communicate with the PLM. Users could easily write programmes to send notifications based on that flag and/or reboot the ISY several times in attempts to recover without human intervention, especially in the case of remote systems.

The short timeframe of the Java updates has to tell us something. I noticed flakey operation ever since I updated to v4.1.2. I noticed other areas operating a bit weird so I figured it was the new Java7u55 I had to install with the ISY update. I found the Java 8u5 version and installed on one PC but when I went back to update another PC the next day Java 8u5 version didn't exist. I wondered if bugs were found and it was pulled temporarily as it is back again. I believe Java 8u5 is the first 64 bit version also, something they originally reported they wouldn't support. Seems to be sudden new market drive from Oracle lately.

Some confusion on posters, maybe? I am not the OP. Sorry for the bad timing. I only posted a simple example since the OP had only a few posts and this point threw me for a while.

I found the need for the negative and second "If" trigger a little surprising. The remotes seem to require programming a little differently than some other devices. If Control 'Gathering Room / Remote.B' is switched On Or Control 'Gathering Room / Remote.B' is not switched Off Then Set 'Gathering Room / Flower Lamp on desk' On Wait 30 minutes Set 'Gathering Room / Flower Lamp on desk' Off Else Set 'Gathering Room / Flower Lamp on desk' Off If: Need both conditions to trigger both Then & Else

I have tried this using two different PCs with Java 8u5 and neither displayed the problems I had with Java 7 versions. A desktop runs Win 7 Pro x64 and sleeps. A netbook running Win 7 Home x32 sleeps and hibernates. I have run one trial only, on each, with Java 8u5 installed. On both PCs, when woke up, after sleeping all night (and me too ), the Admin Console login box was there, pre-filled in, and all I had to do was push twice to continue as if it never happened. Running UD v4.1.2

Since the last few Java upgrades mine does the same thing. If you leave the PC and it goes to sleep the Amin Console will do nasty things. Sometimes just not closing the Admin Console for a few hours will cause it to act crazy. It seems after about an hour I have to sign back into the Admin Console. Most times it locks out many functions. It appears normal and sometimes I can edit programs but they won't save or only some edits will save. Sometimes devices can not be mannually controlled or will not update. After many times of frustration I have learned when I see erratic, nonsense, behaviour from the Admin Console after, especially after leaving it for an extended time, to close it and reload it. Then it behaves as it should. I never found this behaviour before Java 7 updates. I have not noticed this with Java 8 (64 bit), which is a lot faster and smoother.

An X10 device would be required to eliminate any X10 response from Insteon devices without factory resetting them. Perhaps a wired keypad can be borrowed from a neighbour that is sending the X10 codes, assuming the X10 events are real signals. Years back I had X10 devices that suddenly started turning themselves on and off in the idle of the night. This happened many times after that. After attempting to figure who the techie neighbour was, in frustration I wrote some loops to send all lights on and off for a few hours on the same house code. I never saw a house with flashing lights but it stopped and never happened again. Either the neighbour took the units back or changed his house code not to interfere with mine.

I have many X-10 motion sensors that control Insteon modules directly and the ISY doesn't know they are being operated. My programmes usually include a dummy command to turn the (already on) Insteon module on just so ISY knows it is on. The ISY sees the X-10 command on the powerlines but sees no status change report from the affected Insteon module(s). I second Brian H's idea about an Insteon device with an X-10 link installed in it. Now you may have a neighbour with an Insteon system affecting you. Assuming you factory reset all these Insteon devices when you installed them, does anybody know if a factory reset removes X-10 links in Insteon devices?

Can you copy each programme and paste them here so people can examine the fine details ot the syntax? Use the right click on the programmes and the "Code" button above the text box to paste them in verbatim format.

Does this mean they even ran the Admin Panel to edit the ISY? You also got some nasty Trojan on your PC to get rid of I would think.

Wouldn't a few soil moisture sensors with some averaging and outlier logic and alarms be a much more reliable source than attempting to use a lot of fudged factor math based on unreliable information from some school kids?

I find the same multiple login if I run the java shortcut directly with the same versions as above. This started with 4.1.2 and the Java 51 update for me. If I run this one "ISY admin.jnlp" the problem is very infrequent. I also notice the admin panel hangs if I leave it minimized for more than a few minutes and there is no way out of it except to use and kill the process in the task manager.

Have a look at this thread. http://forum.universal-devices.com/viewtopic.php?f=27&t=13564

You could slow the response down by using separate timing loop(s), testing variables used as semaphores sent from the thermostat triggered programmes

What model of battery do the leak detectors take?

I hear ya'! Well, sometimes!

"Not I", said the wolf, reading by the pool.