search

zwave-js / node-zwave-js

Z-Wave driver written entirely in JavaScript/TypeScript
https://zwave-js.github.io/node-zwave-js/
MIT License
739 stars 588 forks source link

Everspring - EH403 - Cannot change default configuration #6829

Closed AlCalzone closed 1 month ago

AlCalzone commented 2 months ago

Discussed in https://github.com/zwave-js/node-zwave-js/discussions/6828

Originally posted by **@s8109csa** May 8, 2024 ### Checklist - [X] I have read and followed the above instructions - [X] I have checked the [troubleshooting section](https://zwave-js.github.io/node-zwave-js/#/troubleshooting/index) and my problem is **not** described there. - [X] I have read the [changelog](https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md) and my problem was **not** mentioned there or the fix **did not work**. ### Describe the issue What is happening? I cannot change default configuration on Everspring EH403. I have 3 of them, same issue on all. There are 3 parameters and for me the important would be the auto report lux value. I wanted to change 0 to 3 and when I clicked somewhere else in the Home Assisstant, there was only an error message: Error happened. Other Z-Wave devices are working as expected. What did you expect to happen instead? Update parameters Steps to reproduce the behavior: 1. Go to Devices -> Z-Wave -> Everspring EH403 -> Settings -> Edit parameter 3 -> click out from the cell. 2. See error Anything else we should know? The devices are securely connected to Aeotec USB Z-Stick 7 - again, I can edit other devices. FW is default, I don't think there was ever a firmware update on these flood lights. ### Software versions Driver (node-zwave-js): ... Z-Wave JS UI: ... Home Assistant Z-Wave Integration: ... Home Assistant Z-Wave JS Addon: ...newest but it was always the case ioBroker.zwave2 Adapter: ... If you are using something non-standard, tell us here: ... ### Device information Manufacturer: EverSpring Model name: EH-403 Node ID: 11 ### Checklist - [X] I [made sure](https://zwave-js.github.io/node-zwave-js/#/troubleshooting/index?id=rule-1-use-the-driver-log-luke) to provide a **driver log** on level **debug**. - [X] The log includes a re-interview of the problematic device _(if applicable)_. - [X] The log includes the problematic interaction with the device _(if applicable)_. - [X] I provided the node ID of the problematic device _(if applicable)_. ### Upload Logfile [home-assistant_zwave_js_2024-05-08T15-09-55.901Z.log](https://github.com/zwave-js/node-zwave-js/files/15250841/home-assistant_zwave_js_2024-05-08T15-09-55.901Z.log)
AlCalzone commented 2 months ago

Fix: Disable Supervision CC for this device.

s8109csa commented 2 months ago

Hi,

I see you created an issue but what is happening now? Shall I wait for a new revision of the node-zwave-js? Can you explain what is disable supervision cc for this device?

Thank you Peter

AlCalzone @.***> ezt írta (időpont: 2024. máj. 8., Sze, 19:58):

Fix: Disable Supervision CC for this device.

— Reply to this email directly, view it on GitHub https://github.com/zwave-js/node-zwave-js/issues/6829#issuecomment-2101113436, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARW5BUF4DBSQEM4IVL6CQ3DZBJRT3AVCNFSM6AAAAABHNNPEUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRGEYTGNBTGY . You are receiving this because you were mentioned.Message ID: @.***>

AlCalzone commented 1 month ago

Yeah that's something I have to do in Z-Wave JS.

AlCalzone commented 1 month ago

@zwave-js-bot add compat flag to 0x0060:0x0012:0x0001

"commandClasses": {
    "remove": {
        // The device does not support Supervision correctly
        "Supervision": {
            "endpoints": "*"
        },
    }
}
zwave-js-bot commented 1 month ago

🔨 I created a PR at #6847 - check it out!

s8109csa commented 3 weeks ago

Hi, thank you for your efforts, I just want to inform you that I have just installed 0.6.0 of Z-Wave JS and tested Everspring EH-403 parameter update, it is still doesn't work, it just says error. Logs shows nothing at all, no communication seen in the JS log file.

Can it be that it is S2 connected?

Thanks Peter

AlCalzone @.***> ezt írta (időpont: 2024. máj. 14., K, 9:12):

Closed #6829 https://github.com/zwave-js/node-zwave-js/issues/6829 as completed via #6847 https://github.com/zwave-js/node-zwave-js/pull/6847.

— Reply to this email directly, view it on GitHub https://github.com/zwave-js/node-zwave-js/issues/6829#event-12797127383, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARW5BUGG24PFSTI3O363PCTZCG2M7AVCNFSM6AAAAABHNNPEUSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSG44TOMJSG4ZTQMY . You are receiving this because you were mentioned.Message ID: @.***>

AlCalzone commented 3 weeks ago

Did you re-interview the device after updating?

s8109csa commented 3 weeks ago

Great Support, that solved it, didn't know I have to do that.

Thank you Peter

AlCalzone @.***> ezt írta (időpont: 2024. jún. 18., K, 19:31):

Did you re-interview the device after updating?

— Reply to this email directly, view it on GitHub https://github.com/zwave-js/node-zwave-js/issues/6829#issuecomment-2176622406, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARW5BUEIZ4IPGEKQDRVBY7DZIBVGLAVCNFSM6AAAAABHNNPEUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWGYZDENBQGY . You are receiving this because you were mentioned.Message ID: @.***>