Techman

What version of the ISY firmware and UI are you running?

I added the Smart Switch 7 yesterday without issues. I'm running 5.3.3

Glad to hear you got it resolved.

Not sure what "Network Empty" refers to. Best to wait for a response from your support ticket.

Click on Zwave, Advanced, Zwave information. Does it show as connected, etc.

It's possible that you may have a bad Zwave back up or that the Zwave dongle is defective. It's best to submit a support ticket to UDI and let them analyze the problem.

Don't try to restore the ISY 4.9.0 firmware as it's not compatible with the 500 series Z-wave dongle. You must do a zwave restore which will populate the 500 series dongle with the data that was stored on your 300 series dongle. Click on Zwave then Zwave version, it should be 6.81.00. If it isn't then the dongle may not be properly installed.

also make sure that your ISY firmware and your UI are the same version. The 500 series is not compatible with the 4.9.0 version so don't do a restore.

I also would like the network module supported in the polisy, assuming that's possible.

Here's the manual on the new USB PLM. Not sure if it will ever see the light of day. It seems that all we would need is a compatible cable. If you scroll down you'll see a 2234-223 which is the serial port version. These are both pending FCC approval. 2234-222.pdf The specs are impressive. 2234-222.pdf

Aeotec shows the Aeotec Siren as compatible, and tested, with the ISY. Try moving the siren to a different location and adding again.

It sounds like it's trying to write updates to your battery operated devices. If that's the case then in the admin console clicik on FILES then disable AUTOMATIC WRITES TO BATTERY POWERED DEVICES. If the battery operated devices show a 1011 to the left of the device name then you'll have to put the device into the linking mode then right click on the device name and then click on write updates. Only one battery operated device should be in the linking mode at any time otherwise your link tables can get corrupted.

We lost internet connectivity for most of the day yesterday and I noticed that I was unable to access the Admin Console over my LAN during the outage. Was it trying to validate credentials over the internet? I thought the ISY / Admin Console were self sufficient.

Adding to the above, only one battery operated device should be in the linking mode at any time. If multiple battery operated devices are put into the linking mode at the same time the link tables can become cross linked. The battery operated device must be manually put into the linking mode before you can write an update to it. Another possibility: the following program worked with earlier ISY firmware versions, not sure if it's currently compatible. Disable or delete the program after you write the updates to the device. If 'South Stairs Motion Sensor' is switched On Then Set 'South Stairs Motion Sensor' Write Changes Else - No Actions - (To add one, press 'Action')

If you delete a device the device will be removed from any program it's associated with. If you factory reset a device then do a restore device the programs won't be affected.

Also take a hard look at the device id 56.18.5A. Make sure it's 18 not 1B as the two can be misread, especially with the newer labeling that Smarthome is using.

Did you follow the "replace PLM procedure" in the attached file? Replace ISY PLM.pdf

I'm not familiar with Home Assistant but it's possible that there may be a conflict between your devices, ISY and Home Assistant. Try putting one of your battery operated devices into the linking mode then do a restore device from the ISY as it's possible that your device link records got corrupted. The restore device should fix that.

Another option would be to have the IOLinc send you an email or text message when the pump overflows, you could then remotely shut off the HVAC using the Carrier app on a computer or cell phone.

What you've described should work. The 2466SW is rated at 15 amps. The only concern I have is if you shut off the HVAC power during a heating cycle the furnace fan which usually runs for a few minutes after the gas valve closes to cool down the heat exchanger, will not run and may cause the heat exchanger to overheat. Did you explore the possibility of sending a signal to the thermostat to turn off the HVAC, that would allow the fan to continue to run for a few minutes if the heat is on. Do you know what protocol the HVAC uses to communicate with the thermostat?

The only reason I can think of is if the ISY isn't getting the signal back from the fan. Sometimes a motor or other device can create noise on the powerline and interfere with the Insteon signal. Are you able to turn the fan on and off from the ISY without using the program? Try changing the OFF to ON in you program and then right click on the program and run the THEN clause to see if the fan turns on. I've come across instances where a device will turn on but won't turn off due to the noise the device creates on the powerline. This is especially true if you have a UPS, Computer or other electrical device on the same circuit as the ISY or the device you're trying to operate.

If the IF clause is true then the THEN clause will run If the IF clause is false then the ELSE clause will run I've attached the ISY cookbook which is an excellent guide to using and programing the ISY 35358288_ISYCookbook.pdf

GREEN means that the THEN clause has executed RED means that the ELSE clause has executed If you right click on a program then click on run THEN, the then clause should execute Try manually turning on the fan at the switch, then right click on the THEN clause to see if the fan turns off. Let me know what happens

If the program doesn't turn the Master bath fan on or off then it could be a communication issue between the switch and the ISY. If you turn the fan on and off from the ISY does the fan correctly respond?

There are two types of persistent sockets in ISY: RSub = Regular Sub = a Client subscribing to ISY (including websockets) PSub = Portal Sub = subscription from the portal Error 6 = the client that subscribed is no longer active. In the TCP vernacular, the socket is in CLOSE_WAIT state. This will eventually go away by itself.