zorax2 Posted November 27, 2023 Share Posted November 27, 2023 I recently started receiving notifications on my UDI Mobile App showing "ELK (1): Failed from PG3" followed (usually within a minute) by "ELK (1): Connected from PG3". These notifications are at least daily and sometimes multiple times per day. I turned off the sound for notifications due to the frequency of the notifications. I don't recall this happening in the past and it seems to have started within the past month I'm guessing. I just thought it was an aberration and would go away on its own. In terms of troubleshooting, I'm stumped. I have my cable modem, router and ISY on an uninterruptible power supply. There is no evidence of a bad internet connection at the failure times on either my cable modem or router logs. My Elk alarm panel gave a system battery error last week but I replaced the system 12V 8AH battery within a few days and continued to recieve these notifications both before and after the battery replacement. There are no other causal factors I can tie to this other than the notification behavior seems completely random. Any ideas? Link to comment
Jimbo.Automates Posted November 27, 2023 Share Posted November 27, 2023 Please run the reinstall all plugins from the PG3 UI. There have been a couple recent fixes to the PG3 Python interface recently that resolved similar issues.Sent from my Pixel 8 Pro using Tapatalk Link to comment
zorax2 Posted November 27, 2023 Author Share Posted November 27, 2023 Thank you! I'll go ahead with your recommended solution. Link to comment
DennisC Posted November 28, 2023 Share Posted November 28, 2023 Don't be surprised if you continue to have this issue after reinstalling the plugin. There is still an issue UD is working on correcting. Link to comment
Jimbo.Automates Posted November 28, 2023 Share Posted November 28, 2023 Don't be surprised if you continue to have this issue after reinstalling the plugin. There is still an issue UD is working on correcting. @bmercier updated a couple days ago and that has resolved my issue so far.Sent from my Pixel 8 Pro using Tapatalk Link to comment
DennisC Posted November 28, 2023 Share Posted November 28, 2023 4 minutes ago, Jimbo.Automates said: @bmercier updated a couple days ago and that has resolved my issue so far. Sent from my Pixel 8 Pro using Tapatalk I'm still having issues, as late as this afternoon. This was after installing another Python Interface update this morning. @bmercier is aware of this and has been working on a solution. I sent him additional log information this afternoon. Link to comment
GJ Software Products Posted January 1 Share Posted January 1 Still today I too am seeing: "ELK (1): Failed" then "ELK (1): Connected" within one minute on the UD Mobile app. The node seems to be working, it's just those annoying messages. I'm at 5.7.1_7, 3.2.17, and Elk 3.10.11 . Link to comment
zorax2 Posted January 1 Author Share Posted January 1 I’m having the same issue. I thought I was perhaps losing my connection with the Internet provider but it’s always one minute at random times. Link to comment
Jimbo.Automates Posted January 1 Share Posted January 1 If you can grab a log package soon after it happens then please PM it to me.Sent from my Pixel 8 Pro using Tapatalk Link to comment
zorax2 Posted January 7 Author Share Posted January 7 PM Sent with log package attached. Thank you. Link to comment
Jimbo.Automates Posted January 9 Share Posted January 9 The log shows a PG3x error, please submit a support ticket and include those log packages and information. 2024-01-06 19:34:06,657 Thread-34461 udi_interface.interface CRITICAL interface:send_thread: Message send thread aborting: Message publish failed: The client is not currently connected. Link to comment
GJ Software Products Posted March 10 Share Posted March 10 I'm still intermittently getting this error as recent as 3/9/24. 5.8.0_1 , 3.2.19 , 3.10.15 . Link to comment
Jimbo.Automates Posted March 11 Share Posted March 11 On 3/10/2024 at 12:09 PM, GJ Software Products said: I'm still intermittently getting this error as recent as 3/9/24. 5.8.0_1 , 3.2.19 , 3.10.15 . Will need @bmercier to review your PG3 logs. Link to comment
Recommended Posts