Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]AEON Labs / MultiSensor 6 firmware update not working #3066

Closed
4 tasks done
mschiessl opened this issue Jul 21, 2021 · 2 comments · Fixed by #3068
Closed
4 tasks done

[bug]AEON Labs / MultiSensor 6 firmware update not working #3066

mschiessl opened this issue Jul 21, 2021 · 2 comments · Fixed by #3068
Assignees
Labels
bug Something isn't working

Comments

@mschiessl
Copy link

Checklist:

  • I am not using HomeAssistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog problem was not mentioned there.

Build/Run method

  • Docker

zwavejs2mqtt: 5.4.0
zwave-js: 8.0.3

Describe the bug

When trying to send a firmware update towards AEON Labs / MultiSensor 6 i am getting the following error messages:

First attempt

Failed to start the update: Firmware target #0 not found on this node! beginFirmwareUpdate undefined

on other attempts i am getting the following error

Failed to start the update: A firmware upgrade is already in progress! beginFirmwareUpdate undefined

Trying to abort the update i am receiving this but without any change on the second err message

Success zwave api call abortFirmwareUpdate undefined

To Reproduce

  • Go to the Aeotec website and fetch the latest EU firmware (for my use case)
  • extract the received rar file
  • Go to the webinterface, pick the device ID (tested on several Multisensors - so lets use feat: support start stop commands for multilevel switch zwave-js-ui#40 for now)
  • Click the advanced button within the device details subpage
  • select Firmware update
  • set Target: "0" (to hit the chip)
  • Select the extracted .exe file from the firmware (found that zwave.js is able to extract aeotec firmware from it)
  • click the begin button

See error message on botton & observer log

I waited ~ 1.5 hours for the update to complete without success

Expected behavior

The regarding deviceID is getting the firmwareupdate through (after some time)

@robertsLando robertsLando transferred this issue from zwave-js/zwave-js-ui Jul 21, 2021
@AlCalzone AlCalzone assigned AlCalzone and unassigned robertsLando Jul 21, 2021
@AlCalzone AlCalzone added the bug Something isn't working label Jul 21, 2021
@AlCalzone
Copy link
Member

Thanks, I think I know why this happens. Should be fixed in the next patch.

@mschiessl
Copy link
Author

@AlCalzone - thanks that was a seamlessly quick one :D thanks for the heads up.
Let me know if you want me to run a preflight test with a self built image. Happy to verify upfront a release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants