Forum Announcements and News Firmware Upgrade 07/10/2020 (IPC_51516M) Firmware "Upgrade" Still Has Bugs

This topic contains 8 replies, has 6 voices, and was last updated by  Cynthia 3 months, 1 week ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #1058224

    dbchase69
    Participant

    The newly released firmware that replaced the previous June update that borked the RLC-410-5MP and the RLC-420-5MP did fix the broken FTP upload but is still having at least one glaring issue:

    The inability to turn off Motion Detection.

    You uncheck the box for motion detection & click Save, then click to any other area of the Settings, go back to motion detection, and the box has magically been enabled again. The save button is clearly not saving the preference, and this was a bug that was present in the June firmware as well. I guess it got missed.

    A temporary workaround is to clear the motion zone.

    My RLC-420-5MP for some reason refuses to accept the new *.pak file at all, and won't update at all, but that seems just as well as the firmware still seems to have failed QC again. Restored all cameras back to the March firmware.

    #1058238

    Peter
    Participant

    I'm having similar issues with the latest firmware. I don't have the March version of the firmware. Can you point me to the location of the March version.

    #1058246

    dbchase69
    Participant

    March 14/2020 Firmware for the 5MP cameras:

    RLC-410-5MP here

    RLC-420-5MP here

    The March firmware functions as expected. This is only for the 5 megapixel versions.

    #1058259

    Peter
    Participant

    Thanks for the links. Appreciate the help. 🙂

    #1062918

    azicemachine
    Participant

    Spent 3 days jerking around with this motion issue. Put in a ticket to Reolink with detailed information and they wanted more configuration data to troubleshoot. The motion issue has only affected my RLC-420 5MP domes so I rolled back firmware and imported old configurations.
    I also was unable to import a .pak configuration file with the new firmware. The new config exports to a .tgz file and won't import the previous .pak files. That was an unpleasant surprise that Reolink should have warned us about.

    #1064581

    Cynthia
    Keymaster

    We apologize for the trouble caused you.
    We will improve our service in the future.
    If you have any requests and issues, please feel free to contact our support and we will try our best to help you.
    Wish a good day/

    #1161759

    Germo Görtz
    Participant

    what is the preferred way for reolink to get bug reports?

    – does a dedicated public bug tracker for bugs and / or features exist?
    – should we report bugs here in the forum?
    – Should I open a new common support ticket for several bugs per firmware?
    – Should I open a support ticket per bug?

    A public tracker could avoid reporting known issues.
    A public ”feature request collecting and voting system” allows to quantity feedback.

    #1161795

    Jose
    Participant

    what is the preferred way for reolink to get bug reports?
    A public tracker could avoid reporting known issues.
    A public "feature request collecting and voting system" allows to quantity feedback.

    I strongly support that idea. I have reported some bugs and improvement suggestions directly to Support and, beyond the usual and kind word of thanks, there is no real way to know whether or not there are other interested users and the ultimate fate of the proposals.

    #1161813

    Cynthia
    Keymaster

    We are quite sorry for the inconvenience. It will be better if you open a ticket to inform our technical support team of the bugs. It will be more convenient to help you. We will forward your feedback to our engineers to check the bugs. Thanks for figuring it out, which helps us to improve our products in the future. Have a nice day.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.