larryllix

As a matter of inerest here is how I got around the log usage with ISY. A simple calcualtion of %RH divided by a factor of 5 was offered elsewhere but the curve gets way off at one end of the range. Note how this line has been used as an inline If/Then condition to fudge any humidity over 45% ...Repeat While $Variable > 45 This is to bring dewpoint resultant at that end of the curve, closer to the actual conversion curves . I use three programs like this, for conversion of inside, outside and cold cellar %RH humidities to dewpoint humidity readings. Sync.DewPoint.in - [ID 0128][Parent 0101] If $sHouse.humidity <= 100 Or $sHouse.temperature <= 100 Then $House.dewPoint.scratch2 = 100 $House.dewPoint.scratch2 -= $sHouse.humidity $House.dewPoint.scratch1 = $House.dewPoint.scratch2 Repeat While $House.dewPoint.scratch1 > 45 $House.dewPoint.scratch1 -= 45 $House.dewPoint.scratch1 *= 0.7 $House.dewPoint.scratch2 += $House.dewPoint.scratch1 $House.dewPoint.scratch1 = 0 Repeat 1 times $House.dewPoint.scratch2 /= 5 $House.dewPoint.scratch2 -= $sHouse.temperature $House.dewPoint.scratch2 *= -1 $sHouse.dewPoint.in = $House.dewPoint.scratch2 Else - No Actions - (To add one, press 'Action')

Yeah. Dew point is only necessary where you compare two humidity levels. I calculate mine, dynamically, using ISY programs so Logs are not happenin' there. My usage is my cold cellar running at 10-18C degrees, and if you bring in warmer and lower RH% air, very often you will increase the humidity RH% as the temperature drops. Use SOAP RPN, I do not. To do the work for me, I like my computers.

There is a troubleshooting chart based on the LED pattern. Not sure where to find it but Google is your friend. First try a power cycle of the PLM and ISY. PLM gets powered up first for a few seconds, and then ISY. If that doesn't work, try a factory reset. Research how to do it, so you have better access to proper troubleshooting information. I hope you have a good backup file. If you factory reset it, you will need the factory password, reset the location information and then use your back up file.

That's awesome! Many people will have usage for that find. Softeners do a lot of clear water flushing at the end of the cycle but the salt could be a problem for some internal part maybe. Hopefully not, Price is excellent too. You da' man!

I use dew point to run exhaust fans now. It is more predictive of the desired resultant. I discovered by exhausting air with a higher humidity than the outside air, I may still be increasing the humidity, instead of lowering it, once the incoming air is cooled down to the room temperature. Dew Point comparisons eliminate this and it's easy to calculate.

Other than a multiple try or a better mail server I don't know. Repeat 2 times (Canuck = twice ) ...send X email notification to ES1400 ...send X sms notification to ES1400 ...wait 1 hour Repeat 1 times

It's upgradeable right from inside your ISY admin console.

hmmmm. I might have a screen shot somewhere here.... IIRC you are one of those apple guys and they only allow a single core

Try deleting all the java cache stuff and reloading the admin console.

This was reported by a previous poster about a year ago. Can't remember the fix though...sorry. I would try a factory reset of the ISY. You will have to fix your password and time zone options. Make sure you have a good backup image. I have had a few installation quirks in my time. The firmware was always great but the install got confused somehow.

Has the admin console worked OK from the same device when at home, via the same comm path? You haven't said what type of connection you are using (public, private, hotel, shopping mail) or what type type of device you are using. ISY has a soft reboot found on the System? Tab on the far right.

Sounds like a intermittent comm problem. I take it you are away from your LAN. The missing devices sounds like a hang during the data loading. My guess is ISY is fine. Do you have any anti-virus or firewall things on your remote device that have suddenly jumped into action, not liking your access? Some ports are not liked by public style access points.

ahhhhh.. This would fit in with the checkbox at the end of every line idea, to enable/disable it. It would have a slightly different function in the If section.

Probably all the same electronics and paddle but with one component missing that allows dimming to happen The paddles may put out Dim and Brighten also. Hey that could be useful for people controlling bathroom fans and other side jobs from the same switch. We know the light control can't respond to the strange paddle pushes. I don't have any On/Off Switchlincs. Are they relay contact or Triac?

V5 has comment lines but they take too much space vertically, so far. End of line remarks would be nice.

Sorry. I was totally confused in the thread and didn't start over reading. I guess I don't understand what the Fast On/Off have to do with the logic working. Do you think the switch is contact bouncing and sending those codes by mistake?

It's a syntax error (grammaro) that has existed since Repeat was added to the ISY repertoire. ....Repeat 1 times means execute once only. I was using it in a few programs only to find out it had some problems. I don't recall what the problems were now. The discussion was posted in a thread about a year back.

This hasn't come up for quite a while but just a thought..... Status devicename is On may not test true if the dimmer is 1-99% Try status devicename is NOT off

Control devicename is switched On is not ever false if it causes the re-evaluation of the logic in that program. Control devicename is switched On calls the attention of the ISY logic engine upon receiving the On signal from a device, so while the line is being evaluated it is always True = running Then. Statuses have two states, usually On and Off. Control devicename is switched ON has two states = active and not-active. Control devicename is switched Off has two states = active and not-active. Note two different signals to detect Now just to complicate things. If ...control devicename1 is switched On ...AND ...control devicename2 is switched On can never be True = never run Then. While one line is being evaluated, due to it triggering the evaluation, the other line will always be False (at that time) and the combo will run Else. So there are two ways to do this. If ...status of devicename is On Then ....set light On Else ....set light off If ....control devicename is switched On AND ....control devicename is NOT switched Off Then ....set light On Else ....set light Off

...Repeat 0 times may have undetermined results. You should use ...Repeat 1 times as a UDI documented method. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Action

You have to scroll to bottom of all your devices and click the delete all (no exact name) before doing a further discovery in the Alexa app or it will just keep accumulating names for the same element. Amazon likes to hide things.

Mine appeared to be a "run-away program" inside an OnOff module that was sending out a bad Scene On code, after ISY would switch it on or off. I don't believe Scenes send out status changes from devices so there is no logging of status changes. This drove me crazy for months changing and turning on certain lights at random. I could query the affected units and find exact dimming levels. Then I recognised the pattern as a scene I created. ISY had no awareness of the event or levels. I still use the module to control my humidifier. Ocasionally when ISY would cycle it, the ISY log would show a bad response. After unplugging the module and then plugging it back in, it hasn't done it again since last fall. It seems it would send out a totally unrelated Scene On code, instead of an ACK. PLM was not involved with this. Insteon modules contain CPUs running code and can go into runaway loops just like any other software.

This is one of the confusing logic puzzles ISY has. Took me awhile to absorb this one. The best example I have is to use a SwitchLinc Switch Status has two states = On/ Off. This is the status of the electronic switch controlling the light. Along comes the switch handle with four states. Tapped up, Not tapped Up, tapped down, and Not tapped down = think two devices for just the paddle. So now the tap up detection = ISY "Control switch Switched On" signal has two states. Happenning now or not happenning. Also the tap down detection = ISY "Control switch Switched Off" signal has two states. Happenning now or not happenning. When an event like a SwitchLinc paddle is tapped down , the ISY engine scans all the programs to see who cares. If ....Control device is switched Off would get evaluated by the ISY engine finding it true and running Then but ....Control device is NOT switched Off, would get evaluated by the ISY engine finding it False and running the Else section. Let's see if I can confuse you further another way. The line can never be true. If the paddle is not tapped down, the program logic line, if it is ever tested, will always be False When the paddle is tapped down, the program logic line will be tested and the Not will make it False.

Turn On and Turn Off run the same program. On runs Then section. Off runs the Else section. If ....--- = nothing required for Echo vocals Then ....turn light On ....Wait 6 hours = lest yee forget. ....turn light Off Else ...turn light Off You can turn on scenes or use direct commands for any quantity of devices. Slight ramp rates cover up different reponse times, to the human eye.

As per smokegrub's program..just set a timer to notify you and let the control/switched event of the pump detection keep resetting the timer. If ....control pump is switched off (status doesn't work well here) AND ....control pump is NOT switched on (cancel Then running = off is coming) Then ....Wait 120 minutes = offtime x 2 (maybe missed one signal and eiminate nuisance notifications) ....send notification to you Else ....--- You also may want another reboot program to initiate this in case of a power failure. Enabled to run at power up. If ...-- Then ....Run (then) program above Else ...---