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

Remove Aeotec ZW175-C #143

Merged
merged 1 commit into from
Sep 25, 2024
Merged

Remove Aeotec ZW175-C #143

merged 1 commit into from
Sep 25, 2024

Conversation

Aeotec-ccheng
Copy link
Contributor

Removed due to forcing users to exclude and include device again.

The firmware change was on the larger side causing the security keys to be wiped. If this gets fixed in the future, then the update will be brought back into the ZWaveJS database.

Removed due to forcing users to exclude and include device again. 

The change in firmware was on the larger side causing the security keys to be wiped. If this gets fixed in the future, then the update will be brought back into the ZWaveJS database.
@AlCalzone AlCalzone changed the title Delete firmwares/aeotec/ZW175-C.json Remove Aeotec ZW175-C Sep 25, 2024
@AlCalzone AlCalzone merged commit d6f7815 into zwave-js:main Sep 25, 2024
4 checks passed
@mmattel
Copy link

mmattel commented Oct 5, 2024

For those who find that PR:

To update the FW manually, you need to follow the guide in:

https://aeotec.freshdesk.com/support/solutions/articles/6000270359-update-smart-switch-7-eu-v1-03-zw175-c- using Simplicity Studio and mandatory deselect all security options on first adding.

When you have finally added the device via SS again post upgrading, you need to remove it AND readd it via zwave-js. Else you will NOT get all device info and config options. Drove me nuts...

@mundschenk-at
Copy link
Contributor

@mmattel No need for Simplicity Studio, you "just" need to factory reset the device after the update and re-include it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants