If I have cancelled my digital life service will I still be able to to use this?
No. This requires Digital Life service to work.
Hi ady624ā¦Thanks for all the work you put into the HomeCloudHub. Iām new here and just installed the HomeCloud and getting the following error:
[ERR_INVALID_CALLBACK]: Callback must be a function
(node:7286) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Is there a fix for this that you know of?
Thanks
hey guys, just saw this. Iāll take a look at the code, Iām using this and it still works, so I never had to check IDE logs. Got any line number info?
I have had the Homecloudhub integrations for the past two years and the past several days, I am getting an error stating that "[homecloudhub] Failed sending event: Error: read ECONNRESET and then it stops the node service and "throw er; //Unhandled āerrorā event. When I restart the service, it occasionally throws an error: Error read ECONNRESET at _errnoException (util.js:1024:11) at TCP.onread (net.js:615:25). I restarted the service several times and can get it to start the node service but will only run for about an hour before it quits after throwing several āError: read ECONNRESETā errors. Any input would be great
I have not looked at any logs or done any troubleshooting yet but I also noticed significant delays and the need to reconnect/ restart for about 2 weeks now. I assumed it was an ATT issue like so often before.
I will post logs when I get some time to look at details.
Hey ady624 - First, I love your code. Iāve been using it for some time now, typically I have no issues (that are not related to AT&T 
) But, I do have a long-standing re-occuring issueā¦With some regularity the listener connection is terminated, and it typically happens every 20 minutes or soā¦The downside of this is that over time I miss events (doors/windows opening and closing) as well as automation failures that tries to arm/disarm automatically, etc. (it typically takes about 30 seconds to recover, so 30 seconds of downtime every 20 minutes). Further, every so often (at least every few days) it does not initialize causing me to have to go in and kill and restart the daemon. Any wisdom here?
Jul 17 08:05:16 raspberrypi node[9878]: 7/17/2019, 8:05:16 AM [digitallife] Listener connection terminated, recovering...
Jul 17 08:25:25 raspberrypi node[9878]: 7/17/2019, 8:25:25 AM [digitallife] Listener connection terminated, recovering...
Jul 17 08:45:36 raspberrypi node[9878]: 7/17/2019, 8:45:36 AM [digitallife] Listener connection terminated, recovering...
Jul 17 09:05:48 raspberrypi node[9878]: 7/17/2019, 9:05:48 AM [digitallife] Listener connection terminated, recovering...
Thank you!!
My integration stopped working a while back and I tried to re-install without success.
I found this article that addresses the 2nd part of your error. It looks like line 131 in the homecloudhub.js needs to be updated to work with the newer node.js version?
Now, I am still getting the ā[ERR_INVALID_CALLBACK]: Callback must be a functionā error.
After so many years of use, I have finally run into a problem I can not solve with this app.
Any help?
This is on the homecloudhub pi:
Aug 30 05:18:29 raspberrypi node[17942]: 8/30/2019, 5:18:29 AM [homecloudhub] ====================================================================================================
Aug 30 05:18:29 raspberrypi node[17942]: 8/30/2019, 5:18:29 AM [homecloudhub] Retrieved config with server at 192.168.1.XXXX:39500
Aug 30 05:18:37 raspberrypi node[17942]: events.js:163
Aug 30 05:18:37 raspberrypi node[17942]: throw er; // Unhandled 'error' event
Aug 30 05:18:37 raspberrypi node[17942]: ^
Aug 30 05:18:37 raspberrypi node[17942]: Error: socket hang up
Aug 30 05:18:37 raspberrypi node[17942]: at createHangUpError (_http_client.js:302:15)
Aug 30 05:18:37 raspberrypi node[17942]: at Socket.socketOnEnd (_http_client.js:394:23)
Aug 30 05:18:37 raspberrypi node[17942]: at emitNone (events.js:91:20)
Aug 30 05:18:37 raspberrypi node[17942]: at Socket.emit (events.js:188:7)
Aug 30 05:18:37 raspberrypi node[17942]: at endReadableNT (_stream_readable.js:975:12)
Aug 30 05:18:37 raspberrypi node[17942]: at _combinedTickCallback (internal/process/next_tick.js:80:11)
Aug 30 05:18:37 raspberrypi node[17942]: at process._tickCallback (internal/process/next_tick.js:104:9)
Aug 30 05:18:37 raspberrypi systemd[1]: **homecloudhub.service: main process exited, code=exited, status=1/FAILURE**
Aug 30 05:18:37 raspberrypi systemd[1]: **Unit homecloudhub.service entered failed state.**
Aug 30 05:18:48 raspberrypi systemd[1]: homecloudhub.service holdoff time over, scheduling restart.
Aug 30 05:18:48 raspberrypi systemd[1]: Stopping Node.js Local Home Cloud Hub Server...
Aug 30 05:18:48 raspberrypi systemd[1]: Starting Node.js Local Home Cloud Hub Server...
Aug 30 05:18:48 raspberrypi systemd[1]: Started Node.js Local Home Cloud Hub Server.
Aug 30 05:18:51 raspberrypi node[17953]: 8/30/2019, 5:18:51 AM [homecloudhub] Home Cloud Hub app v0.1With the forced migration coming I assume this will no longer work?