Techman

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.

This is the 140005 error. Not sure about the Net module Rule codes. 140005 HTTP_CLIENT_READ_RESPONSE_FAILED Here's the link to the available error codes https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages

This is the program I use to monitor the heartbeat signals. If it doesn't detect a heartbeat within 27 hours then it runs a program that sends me an email. Note that this program is enabled at Startup. ---------------------------------------------------------- Sensor Heartbeat Fail Monitor - [ID 0094][Parent 0092][Run At Startup] If Control 'Screen Door Opened / Screen Door Heartbeat' is not switched On Or Control 'Screen Door Opened / Screen Door Heartbeat' is not switched Off Then Wait 27 hours Run Program 'Screen Door Sensor Heartbeat Fail' (Then Path) Else - No Actions - (To add one, press 'Action')

Here's the answer https://www.geeksforgeeks.org/little-and-big-endian-mystery/

What type of interface will be available to access Polisy? Will there be an option to xfer existing ISY data to the Polisy or will the Polisy database need to be reconstructed from scratch?

Somfy can interface with the ISY via Zwave. The Somfy motors have hardwired, replaceable batteries, and rechargeable battery options. Not sure about Hunter Douglas as some manufactures use a proprietary protocol.

In addition to the file opening on your desktop a copy is also saved in the folder where you keep your ISY backups.

I'm using the ZRTSI which integrates well with the ISY and easy to set up., The ZRTSI requires that you have the ISY Zwave module.

There are numerous options available from either Home Depot or hardware stores. The tapes are rated by the weight they can hold. The higher the rated weight capacity the better the adhesive. Yes, there are also thin tape options available.

I also swapped out some of the older motion sensors for the later version of the "old" sensor, and also replaced some of the motion sensors with the multisensor 6. I haven't experienced an all on event since then. The following is from the UDI Wiki: Random All On events are related to INSTEON commands being sent to the PLM from ISY and, on the other hand, one (or more) INSTEON devices sending events to the PLM at the same time and thus causing packet collision. RF/dual band devices increase the likelihood of this event since they send two packets for each signal. The combination of the following technique will dramatically reduce the likelihood of All On events: You don't have any programs that use Control for a device and then send a Scene command to a scene which includes the same physical device. So different buttons from the same KPL are considered one device Don't Use a Control for a device which is already a Controller for some Scene and then have the program send other INSTEON commands to other devices/scenes. This basically causes two or more events arrive at the PLM at the same time In addition, motion sensors with low battery, sometimes go crazy and start sending sequences of on/off every second or so. As such: Check Tools | Log for sequences of motion sensor on/off every few seconds and in succession If you do have those, change the motion sensor battery