Script exiting with refrence error about ring-mqtt HOT 5 CLOSED

All of this is basically correct, it's the state for each sensor and that output is expected. What's not expected is exiting unless you canceled the script. Can you run the script with full debug and see if there are any obvious errors? Also, what version of nodeJS are you running on?

from ring-mqtt.

It looks like there's probably a syntax/scoping issue with the error handling code when the mqtt connection fails. I found an authentication error in my mqtt broker's logs, and noticed I had my password wrong. So that was the root cause of the error, and when I corrected that it started working. So I'm good now, but there's probably an issue in the code that is preventing the script from properly outputting the error as intended. Thanks for the great project!

from ring-mqtt.

Ok, I'll test this scenario more stringently and dig up the error. I definitely saw that the error was not getting reported but obviously that didn't cause the exit. I've actually tested failure scenarios a good bit but maybe missed the MQTT fails to connect on startup case.

Thanks for the report!

from ring-mqtt.

I found the error, it was silly! Just missing the "error" in the function parameter. I had tested with the MQTT broker not running/reachable, but I had not tested a scenario where the broker was connected, but not authorized to send data.

Once I added the error parameter to the function it now generates a nice "Not authorized" message (at least if you have debug enabled) and, instead of exiting, it just keeps trying to connect every second like it's supposed to. I'll push an update to the dev branch to fix this, so that when I push that to the master branch later next week it gets fixed. Thanks again for reporting it!

from ring-mqtt.

Commited the 0.8.0 version to the master branch which should close this issue.

from ring-mqtt.