Missing device configuration: Oomi Color Strip

zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript

https://zwave-js.github.io/node-zwave-js/

MIT License

741 stars 594 forks source link

Missing device configuration: Oomi Color Strip #6037

Closed polskikrol closed 1 year ago

polskikrol commented 1 year ago

Checklist

[X] It is not in the configuration DB
[X] It was not merged recently or has a pending PR

Which device is missing?

Oomi Color Strip

Manufacturer ID

N/A

Product Type

N/A

Product ID

N/A

Firmware Version

No response

Is the device listed on the Z-Wave Alliance website?

https://products.z-wavealliance.org/products/2362?selectedFrequencyId=-1

Do you have a manual?

Attaching logs for the interview for Node 20. zwave-js-ui-store.zip

Also, here is the manual. Oomi ColorStrip manual - 2.pdf

This is a re badge of the Aeotec LED Strip... https://products.z-wavealliance.org/products/2498?selectedFrequencyId=-1. According to manufacturer support, it can be flashed with the EXE firmware to re badge as Aeotec. Firmware 1.02 is available for this.

AlCalzone commented 1 year ago

@zwave-js-bot import config 2362 from zwa

zwave-js-bot commented 1 year ago

🔨 I created a PR at #6039 - check it out! Usually, I'm going to need some help from a human to make sure the configuration matches the style guide.

If anyone feels compelled to help out, please follow these steps:

Fork this repository if you haven't already. If you have, synchronize your fork so you get a copy of the new branch.
Make the necessary changes in the branch import-config-1689774556 in your fork
Create a pull request with your branch import-config-1689774556 as the source and our branch import-config-1689774556 as the target.

Thanks!

zwave-js-assistant[bot] commented 1 year ago

Because of the large amount of Z-Wave devices, we cannot write all configuration files ourselves. Help from the community is required, so we can focus our time on improving Z-Wave JS itself. 🙏🏻

This issue has been labeled "Help wanted", meaning we kindly ask anyone who wants to help out for support. Here are a few resources to get you started - don't hesitate to ask if you are having problems:

We may get around to doing it ourselves at some point, but community support will speed up this process immensely.

Thanks!

AlCalzone commented 1 year ago

Attaching logs for the interview for Node 20. zwave-js-ui-store.zip

Can you try again please? Looks like the interview didn't succeed because some strange route management was going on and the stick was unresponsive.

Ideally clear the entire logfile first, so there aren't 50k unrelated lines in there.

polskikrol commented 1 year ago

Strange. I 'healed' the node, and same issue. I also went under log, and removed the current log files. I then do a test, and both log files show 22 bytes or so. However, when I select both files and download, it is a few MB. So maybe I dont know how to clear the logs properly or something? But figured if I trashed the file, it would write a new one and not be loaded with info.

AlCalzone commented 1 year ago

log files show 22 bytes or so

zwavejs_current.log is a symlink, that doesn't show the correct file size. Or maybe Z-UI doesn't update the size correctly. Depending on how you run Z-UI, you can just shut down, delete the log files from your store directory and boot it up again.

polskikrol commented 1 year ago

I ended up using my Z-Stick 5 with the PC controller firmware updater to change the firmware to ZW121 v1.3. As this was a rebadge of the Aeon (Aeotec) LED Strip. Then I unpaired it from Z-Stick 5, repaired it with Vera Plus, and relearned the network via Z-Stick 7 and HA. Re-interviewed and it comes up fine now.