🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

I use the dock image.

Docker log reads:

ipcam2mqtt_1           | 2019-07-25T02:39:56.952916898Z 2019-07-25 02:39:56.952 <info>  Motion detected for ftpuser
ipcam2mqtt_1           | 2019-07-25T02:40:07.974386526Z 2019-07-25 02:40:07.974 <info>  Motion detected for ftpuser
ipcam2mqtt_1           | 2019-07-25T02:40:18.991486184Z 2019-07-25 02:40:18.991 <info>  Motion detected for ftpuser
ipcam2mqtt_1           | 2019-07-25T03:37:16.890100437Z 2019-07-25 03:37:16.889 <info>  Motion detected for ftpuser
ipcam2mqtt_1           | 2019-07-25T03:37:27.877646251Z 2019-07-25 03:37:27.877 <info>  Motion detected for ftpuser
ipcam2mqtt_1           | 2019-07-25T03:37:49.056456207Z ERROR: <::ffff:192.168.3.78> Error sending file list, reading directory: Error: Not implemented
ipcam2mqtt_1           | 2019-07-25T03:37:59.882173049Z ERROR: <::ffff:192.168.3.78> Error sending file list, reading directory: Error: Not implemented
ipcam2mqtt_1           | 2019-07-25T03:38:10.819778096Z ERROR: <::ffff:192.168.3.78> Error sending file list, reading directory: Error: Not implemented
ipcam2mqtt_1           | 2019-07-25T03:38:21.873036788Z ERROR: <::ffff:192.168.3.78> Error sending file list, reading directory: Error: Not implemented
ipcam2mqtt_1           | 2019-07-25T06:53:03.740454131Z ERROR: <::ffff:192.168.3.78> Error sending file list, reading directory: Error: Not implemented
ipcam2mqtt_1           | 2019-07-25T06:53:14.713013235Z ERROR: <::ffff:192.168.3.78> Error sending file list, reading directory: Error: Not implemented

It would be really nice to save the images and only send the url of the image to mqtt. That would take the load of mqtt. Also very nice to keep records.

At this moment every password is accepted, I should maybe require at least some sort off password. This function could be used.

Hi, thanks for this great project, however I'm facing some problem.

Every time after restarting ipcam2mqtt, the 1st ftp upload will always trigger the "Motion detected" message instantly, but then there will be 5-20 seconds delay between the time when camera uploaded image and the ipcam2matt "motion detected" message.

And the -v debug or --verbosity debug parameter doesn't work, so I can't get more debug info

My Reolink cameras insist on creating directories for snapshots. When I do a test from the camera (even when I tell the camera not to use a directory), I get the following from ipcam2mqtt:

ERROR: <::ffff:192.168.1.201> CWD //camera_test20190222080904: Error: ENOENT: no such file or directory, stat '/srv/homeassistant/camera_test20190222080904'
ERROR: <::ffff:192.168.1.201> CWD camera_test20190222080904: Error: ENOENT: no such file or directory, stat '/srv/homeassistant/camera_test20190222080904'
ERROR: <::ffff:192.168.1.201> MKD camera_test20190222080904: Error: Not implemented

Is there an easy fix for this on the ipcam2mqtt side of things? I don't even care to save the images, I just want to push them via MQTT to Home Assistant.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀