The developer tools show me this:
Can you explain this?
It works now. Sorry
Socket hang up basically means that Homey couldnât get a response from the camera. It could be caused by a number of things, but most likely a temporary network issue with either the camera, router or Homey.
Hi Adrian,
My Homey 2019 crashed this morning at around 04u. Some minutes later this app notified by timeline that it has stopped working and developer has been notified. Not 100% convinced that the crash and app crash are related or which one caused the other to crash, but would you be so kind to check the notification to see what happened?
Thanks,
EDIT: I did not change anything the past 2 weeks.
Could you try the new test version. I have added extra traps for error in that version.
Another 2 homeyâs 2019 with the app as well installed, no problems there. So I will install the test version of the app only on the crashed HP2019 I suppose.
Do all the Homeyâs access the same cameras?
Iâm just wondering if that could be the issue as the camera is rejecting the connection.
No, separate locations, and separate camera systems
But it rings a bell, let me see if I have a remote connection, do remember an experiment..
Hi Andrian,
at 1713u again the app stopped working (timeline info) and again the homey crashed.
I did install the test version and I also clarified any other homey connecting.
Is there anything I can contribute at this time? I will not be able to be on site after tomorrow, so when nothing changes, I need to disable the app. and with that also disable some alarm functionsâŚ
EDIT
Killed the homeylink and homesh apps to be sure, but there was nothing going on there.
You could try setting the log level Basic Information and then when it crashes the log that Homey sends might have something useful in it.
Just enabled the app again and set the log level basic. 2 questions:
Can I leave the emailaddress unfilled?
Can I close this setting popup?
Just sent the log to you also.
Yes to both.
I can see in the log that the new flood protection has kicked in a couple of times, so maybe the issue was caused by the camera sending large bursts of message to process, causing Homey to close the app if it was consuming too many resources.
ok, well. I have 3 cams of which 2 detecting cross line only. The first crash (2 days ago) was during the night, chances are slim this was caused by line crossing.
Any tips for reducing cam activity itself, so prior to use things in a flow?
Thanks
How should I read the log entry below? Nothing is going on, no line detection nothing.
I could try to disable motion detection on cam settings, but have my doubts..
17:36:2.553: Event data: (192.168.x.xxy) Monitoring/ProcessorUsage: Value = 45
17:36:10.567: Push event: 192.168.x.xxx
17:36:10.579: Push event token: Processor_Usage
17:36:10.604:
â Event detected (192.168.x.xxx) â
That entry shows the camera has pushed a CPU usage value.
Which means the events system is working.
After another look at the log you sent earlier, the camera is certainly blasting messages at Homey, so it wouldnât surprise me if it was causing the app to be killed due to high processor usage. It seems it isnât just sending messages when something changes, but constantly sending them with a false value. I have seen this before and I the the user got a firmware update for the camera to fix it.
Hi Adrian,
Ad-Hoc firmware upgrade, reset the log. Please allow me to send you the log this afternoon, hoping that data-blasting is over.
EDIT:
Sent the log again, and deleted the intercom device as this device isnât required in the app.
Just another homey crash. Will reboot now. Anything useful in the log?
EDIT:
Iâm forced by time pressure to disable the app now. I have until this evening to support you when possible and make adjustments or anything, testing period this night.
