Techman

Hopefully you DIDN'T do a delete modem prior to adding the new PLM. If you did let me know.

Right click on MY PROGRAMS, the click on copy to clipboard. You can then paste the results into your word processor.

Attached is the procedure for replacing a PLM. NEVER do a delete PLM. Replace ISY PLM.pdf

I'm using the Somfy ZRTSI zwave to RTS interface. The only options are either open or closed. To use the Somfy dry contact interface you would have to send two control signals, i.e. CLOSE and STOP. That can be done using an ISY program with a WAIT clause between commands. The position the shades stops in could vary depending on various timing conditions. I'm assuming that your Somfy motors are RTS and not hardwired.

Take a look at this thread re: socket error. For the devices you're unable to communicate with do a factory reset on the device then a restore device from the admin console. It's possible that your power outage corrupted the device's memory.

This is the one you need. It's the only one compatible with the Insteon Smoke Bridge First Alert SCO501CN-3ST https://www.amazon.com/s?k=sc0501cn-3st

With the ISY 4.7.3 firmware the ISY does not support any of the sensor configuration settings, You should set the jumpers on the motion sensor accordingly. The motion sensor II is fully supported in the 5.0.15A ISY firmware and can be configured via the ISY

Take a look at this link. It's a primer on ISY programming https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order

The code executes from the top down. Sometimes moving a line of code up or down can make a difference.

Also, try removing the lines Sunset to Sunrise for testing purposes. If the lights then turn put the Sunset - Sunrise as the first line of code in your IF statement

That error indicates your SMTP server timed out. Try increasing the timeout value in the ISY email configuration. What email server are you using?

The log looks good. Try removing and reinstalling the Multisensor 6. Then do a heal. If I remember correctly you have the option of installing both devices with security encryption which is supported by the 500 series dongle. You may want to use that option if you haven't already.

The 300 series dongle will work with both 4.7.3 and 5.015A. The 500 series dongle requires the 5.x.x ISY firmware. Based on the distances between your devices everything should be working. It's possible that the update is an issue. You shouldn't have noticed any change in performance with the 300 series dongle between 4.7.3 and 5.0.15A. My guess is that the range extender didn't properly install. If you put the event viewer in level 3 then query the range extender does the extender respond without errors?

Verifying the firmware on the Multisensor 6 is a bit of a process. I wouldn't be concerned with it now. Some forum members have posted that the coverage range with the 500 module is less than the 300 module. Is your multisensory 6 running on batteries or a power supply? How far is the range extender from the multisensory 6. How far is the range extender from the ISY? Your issue appears to be that the Multisensor is not communicating with the range extender. When you moved the repeater did you do a heal each time you moved it, if not try doing that. I have both the range extender and several multisensory 6 devices using the 300 series dongle and have never had a problem. They are quite reliable.

What version of the Multisensor are you using. Do you have it updated to the latest firmware? What device are you using for a repeater? What is your ISY UI version? What version of the ZWave board do you have in your ISY?

Your first problem is that your UI and your ISY firmware are different versions, this can be problematic. Follow the instructions below to update your user interface. After you update the UI then update your ISY firmware to 4.7.3. Be sure to do an ISY backup before and after any updates. Let me know if that resolves your problem.

There's a typo in my suggestion, it should read SMARTPHONE.

The error you're getting is a MAIL SERVER DNS ERROR what parameters do you have set for your email configuration? What version of the ISY firmware and UI are you running?

The Venstar thermostats are reliable and can be controlled via a Smartphone app. All that's required is a internet connection and a/c power. They are totally independent from the ISY. You would also be able to monitor interior humidity and temperature remotely. https://venstar.com/thermostats/colortouch/

Even though 5.015A is a beta release it appears to be quite stable.

Before you do anything you need to update your UI. The UI and the ISY firmware need to be the same version. Click on the link below I would also suggest updating to 4.7.3. then do an ISY backup before you try to update to 5.x.x The new motion sensor will work with 4.7.3, but in a limited capacity. The sensor will default to a 30 seconds on signal and cannot be changed. If you decide to update to 5.015A you'll find a lot of update tips in the forum. You should use the option that includes Insteon and Zwave support.

The most reliable way to couple the two circuits would be with plug in dual band modules. Unlike the in the wall modules which have their antennas located at the back of the device, the plug in modules have external antennas which will give you much better RF coverage.

In answer to PeteF as I recall some of the sensors sent an off heartbeat signal and some sent an on heartbeat signal so you have to cover all the bases. If you include those options in your programs the heartbeat signal should be detected. The problem with Smartlabs is that they have a propensity to change their firmware without providing the release notes. The earlier sensors were called triggerlincs and the current sensors are called open/close sensors. Basically the same product with a few minor hardware and firmware modifications.

If the ISY reboots then the IF clause will run, and evaluate as true, which starts the timer. When you first create the program you have to manually run the IF clause to start the timer loop. I used this programming approach to avoid multiple programs. .

If the device is NOT switched on or if it's NOT switched off then the IF clause becomes TRUE which then starts the 27 hour timer. If the heartbeat signal is received then the IF clause becomes FALSE. When my batteries fail I always get the email.