Vimar Dimmer Smart

andro17 · November 23, 2023, 7:35am

Hi everyone! I purchased a Vimar Smart dimmer, but I can't find a compatible DH that makes it work, what can I do? If I connect it to my echo it works great. I have other Vimar devices (shutters, actuators and switches) and they work very well with DH "generic zigbee..".

kkossev · November 23, 2023, 7:52am

Can you give some more details on Vimar Smart dimmer?
Do you have it paired to Hubitat hub? If yes, please post the device model and manufacturer (as found on the web page 'Device Details' data section.

andro17 · November 23, 2023, 8:16am

thanks for the reply, I was able to easily connect the device to the c-7 hub. I can't make a complete fingerprint, but this is the data:

manufacturer: Vimar
model: DimmerSwitch_v1.0
endpointID: 0B
application: 01
driver: v1.0.1.1123
incluster and autcluster: null

kkossev · November 23, 2023, 8:54am

Does it look like this ?

This seems to be a rather new model, still in a process of integrating into Zigbee2MQTT :

github.com/Koenkk/zigbee2mqtt

Vimar 14595.0

opened 06:56PM - 14 Jul 23 UTC

closed 06:41PM - 23 Nov 23 UTC

giovannismart

new device support

### Link https://www.vimar.com/en/int/catalog/product/index/code/14595.0 ### D…atabase entry "modelZigbee":"DimmerSwitch_v1.0","type":"Router","ieeeAddr":"0xf4ce362762f02e35 ### Comments Hello! I am currently trying to integrate in my HomeAssistant+Zigbee2MQTT setup a Vimar 14595.0 dimmer-switch which, unfortunately, is currently not supported by Zigbee2MQTT as indicated by the 'Unsupported' tag on the Zigbee2MQTT dashboard. More specifically, the module is recognized and it can be added to the Zigbee2MQTT dashboard but I believe that since it lacks a suitable configuration in the .ts file, none of its functionalities are available. Even following the (https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html#_2-adding-your-device) guide provided on the Zigbee2MQTT site, I was not able to configure the dimmer properly. I borrowed the .ts configuration of supported devices with dimmer capabilities like i) 'BTicino' model: 'L4411C/N4411C/NT4411C'; ii) 'Enbrighten' model: '43080',43113','43082'; iii) 'GE' model: '45852GE','45857GE') but it did not help as the dimmer still could not control the lights (not switching on/off nor dimming). Please provide guidance. How do I build the correct configuration for my device? Thank you! ### External converter ```shell const fz = require('zigbee-herdsman-converters/converters/fromZigbee'); const tz = require('zigbee-herdsman-converters/converters/toZigbee'); const exposes = require('zigbee-herdsman-converters/lib/exposes'); const reporting = require('zigbee-herdsman-converters/lib/reporting'); const legacy = require('zigbee-herdsman-converters/lib/legacy'); const extend = require('zigbee-herdsman-converters/lib/extend'); const ota = require('zigbee-herdsman-converters/lib/ota'); const tuya = require('zigbee-herdsman-converters/lib/tuya'); const utils = require('zigbee-herdsman-converters/lib/utils'); const globalStore = require('zigbee-herdsman-converters/lib/store'); const e = exposes.presets; const ea = exposes.access; const definition = { zigbeeModel: ['DimmerSwitch_v1.0'], model: '14595.0', vendor: 'Vimar', description: 'IoT connected dimmer mechanism 220-240V', extend: extend.light_onoff_brightness({noConfigure: true, disableEffect: true}), configure: async (device, coordinatorEndpoint, logger) => { await extend.light_onoff_brightness().configure(device, coordinatorEndpoint, logger); const endpoint = device.getEndpoint(1); await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff', 'genLevelCtrl']); await reporting.onOff(endpoint); await reporting.brightness(endpoint, {min: 1}); }, }; module.exports = definition; ``` ### Supported color modes _No response_ ### Color temperature range _No response_

If you switch the driver manually to the HE inbuil driver named 'Device' and you click on 'Get Info' button, do you see the device fingerprint shown in the live logs?

andro17 · November 23, 2023, 9:31am

unfortunately I don't see the complete fingerprint: "INCOMPLETE - DO NOT SUBMIT THIS - TRY AGAIN"; INclusters and OUTclusters are NULL…

kkossev · November 23, 2023, 9:35am

This is from Markus’s driver …

Please use the HE system driver named ‘Device’

andro17 · November 23, 2023, 10:24am

I set the DH device and this is the result:

kkossev · November 23, 2023, 10:36am

There is something non-standard in this deviece, and the stock driver is throwing an exception ...
You can try to first delete the device (use the red 'REMOVE DEVICE' button at the bottom of the web page), and then pair it again - very close to the HE hub!

But before doing this, can you try this driver ?
[RE-RELEASE][BETA] Tuya Zigbee Dimmer Module (w/ healthStatus)

Enable the 'Advanced Options' and select Profile: "OTHER_OEM_DIMMER"

andro17 · November 23, 2023, 10:49am

just tried it, the tuya driver doesn't work for me..

I have tried to re-pair the device several times but the result is always the same..

I don't think the device is defective because it works easily with the echo hub.

kkossev · November 23, 2023, 11:05am

Let me know if you are willing to spend the time to troubleshoot this device and make it work.
I will need a lot of details ...

The more practical approach is to try to return it and try another one which will hopefully work out of the box in HE.

andro17 · November 23, 2023, 11:21am

ok, it can be done, someone else could benefit from it in the future. I will purchase a new one and will update you when it arrives. do I need to do anything else with this one installed?

kkossev · November 23, 2023, 11:26am

Some more info needed :

Please confirm if you are simply re-pairing the device, or you are completely removing it first, and then pairing it again as a new device?

What is your hub - C-8 or C-7?

I don't think that the device is faulty, IMO there is no need to buy another one (if the same model/manufactuer) - the result may bet he same ..

With the Tuya Dimmer driver:

enable the debug logs
clear the live logs for this device
power the dimmer off for a few seconds and then power it on ( from the mains circuit breaker)
press the dimmer buttons (should be 2 physical buttons?)
send me the debug logs

I need the debug logs sent as a text (not as a picture) - use the select->copy->paste sequence on a PC browser.

Can you do this?

andro17 · November 23, 2023, 11:51am

ok I removed the device again, after which I added it again as a new device. I followed the procedure and this is the result of the logs, at this moment the device turns the connected light on and off:

dev:1772023-11-23 12:49:56.785debugvimar dimmer parse: received raw description: catchall: 0000 0013 00 00 0040 00 969A 00 00 0000 00 00 019A96D0758F6E2136CEF48E

dev:1772023-11-23 12:49:41.007debugvimar dimmer parse: received raw description: catchall: 0000 0013 00 00 0040 00 4E15 00 00 0000 00 00 01154ED0758F6E2136CEF48E

dev:1772023-11-23 12:49:25.255debugvimar dimmer parse: received raw description: catchall: 0000 0013 00 00 0040 00 13C5 00 00 0000 00 00 01C513D0758F6E2136CEF48E

dev:1772023-11-23 12:49:04.035debugvimar dimmer parse: received raw description: catchall: 0000 0013 00 00 0040 00 DDCB 00 00 0000 00 00 01CBDDD0758F6E2136CEF48E

dev:1772023-11-23 12:48:48.234debugvimar dimmer parse: received raw description: catchall: 0000 0013 00 00 0040 00 871A 00 00 0000 00 00 011A87D0758F6E2136CEF48E

dev:1772023-11-23 12:48:37.429debugvimar dimmer parse: received raw description: catchall: 0000 0013 00 00 0040 00 DD36 00 00 0000 00 00 0136DDD0758F6E2136CEF48E

dev:372023-11-23 12:48:12.694debugdescription is read attr - raw: A78D0A00060800001000, dni: A78D, endpoint: 0A, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

dev:382023-11-23 12:48:12.651debugdescription is read attr - raw: 6A3D0A00060800001000, dni: 6A3D, endpoint: 0A, cluster: 0006, size: 08, attrId: 0000, encoding: 10, command: 0A, value: 00

kkossev · November 23, 2023, 12:17pm

This repeating log is a ZDO 'Device Announcement' message, which usually means that this is a Zigbee connectivity problems. These can not be fixed on a driver level, but only on Hubitat platform level.

It constantly changes it's NWK - DD36 , 871A , DDCB ...

So this is just another Zigbee 3.0 device that Hubitat hub has a problem with. It matches the pattern in this thread, registered nearly one year ago.

Hopefully, Hubitat engineers will find the problem and fix it.