Mikes

I recently lost a PLM for my ISY or at least that's the best I can tell due to lack of help and useful information for debugging and the terrible admin UI. I've had my ISY since they first came out and it's been rock solid. That being said I'm tired of Java, it's horrible updating process and the very old UI so I decided to try out Zwave with a Hubitat. So far I love the Hubitat, I have a lot to learn yet but it was far easier to get setup and use than the ISY.

Thanks stillwater I remember replacing the PLM probably 4 or 5 years ago. Searching for capacitor I found the thread you mentioned. My version is much newer than those that seem to have the problems. Sounds like they have tried to fix the older issues so I am not sure if this applies to my PLM or not. I spent more time looking around for troubleshooting info and can find nothing useful. I have decided to use this issue as the another reason to move away from the ISY and Insteon platform. My ISY has been rock solid and ran great for many years and I hate to give it up. I considered adding the Zwave interface to my ISY but the Java requirement and horridly old and buggy UI with not very good programmability was the final deciding factor for me to go ahead and move on. I don't have to many Insteon devices and can say I have gotten my money's worth from them. I think I will try the Hubitat controller with some new ZWave devices. If that doesn't work out to well then I'll probably try Home Assistant.

I've had my ISY for many years running silently just fine controlling a simple handful of devices. All my devices are controlled by simple programs that just schedule outlets to come on and off at certain times. I recently noted that these controlled devices have randomly not been coming on or going off. I bring up the admin console and see a number of dialogs titled 'Failed Communicating with' and the rest of the dialog is totally empty, a couple of dialogs with same title do have details on the device that it can't communicate with. I do not that I have a couple of Insteon devices that are not currently wired in currently so would expect some f these communication errors, however, I would expect the dialogs to state what it can't communicate with. All ISY devices this evening have red exclamation points, if I right click and choose query I see a temporary 'System Busy' dialog and I sending commands, On or Off, to any of the devices does nothing. Yesterday all was the same but I was able to send commands from the admin site I've been running4.9.0 UI and firmware for many many months. Trying to trouble shoot my first thought was to look at the Tools>Log. This doesn't tell me anything useful in terms of errors, I see some entries in blue that were the scheduled programs running and sending commands, I see my manual queries and commands in red with no error information logged. I look at the Tools>Error Log and see nothing that looks like error logging. I then found Tools>Diagnostics>Event Viewer and guessed this is what I needed to see but after clicking thru the various levels I see nothing. The system status option tells me nothing about any issues. Searching for 'Failed Communicating with' in the Wiki finds nothing and in the Forum it finds nothing that helps me move forward. How do I go about troubleshooting the issue at hand.

Have not touched my very small ISY system in at least a year. It's fascinating to me that the ISY 'just runs'. Anyway I did the needed Java and auto update on ISY to 4.9 and remembered the last time I was around here that 5.x was in the works. I see 5.X has been out awhile and started looking around here wondering why auto update only went to 4.9. After reading a bit I guess its a big change but I can't seem to find anything about what the 5.X does and what I must do to update to the latest. As the Original author of this post asked and I didn't see....is there an article on what going to 5.X does and what I must be concerned about? Can I just go from 4.9 to the latest 5.X?

LeeG, I was finally able to take the time and test my situation and it does not work, which is what you have said. I have no idea how or why this program, that had worked all winter, comes up with the Responding in my If statement I wouldn't think I would have put in there and accidentally saved it but it was there and does not work. Thanks for your time and the above, where can I find more details on interpreting the above 'trace' you have posted?

I have a non Insteon thermostat switch feeding the input of a Insteon sensor. I can't believe the ISY does not tell me what type of device it is but I know it's the one folks typically use for garage door closure sensor. When the thermostat trips it closes the input Sensor. I have no other applications reading the 'Sensor' but there are some timed programs that control the 'Relay' side of the same Insteon device. Does sending a command to the 'Relay' constitute reading the 'Sensor'? One other possibility is that this doesn't actually work any longer, it was working just fine all winter. Heating season is over so I have not actually had the thermostat trip,in a while. I was actually going to refine a program, to make a 'cool' mode, to trip the sensor when temp goes below a set point. That's how I got to this question how \why does this work now.

LeeG, I'm actually trying to understand how a program that I wrote sometime back is working. I have a thermostat near my woodstove that inputs to an Insteon Input device that turns a fan on when the temp gets to hot and turns it off when temp goes back down. My program is just doing an if Status 'xxx' is Responding with then turning the fan on and the else turning the fan off. Everything I read here says this should not work. I don't remember writing this or why I may have done it this way other than reading it in the forums here somewhere. Being a long time programmer it just baffles me as to when\why these If's (programs) are called. If in a true program are simple statements executed in some flow of an application that I as a programmer know when\why this code may be executing..

I must be missing something. I would think something has to query a device to know that is not responding. If the 'If' statement does not 'query' a device how does the ISY know that a device is not responding? Is the ISY periodically querying devices? If so how often does that happen?

If used in a 'If', as below, what commands are used to test the responding state? How often does this occur? If Status '23.d1.7f-Sensor' is Responding

I guess UD does not care to follow up and answer to the issues I've found.

Finally got a partial resolution but wanted to pass on what I have so far to help anybody else not waste hours on such a simple thing. #1 My test send to email is a Hotmail address and don't know why but when using the 'default' email SMTP setting email gets dropped somewhere, does not even make it to junk mail. (Once I got gmail SMTP working under my gmail account emails did go thru to Hotmail.) #2 The screen will not save the port setting when the cursor is in the port field, i.e. you just can't change port, hit save and then Test, you must first move cursor out of port field......THERE IS NO ERROR TELLING YOU THIS. I only figured this out after changing to another tab and coming back and noted something was not right. #3 Looks like the ISY can't handle sending mail on port 465. Am awaiting response on this issue, my ISP SMTP server uses 465. Would have been nice if UDI would have populated the boxes with the default settings when you check that option. It would have been more clear what the 'Default' does than just empty out all entries and it would show what settings they are using to give you some kind of reference.

I have tripled checked all my entries and they all work in Thunderbird mail client. I am going to guess it is an issue with documentation, I love the ISY but the interface and documentation is just horrible.....and I'm a long time developer, I don't see have a non geek could do anything with this. I have submitted a ticket and will post the findings so that it might help others in the future.

I've spent hours now trying to get my ISY 994 configured to send emails. I've been over and over the SMTP settings and checked everything, I can use same settings with Thunderbird to send emails but no matter what I do the Test button on the Settins/Groups pages always failes. What I have I not done correctly?

I got a mini remote a few weeks back added it to my system IS994i/IR and created a quick program to turn a device on and off and all was well. Due to spring I've been doing outdoor chores and just getting back to continuing with my mini remote. It no longer will control my device I setup earlier. In the main window of controller app I see my remote and can watch it react to me clicking remote buttons On and off. I test the then statements of my 2 simple programs to turn a device on and off and all works. So I can see remote going on/off at console and control my device via program in console. It just appears to me that the remote events are not being fed to the programs to act upon them. What more can I do to figure out what is going on?