Open unixweb opened 6 years ago
Any solutions? am having the same issues
And me. At least once a day. Socket hang up. Only fix is a reboot.
Yes, it's a pity because it is such a nice and useful node but not reliable.
On Fri, Mar 16, 2018 at 9:23 AM, mikebiddell notifications@github.com wrote:
And me. At least once a day. Socket hang up. Only fix is a reboot.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nabbl/node-red-contrib-google-home-notify/issues/10#issuecomment-373638515, or mute the thread https://github.com/notifications/unsubscribe-auth/AGTzwfp6hlUOQ-4Yvj3J4vrs6U38qeaJks5te3aTgaJpZM4ROsjD .
I've been waiting for this node for a couple of years...... very useful. Just needs stability
no updates? experiencing the same behaviour. a reboot of node-red appears to fix it. (redeploying doesn't help)
Hi - I am experiencing this issue - I wondered if anyone had any suggestions of a workaround , ideally that can be scripted to "autoreset" ?
Also experiencing this. Anything that can be done to troubleshoot? I am using google home minis, both experience this issue.
Also seen this; a reboot of the Google Home (mini) seems to work just as a reboot of the NodeRed instance.
Same issue here.... any fix in the roadmap?
Sometime hangs the communication with this error and only solution is to restart node-red.
{ payload: 'Der aktuelle Luftdruck 945 Hecto Pascal.\r', _msgid: 'ae65c197.9679b' } Error: read ECONNRESET { topic: 'toggle', payload: 'toggle', _msgid: '97ea7c2d.09e39' } { topic: 'toggle', payload: 'toggle', _msgid: '97ea7c2d.09e39' } { payload: 'Der aktuelle Luftdruck 946 Hecto Pascal.\r', _msgid: '60901c7c.ddd754' } Error: read ECONNRESET Error: read ECONNRESET