Hi,
I added a Shelly Qubino Shutter to my network, and I see a duplication in the entities for the device.
Any ideas or suggestions?
Should I manually remove the duplicated entities?
1 Like
Thank you, I tried but it doesn’t work.
If this is your device ( QNSH-001P10EU )
According to this schematics there are two independent measuring circuits (A1, A2) and then actually everything is ok like that 
not sure about that, I only try to interpret, what I found with google…
thank you, understood
I found the following discussion that sounds similar
I will research more
Sorry but that discussion has nothing to do with your device.
Can you post the Device diagnostic file so we can see how it’s configured. https://www.home-assistant.io/integrations/zwave_js/#network-devices
“home_assistant”: {
“installation_type”: “Home Assistant OS”,
“version”: “2024.10.1”,
“dev”: false,
“hassio”: true,
“virtualenv”: false,
“python_version”: “3.12.4”,
“docker”: true,
“arch”: “aarch64”,
“timezone”: “Europe/Rome”,
“os_name”: “Linux”,
“os_version”: “6.6.31-haos-raspi”,
“supervisor”: “2024.09.1”,
“host_os”: “Home Assistant OS 13.1”,
“docker_version”: “26.1.4”,
“chassis”: “embedded”,
“run_as_root”: true
},
“integration_manifest”: {
“domain”: “zwave_js”,
“name”: “Z-Wave”,
“codeowners”: [
“home-assistant/z-wave”
],
“config_flow”: true,
“dependencies”: [
“http”,
“repairs”,
“usb”,
“websocket_api”
],
“documentation”: “Z-Wave - Home Assistant”,
“integration_type”: “hub”,
“iot_class”: “local_push”,
“loggers”: [
“zwave_js_server”
],
“quality_scale”: “platinum”,
“requirements”: [
“pyserial==3.5”,
“zwave-js-server-python==0.58.1”
],
“usb”: [
{
“vid”: “0658”,
“pid”: “0200”,
“known_devices”: [
“Aeotec Z-Stick Gen5+”,
“Z-WaveMe UZB”
]
},
{
“vid”: “10C4”,
“pid”: “8A2A”,
“description”: “z-wave”,
“known_devices”: [
“Nortek HUSBZB-1”
]
}
],
“zeroconf”: [
“_zwave-js-server._tcp.local.”
],
“is_built_in”: true
},
“setup_times”: {
“null”: {
“setup”: 0.009194678999989492
},
“01J973T9Z0C0P4198SZGS7029E”: {
“config_entry_setup”: 0.029689627999999857,
“config_entry_platform_setup”: 0.0034922709999989365
}
},
Can you post the complete file to a pastebin? Something like dpaste.org. Sorry, but the multiple posts and unformatted code are too hard to read.
Your device has special code implemented in HA to configure it, but it looks like the discovery went haywire. I assume there was some problem when you initially included the device, some hints being the name of entities as “node_2” instead of including the product name, and you have duplicate entities for config parameter 71.
Based on your current configuration, parameter 71 is set to 0, so the second endpoint is non-functional and would usually be hidden by default. cover.node_2 should be the working cover entity, and you can disable cover.node_2_2 is it should be non-functional. Re-interview does not help here because the integration will not disable any already created entities. If you don’t have any helpers or automations dependent on this device, you could try manually deleting it (same menu as where you download diagnostic), then reload the integration (or restart HA), and see if it will discover it properly.
1 Like
I tried, but no luck. I can’t remove the device as it is still present in the network.
I removed and re-installed the integration, and I rebooted the HA, but node_2 still remains.
I read the documentation. Do you think this is something that can be managed by the Z-Wave JS integration? I mean, if parameter 71 is set to 0, will it filter out node_2?
Could it be related to the fact that the device has two modes: shutter and venetian?
I have a couple of them and I tried with another one, same result
Anything new to share on this issue?