bh56

It's the same v.5.3.4

Sorry, I didn't explain this correctly. I did go through the Start Linking option. It did scan through while I had my device in link mode. It went through the scan, then I clicked on one of the 3 options after the scan that you have. I tried all 3 of the options, but none of them result in a device that has been added at all. So, going this route, does the scan, but no device added at all. Adding a new device, gives me the attached error message. Hope this further helps you understand the steps I took.

I also did try the Start Linking, but nothing happens when I go this route. Device is only recognized if I do New Insteon Device with specific address. When I do the Start Linking, it just goes very quickly but does not find any devices.

Yes, I did a New Insteon Device and it recognizes the device, but gives me an error that I attached in my initial post.

I did use New Insteon Device and used both Auto Discover and tried the specific version. Still no luck. Think it must be DOA?

Thanks for the offer. I have spares, just trying to leverage my investment

My appliancelinc is 2456S3 v4.9 1246. My ISY is on 5.3.4.

Thanks for the suggestion. Did the Factory Reset, made sure to choose my exact model and version. I'm still getting the same error message. Maybe it is fried?

Thanks for the suggestion. I tried right next to the outlet the PLM is connected to. Same issue. So, must be the ApplianceLinc has failed? I've only had the PLM fail on me, not any of the devices so far. Guess it's not too bad since I started down the Insteon/ISY route in 2012.

I've got an AppianceLinc #2456S3 it's a V4.9 1246. Has been working forever. Recently is not recognized from my ISY994i. I can't seem to add the device again. I removed the old/dead one. It starts to recognize it, but then get the error message attached. Anyone have any insight?

MrBill. Thanks so much for letting me know. I was not able to find anything about this in the forum's. I used to get the latest test versions for my home, but had reverted to waiting for the latest RC. But with this, I need my notifications and struggling to get and external one to work.

Sorry, didn't fully read your question. I'm using the java app. My notifications have worked using the default smtp server. I just noticed that I have not gotten a notification for some time. Wondering if it was when I upgraded to V5.x? Anyone else know of issues? Should up update the the most current test version?

This is related to smtp email notifications. I'm using Chrome.

I've had my ISY for I think close to 10+ years. I'm on v5.3.0. I just realized that none of my notifications are coming through. I used to have the default set, but when I do I get an authentication error. When I try to set an smtp address does not appear to come through. I set the time out to 10,000 for it to not say Mail server failure. No error, but now emails. Does anybody have any ideas/insight.

Just curious if you looked at Flume, Moen, Streamlabs options. How did you land on this one? Do you have this hooked up to your ISY?

Curious on your thoughts with phyn. How did it work for you. Looking for a more complete solution to complement the leak detectors. Looking at options from Flume, Moen, Streamlabs and then came across this one.

Yes, everyone. @kclenden@MrBill @Michel Kohanim thank you so much for your help on this. After some of your insight I'm thinking I'm using the Open/Close sensor close event incorrectly. Maybe I should not be monitoring this event. I'm thinking the "Schedule" trips, the open/close sensor is in a "closed" state, thus I get the close alert. Maybe I should just be monitoring the "Open" event, as this is what I'm really looking for. But was thinking at other times, I may want to know both about the "Open" and "Close". I'll play around some more and do some more testing on this. Thanks so much for all of your help with this.

Thanks @Michel Kohanim. Michael, from 7-11(next day), i just arm the alert of any open or close event. During these times, the doors have not been opened or closed. When these events do occur, I get a different message, not the one I get at exactly the program is enabled. @MrBill, I was unable to use the Find function to find the device or program. I've not used this before, but it does not seem to work. Do I find the "Program" or Find the "Device".. I tried changing the enable to be different for the Open and Close, as I was/am enabling them at the same time. Maybe this was/is causing issues for the same device. Will see tonight if this helps.

I have an ISY 994i/IR Pro. Running v.4.8.0 I have a number of Open/Close Sensors 2843-222 v1.6. I have a few programs that turn on at a specific time to monitor if my doors are opened/closed. If From 11:00:00 PM To 7:00:00 AM (next day) And Status 'Device Sensor' is On Then Send notification Else - No Actions For these programs at the From time, I get the following message: Front Entry - CloseA Schedule was met at 2020/09/09 11:03:00 PM.---------------------------------------- At: 2020/09/09 11:03:00 PMProgram: Front Entry - Close Does anyone have any idea of what causes these to be generated?

Xathros, Thanks so much for pointing me in this direction. I will look at this thread further and see if I can diagnose as it appear that some may have done so. Not sure if there is a conclusion either. But maybe help me in finding a solution.

I have a 2441TH. Periodically the Thermostat switches into the Economy Mode. The leaf button. This changes the temperature about 4 degrees colder. Some type of offset. I've contacted Insteon and told them that I am using ISY Device. They said that that is the variable and it it possible for the ISY to send a command that could trigger the Economy Mode. and suggested I contact Universal Devices. Wondering if anyone else has experienced this issue and knows what causes this situation? I'm on the 4.05 version. Plan to upgrade to the latest, but currently traveling and will do when I return.

I've had my 2441TH almost a year. Recently got a new furnace. Just started seeing the Energy Mode randomly getting switched on. Seems similar to others problems. Didn't see that anyone ever solved their issues. Either by changing something with the ISY programs or getting a new 2441TH and it eventually getting fixed. Did Insteon every indicate there was a problem and/or fixed?

Just a follow-up to this posting. I think I've got it figured up and working. To assist others, here is what I have determined. 1) When you add the 2852-222 to the ISY, you get to Nodes. A Dry and a Wet node. It appears the ISY expects the "Dry" to equal Off if the contacts are "Dry". When you wet the sensors(put on wet papertowel), then the Dry sensor goes to "On". This remains until "reset" via the set button. - Although to me these nodes seem flip flopped, it makes a little sense that the "On" stays on until changed via the set button. This would prevent the scenario if the sensor got tipped over while getting wet and then dried off. 2) I also used the Group Device to group the Dry and Wet Nodes together under the "Dry" node and then monitor that as the above describes. Again, although does not make 100% clear to me as it get's added as Dry/Wet, I think I have got it to where my ISY program can monitor it correctly(at least as defined)

Thanks for the information. Will see if I can monitor mine and see if I can tell what the heart beat is. Do you know if there is a way in ISY to monitor for a specific device or do you need to dump the log and search this out?

What about the "heartbeat" mention on insteon' site. Does the ISY support this feature? Is this the same as Responding? So if it's not responding there is either a battery or connectivity problem? "To add a level of security, the sensor also features a "heartbeat" signal which is sent daily. This can be used by central controllers and/or cloud services to notify you that the sensor is still functioning or in the absence of the signal that there is a problem." http://www.insteon.net/2852-222-leak-sensor.html