Techman

If you can turn on the front lawn sprinklers by clicking on the device in the device tree then you don't need to re-install the device. Try right clicking on the device then click on restore device. That will update the device link tables with the data stored in your controller.

My bad, I didn't see the strike through on the small screen.

Attached is an interesting paper comparing the various technologies. It was written a while ago but is still relevant. On page 37 it mentions that a Zwave network only supports one master controller. About how many Insteon devices do you have? Insteon compared.pdf

You can't change the frequency, it's determined by the Country you reside in. Not sure if adding a second Zmatter board would create a conflict. The eisy should be able to support a large network. Are you experiencing an out of memory issue, or are you maxed out of the number of nodes that can be supported?

Android 14

If your email is configured as TEXT try changing it to HTML, if it's configured as HTML try TEXT

@Beaker There's no logical reason why the above program shouldn't work. If you can turn on the sprinklers by turning on the device in the device tree, then the Sprinkler Controller is compatible with your eisy/polisy and firmware. When you run the then clause does the device tree show it running (solid green)?

I't's probably best to submit a support ticket

@ELA Is the issue with IR sensors (infrared sensor) or Motion Sensors? If it's with the motion sensors, are you referring to the older Motion Sensor 1 or the Motion Sensor 2? If you're referring to the older Motion Sensor you should have Jumper 5 (remote management) installed

Try removing power from the eisy for a few minutes then boot it up. If that doesn't resolve the issue then it's best to submit a support ticket

@Kevin Try uninstalling the Bluetooth Service, then reinstall it. The service has a glitch or two. UD is aware of the problem and is working on a fix.

Excellent, now on to the next issue.............

@Kevin I experienced the same issues you're having. I restarted the audio player service and the bluetooth service , paired my speakers, then rebooted my eisy and everything returned to normal After the reboot make sure the audio player output is selected to Bluetooth and the Bluetooth service is set to enabled.

@Kevin There is a known bug in the Bluetooth service. An eisy/polisy reboot will usually give you a temporary fix. After the reboot make sure your audio player output has bluetooth selected.

After you upgraded did you clear your java cache, checking all 3 boxes, then download the IoX Launcher from here: https://isy.universal-devices.com/start.jnlp

@GHenry It appears that the battery level may not be reported until the level changes. You can also try waking up the sensor by holding the set button down for 3 seconds then query the sensor. If that doesn't work then contact Aeotec support, they're very responsive. The folllowing is from Aeotec Battery level will be checked every time the device wakes up. These includes the wake-up timer, motion trigger, button click. When the battery state changed, a battery report command will be sent to the controller Engineering Spec - Aeotec TriSensor 8.pdf

If the Polisy is working there's really no advantage in upgarding to the eisy at this time. The current firmware and UI is 5.8.4 You probably need to first upgrade PG3x 3.2.27,, then update your polisy firmware. See the link below. Polisy:User Guide - Universal Devices, Inc. Wiki (universal-devices.com)

In Advanced Status Configuration, if I set a State Variable value as "Not Equal To" it shows as "Equal to"

@Beaker Use "copy to clipboard" then paste it in the forum

@Beaker Can you post a copy the program that's not working.

@ELA Can you post the program for one of the sensors that are active both day and night but that doesn't show up in the log. Are all the IR sensors identical, i.e. same manufacturer, same version.

@ELA Can you post a copy of a program that's not working correctly.

@MKonrad The most likey reason you had trouble adding the new keypad is that you incorrectly entered its address. It's very easy to misread B and 8. If you had intalled the new keypad and then right clicked on the old keypad and selected "replace with" and selected the new keypad, all your scenes and programs would have had the old keypad address replaced by the new keypad address. No programing would have been necessary.

Factory resetting the dongle most likely won't resolve the issue, It's best to wait for a reply on your support ticket.

So is there a way to see the history of the programs during the night like a log? The short answer is no.