Replies: 2 comments 2 replies
-
It has probably been that way in the source we imported from. I don't see a need to keep the limitation, unless there's a different hardware revision with the same device identifiers. |
Beta Was this translation helpful? Give feedback.
-
I copied the json file from the docker volume using the following command : Then I modified the firmware version section from and copied back the file into docker : After restarting the docker container, my 4 Popp Mold detectors were correctly recognized, but lacking the "Configuration" interface. So I think we can definitely remove the firmware range limitation from the file for future revisions of Zwave-JS. |
Beta Was this translation helpful? Give feedback.
-
Hello,
The Popp 701202 Mold Detector description file specifies the firmware v1.0 only.
https://github.com/zwave-js/node-zwave-js/blob/fee80cf880c4620f1424fb7c38c7322fcc88ac32/packages/config/config/devices/0x0154/pope701202_1.0-1.0.json
Why is it limited ? I own 4 of them with fw v1.2, hence they aren't recognized by my ZWave-JS, so it's difficult to configure it.
Could we remove the limitation ? should we make some tests first ? I'm running zwavejs2mqtt 3.5.0 and zwave-js 7.2.4 under docker, may I change the file locally to test ?
Thanks for your help
Beta Was this translation helpful? Give feedback.
All reactions