Mustang65 Posted December 23, 2019 Share Posted December 23, 2019 As day #1 of Running 5.0.16B has come an gone, I have been having some interesting "ALERTS" generated. My 2843 (R3.0) Open/Close sensors have been triggering and sending me alerts when the doors are not being opened. This was not an issue in Running 5.0.12. I disabled the programs and re-enabled them about 15 minutes ago. There have been no changes to the programs. I think I am going to disable the programs for overnight, and re-enable them in the morning, as I do not want to have them triggering while I am trying to get some sleep. I have not looked at the log files yet. Any thoughts Link to comment
Techman Posted December 23, 2019 Share Posted December 23, 2019 On 12/22/2019 at 6:54 PM, Mustang65 said: As day #1 of Running 5.0.16B has come an gone, I have been having some interesting "ALERTS" generated. My 2843 (R3.0) Open/Close sensors have been triggering and sending me alerts when the doors are not being opened. This was not an issue in Running 5.0.12. I disabled the programs and re-enabled them about 15 minutes ago. There have been no changes to the programs. I think I am going to disable the programs for overnight, and re-enable them in the morning, as I do not want to have them triggering while I am trying to get some sleep. I have not looked at the log files yet. Any thoughts UPDATED: my problem is with the 2421 sensor. I previously said it was the 2843 I've had the 2421 v.43 open/close sensor recently trigger a couple of times. The ISY status will show the sensor as open when it's actually closed. I also tried doing a factory reset and replacing the battery. In my case it has only happened a couple of times and that was several days ago. No false outs since then. I've since replaced the sensor as a precautionary measure. I'm also running 5.0.16B You might try replacing your battery Link to comment
Mustang65 Posted December 23, 2019 Author Share Posted December 23, 2019 Well, needles to say I forgot to disable the lanai screen door program last night and at 1:14AM my phone gave me an alert. I looked at the log and it is showing as open at that time. This morning I went to each sensor and took the battery out and replaced it. This worked (so far) for most of the 2843 sensors but a few did not care. So I took the batteries out and reinstalled them again for those that were still confused. Since then I have not received a false door open alert, and when I do open the door they are working fine.... so far. I have all new batteries in them. Link to comment
Mustang65 Posted December 23, 2019 Author Share Posted December 23, 2019 The reason for installing all these Insteon Open/Close sensors is because I eliminated the SimpliSafe Open/Close sensors that I only used for alerts and not alarm (screen doors, perimeter gates, shed..) and installed a bunch of 2843 sensors in their place. I discontinued the $25/Mo SimpliSafe Interactive Plan and switched to the basic $15/Mo plan for the important sensors. The 2843 sensors were working great up until I installed 15.0.16B. I hope that the reset and batteries fixed the problems or I may go back to 15.0.12. Although, I do have one more sensor to deal with, the Mail Box sensor and it beeped a little while ago, but was not opened. When it stops down pouring, I will go out and reset it also. Link to comment
Techman Posted December 23, 2019 Share Posted December 23, 2019 UPDATED: my problem is with the 2421 sensor. I previously said it was the 2843 I replaced my open/close sensor with a new unit yesterday thinking that my existing unit was defective and I just got a false on signal again with the replacement device.. The open node shows on, the closed node shows off and the heartbeat status shows on. The doors is physically closed. If I open then close the door the sensor then displays the correct state There seems to be an intermittent issue with 5.0.16B and the 2421 v.43 sensor. Link to comment
Mustang65 Posted December 23, 2019 Author Share Posted December 23, 2019 Knock on wood, since I re did the mail box sensor they seem to be working again. No false signals so far.... Let's see if I make it through the night without an alert. Link to comment
Mustang65 Posted December 24, 2019 Author Share Posted December 24, 2019 This morning I have 2 sensors that have reported door "OPEN" and we have not opened the doors. Shutting down all the 2843 sensor programs and in the next few days I will be reinstalling the old version .12 software . Link to comment
gviliunas Posted December 24, 2019 Share Posted December 24, 2019 FWIW, I have five 2421 Triggerlincs (v.43) and running 5.0.16B. I have not had any false open triggers. There must be something different in the way ISY handles 2843 vs 2421 sensors. Edit: As Simplextech noticed, I too do see random long delays of reporting "on" Link to comment
simplextech Posted December 24, 2019 Share Posted December 24, 2019 9 minutes ago, gviliunas said: FWIW, I have five 2421 Triggerlincs (v.43) and running 5.0.16B. I have not had any false open triggers. There must be something different in the way ISY handles 2843 vs 2421 sensors. For what it's worth I also have half a dozen 2421 sensors and no false opens on them. I do have random long delays of reporting "on" from them but no false reporting. Link to comment
Mustang65 Posted December 25, 2019 Author Share Posted December 25, 2019 Reinstalled 5.0.12 last night. No false door open alerts sent so far. Link to comment
Techman Posted December 27, 2019 Share Posted December 27, 2019 On 12/24/2019 at 7:54 AM, simplextech said: For what it's worth I also have half a dozen 2421 sensors and no false opens on them. I do have random long delays of reporting "on" from them but no false reporting. What's the firmware version of your 2421 sensors? Link to comment
simplextech Posted December 27, 2019 Share Posted December 27, 2019 3 minutes ago, Techman said: What's the firmware version of your 2421 sensors? They are all 43 Link to comment
Techman Posted December 27, 2019 Share Posted December 27, 2019 51 minutes ago, simplextech said: They are all 43 As are mine. I've been able to track down the cause of the false on. The heartbeat node signal is being interpreted as an ON status in 5.0.16B. It's strange that your sensors are not affected. Link to comment
simplextech Posted December 27, 2019 Share Posted December 27, 2019 2 minutes ago, Techman said: As are mine. I've been able to tack down the cause of the false on. The heartbeat node signal is being interpreted as an ON status in 5.0.16B. It's strange that your sensors are not affected. I agree that is odd. I would notice as most of mine are controlling lights but I haven't noticed them coming on or weird things. I've had a long standing issue with them of some signals being "missed" or having seriously long delays before the lights do come on though... happens occasionally but not every time. Link to comment
simplextech Posted December 27, 2019 Share Posted December 27, 2019 24 minutes ago, Techman said: As are mine. I've been able to tack down the cause of the false on. The heartbeat node signal is being interpreted as an ON status in 5.0.16B. It's strange that your sensors are not affected. One odd thing I've noticed since the 5.0.16B update with TriggerLinc's is that I get a fast pop-up query window in the Admin Console when "some" doors are opened and closed but I have not noticed it for all of them. Link to comment
Mustang65 Posted December 31, 2019 Author Share Posted December 31, 2019 When I reinstalled 5.0.16B, the 2843 sensors started their random triggering again. May just go back to 5.0.12 where the sensors work properly. Not sure how going back to 5.0.12 will work with Polisy, as Polisy wants the latest version of ISY. P.A.R. (Partners Acceptance Rating) is about 0%, as she hates my iPhone beeping for no reason at all. She is the main reason for the reinstall. Uhhhhh Here are a couple False On alerts: GEM - MAIN - 1 / GEM - DishWasher Current Voltage 122.40 Volts Sat 2019/12/28 07:55:43 AM System Log GEM - MAIN - 1 / GEM - Office-SecurityCameras Status 53.40 Watts Sat 2019/12/28 07:55:43 AM System Log GEM - MAIN - 1 / GEM - WasherShedCarPort Status 1.60 Watts Sat 2019/12/28 07:55:43 AM System Log GEM - MAIN - 1 / GEM - CH22 - FUTURE Current Voltage 122.40 Volts Sat 2019/12/28 07:55:43 AM System Log GEM - MAIN - 1 / GEM - CH29 - FUTURE Current Voltage 122.40 Volts Sat 2019/12/28 07:55:44 AM System Log Door - Lanai ScreenDoor-Heart Status On Sat 2019/12/28 07:55:46 AM System Log Door - Lanai ScreenDoor-Opene Status On Sat 2019/12/28 07:55:46 AM System Log Door - Lanai ScreenDoor-Close Status Off Sat 2019/12/28 07:55:46 AM System Log GEM - MAIN - 1 Current Voltage 122.50 Volts Sat 2019/12/28 07:55:52 AM System Log GEM - MAIN - 1 Status 74.50 Watts Sat 2019/12/28 07:55:52 AM System Log GEM - MAIN - 1 / GEM - MAIN - 2 Status 183.80 Watts Sat 2019/12/28 07:55:52 AM System Log GEM - MAIN - 1 / GEM - HVAC - 1 Status 7.70 Watts Sat 2019/12/28 07:55:52 AM System Log GEM - MAIN - 1 / GEM - HVAC - 2 Status 3.60 Watts Sat 2019/12/28 07:55:52 AM System Log GEM - MAIN - 1 / GEM - WaterHeater - 2 Current Voltage 122.50 Volts Sat 2019/12/28 07:55:52 AM System Log GEM - MAIN - 1 / GEM - Kitchen-Fridge Status 2.00 Watts Sat 2019/12/28 07:55:52 AM System Log GEM - MAIN - 1 / GEM - WasherShedCarPort Status 1.70 Watts Sat 2019/12/28 08:01:54 AM System Log GEM - MAIN - 1 / GEM - CH22 - FUTURE Current Voltage 121.90 Volts Sat 2019/12/28 08:01:54 AM System Log GEM - MAIN - 1 / GEM - CH29 - FUTURE Current Voltage 121.90 Volts Sat 2019/12/28 08:01:55 AM System Log Door - Front ScreenDoor-Heart Status On Sat 2019/12/28 08:01:56 AM System Log Door - Front ScreenDoor-Opene Status On Sat 2019/12/28 08:01:56 AM System Log Door - Front ScreenDoor-Close Status Off Sat 2019/12/28 08:01:56 AM System Log GEM - MAIN - 1 Status 74.20 Watts Sat 2019/12/28 08:02:03 AM System Log GEM - MAIN - 1 / GEM - MAIN - 2 Status 191.80 Watts Sat 2019/12/28 08:02:03 AM System Log GEM - MAIN - 1 / GEM - HVAC - 1 Status 7.80 Watts Sat 2019/12/28 08:02:03 AM System Log GEM - MAIN - 1 / GEM - Kitchen-Fridge Status 1.80 Watts Sat 2019/12/28 08:02:03 AM System Log Link to comment
Mustang65 Posted February 13, 2020 Author Share Posted February 13, 2020 Somewhere along the line I reinstalled 1.0.16C and I still am having the Insteon 2843 Open/Close sensor randomly giving false ON's. Is any one else still encountering the same problem? Link to comment
Teken Posted February 14, 2020 Share Posted February 14, 2020 Has anyone seen their leak sensors (monitoring program) constantly reset back to zero along with the heart beat never switching to 1 as being received?!? This seems related to the open / close sensor others are talking about. I haven’t upgraded to the © firmware given the feedback here.Sent from my iPhone using Tapatalk Link to comment
larryllix Posted February 14, 2020 Share Posted February 14, 2020 IIRC I read about heartbeats that only send On and previously some that alternated ON and then Off. I never saw any Off only heartbeats. Link to comment
Mustang65 Posted February 14, 2020 Author Share Posted February 14, 2020 I started this thread back in December of 2019 and still no fix. I guess I will be calling SimpliSafe to reinstate my "interactive" plan $24/month which I switched to the "Basic" plan. The reason for going with the Basic plan was that I replaced all of my (non-essential) SimpliSafe "Open/Close" sensors (set for Alert only) with the Insteon 2843 "Open/Close" sensors, for a $10/month savings. Now I guess I will be reinstalling those SimpliSafe sensors on my outer perimeter locations until the 2843 issues can be cared for. Bummer! Link to comment
Teken Posted February 14, 2020 Share Posted February 14, 2020 10 hours ago, larryllix said: IIRC I read about heartbeats that only send On and previously some that alternated ON and then Off. I never saw any Off only heartbeats. Hi Larry, I can't say the heart beat is seeing a off per say as the logs and event view haven't been reviewed. But, do know my daily status emails continue to show leak sensors either staying at 0 meaning the ISY Series Controller was rebooted. Or the expected status number of 1 that heart beat was received within the 25+ hours isn't happening. Many times the status of 2 is seen which means the heart beat has exceeded the 25+ hour threshold whether it be from me rebooting the controller and missed that window. But, in this case the controller has not been rebooted and a value of 2 (missed heart beat) is still being sent in. I'll have to pull all of the sensors from their various places and check if the batteries are still good. It's been a long time since I checked any of them and probably shouldn't expect to see the advertised 10 year run time Smarthome indicates. I'll circle back as to what I find and perhaps might push forward in using that modified leak sensor Rabbit and others have improved upon. Link to comment
Bumbershoot Posted February 14, 2020 Share Posted February 14, 2020 10 hours ago, Teken said: Has anyone seen their leak sensors (monitoring program) constantly reset back to zero along with the heart beat never switching to 1 as being received?!? This seems related to the open / close sensor others are talking about. I haven’t upgraded to the © firmware given the feedback here. Sent from my iPhone using Tapatalk I'm not sure that this is the same issue, but if you look at the 5.0.16B release notes, the issue with the leak sensors was fixed (and it was for me). My heartbeat program for leak sensors now seems to be operating as intended under 5.0.16C. A couple of my sensors occasionally miss a heartbeat, which have been correctly reported. The heartbeats resume the next day, and that also was correctly reported. Link to comment
Teken Posted February 14, 2020 Share Posted February 14, 2020 1 hour ago, Bumbershoot said: I'm not sure that this is the same issue, but if you look at the 5.0.16B release notes, the issue with the leak sensors was fixed (and it was for me). My heartbeat program for leak sensors now seems to be operating as intended under 5.0.16C. A couple of my sensors occasionally miss a heartbeat, which have been correctly reported. The heartbeats resume the next day, and that also was correctly reported. As always much thanks for the feedback and will give 5.0.16C a try this week end. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.