larryllix

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.

Since the program is NOT disabled the If line causes a trigger that will cancel the wait timer in progress. IOW switch the light on manually and now it waits for a switch off and the timer is out of the picture.

I would be sure you are correct about that although I have not experienced that yet. I am ln vacation so I cannot experiment with it. I still like the initial fast on in the first programmers though. I find the program called delay time objectionable for turning lights on. Bad keyboard so I won't elaborate.

I don't think this is is even possible for UDI to do. The blame is squarely on Smarthome's shoulders for refusing to make a PLM for use outside of the USA. The Hub is a LAN based device and any LAN PC can control it with proper software. All the ISY needs is a driver to interface to the Hub and it would be a much more up to date interface than a serial port device that may be discontinued any time. The Hub's price has come down significantly lately where it could compete and possibly undercut the price of a 2413S and a serial port cable.

It should work just fine but try to get an actual transformer unit. Most of the small units are just a diode for heating devices. A transformer should pass the insteon signals back into the 220v mains voltage.

Another possibility that works well for radiators with large thermal mass and therefore slow response is proportional or PWM control. To do this with crude method you could set up three programmed each with different on times that give a "pulses" to the heating elements. Let's say one has an On time of 14 minutes, one with 8 minutes, and one with 2 minutes. Now you evaluate your floor temp against your desired temp set point and run the desired gradient of heat programmers every 15 minutes. This would give you almost 100, 50, and 15 percent heat settings so your ceramic floor doesn't overshoot and undershoot your temperature setpoint If the Wait timer is ever allowed to use a variable the PWM (pulse width modulation) times could be varied infinitely with just a calculation. Off would be a 4th level of heat. I certainly hope there is some high temperature limit for this to override a stuck on module contact or triac.

So the tstat is sending it's raw data, but the IST is prescaling it and since it can't handle fractions it can't put out the same resolution it takes in? I assume you can do math with the 0.5 values though.

You may want to fasten the thing down so you don't come home to a Tupperware boat floating across the floor keeping a leak sensor high and dry as it floats across the room!

I think most newbies have a problem with so many programmes required to do what is considered "one job" or "one function". I know it really bugged me in the beginning. What can really help the feeling of tidiness of programme filing is the use of folders that may not be immediately evident at first when starting out. An example of folder lexicology Rear Lights '**** folder (no software) sunset '**** three programmes to do functions night morning

Industrial control systems (SCADA) that I dealt with almost always sent raw binary data for analogue values. It was up to the HMI (human machine interface) to convert the data to engineering units to be viewed by humans. This way no raw sensor resolution accuracy was ever lost other than a rounded off bit (digital bobble) at times. This was a huge Insteon mistake attempting to send data in the same format as viewed on the HMI LCD screen. It would be a simple job in the ISY to multiply the raw binary temperatures by a scaling factor and add a zero offset, as needed (what about Kelvin scales?). Keeping temps as one decimal place as a x10 value is something ISY could easily do and just as easily convert it back to raw binary to send back to the tstat for settings. Dealing with truncated scales inside a computer is another ridiculous design flaw. This forum is starting to save me money!

Check to see if the lights are OFF first and if they are NOT leave them alone. If Control 'Gathering Room / Motion' is switched On And From Sunset + 6 minutes To Sunrise + 6 minutes (next day) And Status 'Gathering Room / Floor Lamp' is Off Then Set 'Gathering Room / Floor Lamp' Fast On Wait 45 seconds Set 'Gathering Room / Floor Lamp' Off Else - No Actions - (To add one, press 'Action') Note the MS is coupled directly to the module via X10 but it causes the responding lamp to come ON very slowly and I don't like it so I hit it with a 'Fast On' immediately and it beats out the ramp up with an almost immediate full brightness. The ISY is fast if you don't call another programme first. I like the slow ramp off though.