Koenkk
Vimar 14595 he associates but does not communicate
What happened?
I can pair the device correctly, but as soon as I try to give any command the error appears: z2m: Device '0xf4ce3672c27f5f76' has no endpoint 'undefined'
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
Trying to turn the light on and off or adjusting the brightness I noticed instead that on another dimmer with older firmware, it works fine.
Zigbee2MQTT version
2.1.3 commit: unknown
Adapter firmware version
7.4.4 [GA]
Adapter
ITEAD Sonoff ZBDongle-E (ZigBee 3.0 USB Dongle Plus) – v2
Setup
Add-on on Home Assistant Os
Debug log
Same issue for me after updating FW to 1.1.5. I tried to pair to Deconz and it works.
My adapter is ITEAD Sonoff ZBDongle-P
I could use this workaround, but I'd prefer to use z2m. Luckily I have two zigbee antennas.
Same issue for me after updating FW to 1.1.5. I tried to pair to Deconz and it works.
My adapter is ITEAD Sonoff ZBDongle-P
I could use this workaround, but I'd prefer to use z2m. Luckily I have two zigbee antennas.
Same for me. I'm using HUE bridge and Z2M. I would avoid to have the 3rd network :-)
Me neither. I hope it gets fixed soon.
Il Lun 10 Mar 2025, 15:51 LeoeLeoeL @.***> ha scritto:
I could use this workaround, but I'd prefer to use z2m. Luckily I have two zigbee antennas.
Same for me. I'm using HUE bridge and Z2M. I would avoid to have the 3rd network :-)
— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/26676#issuecomment-2710864481, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQD2RQKCCNVL6V6UUI73QJT2TWRGVAVCNFSM6AAAAABYUUGSD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQHA3DINBYGE . You are receiving this because you authored the thread.Message ID: @.***> [image: LeoeLeoeL]LeoeLeoeL left a comment (Koenkk/zigbee2mqtt#26676) https://github.com/Koenkk/zigbee2mqtt/issues/26676#issuecomment-2710864481
I could use this workaround, but I'd prefer to use z2m. Luckily I have two zigbee antennas.
Same for me. I'm using HUE bridge and Z2M. I would avoid to have the 3rd network :-)
— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/26676#issuecomment-2710864481, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQD2RQKCCNVL6V6UUI73QJT2TWRGVAVCNFSM6AAAAABYUUGSD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJQHA3DINBYGE . You are receiving this because you authored the thread.Message ID: @.***>
Have you tried this:
- remove the device from the network (do NOT force!)
- stop Z2M
- start Z2M
- pair the device
If it still doesn't work after this, post a screenshot of the Clusters page in frontend for that device.
The device is unable to be removed without the FORCE option. I stopped and started Z2M several times but with no improvement.
The deconz version:
The device is unable to be removed without the FORCE option. I stopped and started Z2M several times but with no improvement.
The deconz version:
The clusters are the same as yours. The only difference is that I was able to dissociate. But after pairing, the issue persists.
For info: I binded an Ikea E1743 to this device and I can switch on/off and dim the light using that.
I didn't find thw fiz in the changelog https://gist.github.com/Koenkk/bfd4c3d1725a2cccacc11d6ba51008ba#new-supported-devices Possible? Tons of New Supported Devices but what about the New UNSupported Devices?
I have one more info. If i switch on/off, using the physical buttons, the state is regularly update; I can see that in Home Assistant
Infact I can read the state and current level in dev console.
Only commands via Z2M don't work.
Is this the case to close this page and open a new one in order to have visibility? I think @Nerivec forgot us. :-)
Is this the case to close this page and open a new one in order to have visibility?
That will only annoy maintainers...
I don't have that device, and Vimar in general appears to have troubles, someone with Vimar devices would have to sniff a network and implement the necessary changes in Z2M...
Can you help me to understand?
Here https://github.com/Koenkk/zigbee-herdsman-converters/commit/3a10293dcd0563345b33849b3a45889312af0c3e there is what Koenkk added in Vimar.ts { zigbeeModel: ['DimmerSwitch_v1.0'], model: '14595.0', vendor: 'Vimar', description: 'IoT connected dimmer mechanism 220-240V', extend: extend.light_onoff_brightness({noConfigure: true, disablePowerOnBehavior: true}), endpoint: (device) => { return {default: 11}; }, configure: async (device, coordinatorEndpoint, logger) => { await extend.light_onoff_brightness().configure(device, coordinatorEndpoint, logger); const endpoint = device.getEndpoint(11); await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff', 'genLevelCtrl']); await reporting.onOff(endpoint); await reporting.brightness(endpoint); }, },
This is what I have in Vimar.js { zigbeeModel: ["DimmerSwitch_v1.0"], model: "14595.0", vendor: "Vimar", description: "IoT connected dimmer mechanism 220-240V", extend: [m.light({ configureReporting: true, powerOnBehavior: false })], endpoint: (device) => { return { default: 11 }; }, },
Is it normal or something is missing?
https://github.com/Koenkk/zigbee2mqtt/issues/18323 @giovannismart @Koenkk Can you help us to make this device operative again? Tks
Could you:
- Force remove the device through the z2m frontend
- Restart z2m
- Provide the debug log of: start z2m, pair the device and try to control it (this fails right?)
See this on how to enable debug logging.
Could you:
- Force remove the device through the z2m frontend
- Restart z2m
- Provide the debug log of: start z2m, pair the device and try to control it (this fails right?)
See this on how to enable debug logging.
Does it work if you force remove, put the attached file in [root of Z2M]/external_converters/ , restart Z2M and join again??
(rename it to VIMAR_dimmer.js without the .txt extension)
It seems to work. :-) Brightness doesn't go below 63. Is it a Vimar lowest brightness available for this dimmer?
It seems to work. :-) Brightness doesn't go below 63. Is it a Vimar lowest brightness available for this dimmer?
I'll try it too as soon as I can. You have to adjust the minimum brightness by performing combinations with the physical buttons. It's all written in the manual.
I re-paired again, configured TE and then the lowest possible brightness and now is OK.
For info, if you configure the colour of the LED and its behaviour (when OFF and ON) while the device has the BT firmware then the setting remains later when you flash again zigbee firmware. :-) This thing doesn't work for switches. :-(
If you confirm it works (I don't have a dimmer) I'll write a PR to change the converter, evidently Vimar changed the endpoint of the dimmer with the last firmware, that's why it didn't work anymore
Se mi confermi che funziona (non ho un dimmer) ti scrivo una richiesta di modifica del convertitore, evidentemente la Vimar ha cambiato l'endpoint del dimmer con l'ultimo firmware, ecco perché non funzionava più
If I can, I'll try tomorrow too.
ON/OFF and brightness slider work. On the other hand, using the physical buttons Z2M reacts slowly at the changement. I don't know if the configurations in Reporting window should be tuned a little bit.
Does it work if you force remove, put the attached file in [root of Z2M]/external_converters/ , restart Z2M and join again??
(rename it to VIMAR_dimmer.js without the .txt extension)
@saveriol I can confirm, having the same issue, that following your procedure the dimmer functions normally, communicating both ways without fault.
Tks @saveriol.
A question. When will be the next release of Z2M, do I have to delete the external converter of Vimar before the update?
@saveriol, I found another problem, when I perform this action:
action: light.turn_on data: brightness_pct: 100 target: entity_id: light.luce_sala_da_pranzo
If I set the brightness to the current one (in this case 100%) the light remains off.
I am forced to give two separate commands. One for the ignition and one for the regulation.