larryllix

Have you tried the transistor open collector intoo to IOLink? Usually, open collector outputs pull almost to 0 volts output unless heavily loaded. They do in any logic chip I used. The IOLnk sense input should have a better tolerence than that. I am guessing it will work. I don't see the purpoese of building a latching circuit. ISY programs can be ade retriggerable and tming can be set with one line of ISY code. If .....control IOInk.input is switched ON Then ,,,,Wait 30 seconds /this will get retirgged ever input pulse If ....status IOLink.input is On Then ....Wait 30 seconds /this will only get triggered when ioLink status changes. The ioLink has options for the output latching or momentary, following input and divorced. Check the device page options in admin console.

We use our rear doorbell sound for a "dryer is done" alert. Trouble is after a few years it still makes us think "who is at the door?" for a split second. Usually you can extend the drop out time of a DC relay with a series diode, resistor, and large capacitor across the coil.

If you advanced enough to write http handling code I really recommend you go to v5.0.10. You should have no trouble with it. Any bugs are monor gui layout things and it would be so simple for you to create a solution to this problem, rather than use workarounds. Then you wouldn't be rewriting you techniques later.OTOH: If you are like me you will enjoy the challenge to resolve it both ways.

Ad hominem comment? I don't know what you are going on about. If you would search the forums, you would find I have posted about a dozen different programs, attempting to teach others techniques, for getting and using temperatures into variables, including averaging three different sensors with outliers being disallowed from the formula, You don't need to preach to me about the value of getting temperatures into variables and your comment in bold seemed very out of context here. Regardless, I had forgoetten that people using less than v5.x, such as this user, do not have this capability, and need to use network resources to dump values into variables. Carry on. I have never had to use that workaround

What time is your general query set to run? Do you have a whole house scene set up?

Port forwarding is for translation through a firewall from WAN to LAN. If you are trying to access your ISY from inside your LAN to inside your LAN then port forwarding is not your tool. You need to lock your ISY ip_address down. You can do this inside the ISY or the best way is to put an entry inside your router. The router DHCP table sees MAC addresses and substitutes IP addresses for them. You can control what the router issues in the reservation table.

Wrong syntax and technique for programs. See my post again. It will do exactly what you want.

I compact my dates and times to a format like this. MMDD.hhmmss. I do this on a regular basis in V5 and keep it in an Integer variable with init to. Then I keep another flag variable set to 1 showing initialisation and init to 0. When ISY boots up I check the flag variable to see if it is initialised status and if not I create my running date.time variable. Now I send both Integer variable and my running date.time variable in a notification. Now, the notification sends the last known time (Integer date.time), as well as the current running date.time. By subtracting about 3 minutes, 30 seconds from the difference, I know how long the power was off. It's not real accurate, being based on the reboot time of ISY but it works as rough indicator. Lastly, I set the initialised status variable to 1. If you are not running v5.xx you will need another date time source. It gets a little more complicated to create than just massaging system variables.

If this device acts as any supported Insteon or Zwave device, it has a status page, and programs can be written and triggered by almost any parameter on that device page. Then it is only a case of dedicating a memory location, and writing a program to trigger on any change of value pf this parameter. If ....Multi.sensor >= 0 /reasonable low limit AND ....Multi.sensor <=99 Then ....$Variable = Multi.sensor /reasonable upper limit Else ...send notification to YOU Multi.sensor is ridiculous Hint: If you want to trigger further programs on the end result you will require the usage of a Status Variable .Now you will need an Integer variable also for the intermediate value, so that you don't rigger programs twice and on the false value. Then ....$iVariable = Multi.sensor ....$iVariable *= 1.8 ....$iVariable += 32.0 ...$sVariable = $iVariable

I use two CAO Tags for humidity control in my cold cellar. One inside and one outside. Last year, I discovered the need for Dew Point meterng, instead of Relative Humidity. Turns out, I was bringing in lower RH air from outside, but when it cooled to the cold cellar temperature, it would raise the humidity in the cold cellar, giving an unwanted result. Calculating dew point is too complex for ISY programs (using exponiatial functions) , but I have fudged a way to create it accurately, inside usuable ranges. Too bad the Tags support dew point metering, but won't send it. . Sent from my SGH-I257M using Tapatalk

Yeah. For in the house the lower may be better but for bathroom or other humidity control? Get the lower one and then use clear salt to check the other end. CAO Tags only take one adjustment anyway. It would be interestingvto see how linear they are with third party testing. My house never gets dowm to 32% Sent from my SGH-I257M using Tapatalk

Nice! Did you know you can get a fairly exact 70% R.H. for calibrating these sensors? There are some available at HomeDepot at 33.3% ? and 70% RH but you can do it much cheaper with table salt if you avoid the type with any sugar or other impurities in it. Do a web search for the technique. It's very easy and cheap involving a smaller container and larger one (or ziploc bag)

See post #6.

Only enough to setup the SSID and security, IIRC, then it goes away. I think I have run into it some time back but I could not get past the security. I don't like devices that require hubs and use proprietary protocols and have been going away from MiLight and Philips to Ledenet.

OK, one more go at it. This is a pretty standard procedure people use. "Turn on backyard floodlights when there is motion" If Status Control 'Back porch motion-Sensor' is Switched On And Status 'Backyard flood lights' is Off And From Sunset To Sunrise (next day) Then Set 'Backyard flood lights' On $backyard_motion = 1 Wait X minutes Set 'Backyard flood lights' Off Else Set 'Backyard flood lights' Off "Turn off backyard floodlights when motion stops" If Status 'Back porch motion-Sensor' is Off And $backyard_motion is 1 And From Sunset To Sunrise (next day) Then Set 'Backyard flood lights' Off $backyard_motion = 0 Using Control Switched, and getting rid of the Off command inside the MS is the usual method. The program, seeing the switched on will retrigger the Then section and also the Wait X hours. The Else section was added to catch the "Until sunrise", just in case the Wait X hours timer ever failed to turn the lights off. It's a backup control, saving potential energy waste. Now for your manual override, there are established methods to do this but with this - You can turn on the light from the switch - You can turn off the light from the switch. However, if you turn on the light from the switch during the night time frame the MS can still activate the program and turn the light off again. For the manual override (just a clue for you) think this way ... - Capture the On in a program and use Disable program "Turn on backyard floodlights when there is motion" - Capture the Off in a program and use Enable program "Turn on backyard floodlights when there is motion"

Very nice! Good sleuthing! IIRC Port 8899 is the same the MiLight controller hubs use. In the end I think we will find most of these gadgets are made by the same company, or at least the firmware is.

First program. Change first line to Switched On Get rid of second status line. It is causing the problem and doesn't serve any purpose. When you turn the light On/Off it causes the first program logic to run again and execute Then or Else. Most of us disable the MS off command and let ISY decide when to turn the lights off. It reduces Insteon traffic and stops erroneous and unexpected things from happenning. Many disable the MS night time only and let ISY decide when the lights are needed.

I don't think this resolves anything for the OP.How does this DMX controller get converted to http/ REST protocol or DMX to RGBW and back. For the rest of the HA stuff, it comes back to... why would one want to convert everything to DMX from any most Etherenet protocols that ISY can put out, and then convert DMX to some other controller protocol driving RGBW LED's? The LEdenet controllers I have (23 units), cost about $11-$12 Plus PS and cables (~ $25 total) and ISY can drive them directly without conversion back and forth to/from DMX.

In view of the hardware wanted, I guess my path might be bilding a bi-directional bridge with python3 and a RPi. Your time would be great, depending on your skills. I have code written to receive NR sends from ISY in python3 if that would help. Not sure what DMX would look like over Ethernet. http stuff is not real time. I have had trouble with packets passing each other in drivers and routers. SCADA systems have trouble with this as well so event are time stamped so they have a recording of the actual event time but that doesn't help real-time events. DMX must have this worked out somehow or not be Ethernet channel protocol sharable.

I prefer the control of having ISY as a central control.The Insteon SwitchLinc Dimmer is plug and play with ISY, and can create 6 different commands, natively. With some thought another 4 or 6 commands can be extracted from combinations..eg. Off command while already Off etc.. Just need to get control of each lighting device from ISY using Network resources, preferably without a bridge computer such as RPi. ISY is your friend to put it all together.

I don't use skills to operate lights directly, only via ISY I have never seen an Alexa skill that will do colour, yet, and I need to operate three different brands of lights with matching hues. Even Philips bulbs use different hues parameters between their Bloom and Hue bulbs. I use ISY variable charts to match them up. So for one uniform colour around the room, I use Alexa. For varios white only levels I use the SwitchLinc on the wall. For different holiday colour themes, I use the SwitchLinc on the wall and ISY sets the festive theme automatically or I can force the colour them with Alexa. "....Alexa! Turn On Halloween lights!" as well as double tap off, on the Switchlink dimmer, during the week before Halloweeen.... gets me orange and dark purple lights around the room.

...."Alexa!...Turn on mauve lights!" Five Hues, five MiLight bulbs, and four LEDenet controlled RGBWW strips all turn to the deepest beautiful mauve colour, all around the room, You won't need to dim the colours (what for?) but you will want to use at least three levels of white. I use a SwitchLinc dimmer to controll all my settings. No wall control will natively control three different protocols. I have remotes and apps for the different brands but never use them, once the novelty wore off. First thought, would be an old Android phone with an app running, mounted in a holder, on the wall. Second, would be an Insteon 4 rockt keys, mini-remote (16 commands) or KPL, for any combination you can think of. Dedicate a few functions to levels, and a few functions to select colours.

For sure, but then when editing programs, I sometimes forget to start the program again. I've been caught a few times now. Right now I rely on multiple times as I cannot depend on the "Run at startup" option. The usual fix is to add another program that kickstarts all these programs (Then). Another easy to forget item though. Hopefully UDI will add this option Run at startup, "If", "Then", "Else", to alleviate this problem.

That would be every 7 minutes due to a syntax error in the ISY syntax. This is just to call attention to users attempting to make time critical programs. Should have been somethig like Repeat and Wait 6 Minutes. Also the OP wanted 24/7 so he can remove the "to 12:00 PM" line. I like to use several OR times durig the day to restart any Repeat loop stalling, sooner, ie...when you edit the program, or the power cycles to ISY.

I have many of the LEDenet controllers you purchased. All you need is a 3A+ 12V power supply, a pigtailed power supply female inline connector, RGBWW LEDs strips, a pigtailed flat ribbon cable with 5 pin connector to match, and a few Network resources in ISY. For mobile device control, download the free app for MagicHouse UFO and select the 5 channel option. The Wall panel doesn't seem to be compatible with any of the cheap controllers and certainly is not required for that LED controller. I don't see what the the 2.4GHz protocol will support documented on a quick look, unless it is some form of DMX controller.