Dear @Mariano_Colmenarejo ,
I hope you doing well. Just a reminder, when you’ll have the opportunity and time,
Please try to add ‘two gang’ window treatment.
I’m here to help and test whenever you want. Take your time, there is no rush
Please add also:
modelID: ‘TS130F’
manufacturerName: ‘_TZ3000_kmsbwdol’
Which is the same
Will this edge driver work for the Yoolax motorshades, it has the Z425 Zigbee motor. I see on the github page you have the source for it.
**Disregard, I found the invite in another thread
Where do I access the channel for this driver? I do not see a link?
Dear @Mariano_Colmenarejo,
I hope it is a good time to ask again, But can you please start thinking again on :
No rush, but I remember you said something on starting working on that in October…
Hi @dotan_shai
I don’t remember saying anything about October, I already told you that it required many hours of work and I don’t have time to do it.
In October and November I have many more things to do, it is mushroom season and I enjoy outdoor activities.
I just needed that now that I’m retired, others set schedules for me.
Ha ha looks very tasty, enjoy your meal…
Just wanted to inform that @w35l3y Default Clusters driver can deal with this module. BUT, without the option to calibrate the % , as in your single gang shutter driver. In order to calibrate the % a Tuya Hub is required on which I want to prevent. I still hope you’ll find few hours to develop this as well.
Hello @Mariano_Colmenarejo
This is my first experience with Moes MS-108ZR blind switch. After quick calibration the blind run is not too repetitive. Reading all this post, I still do not know if it can be accurate calibrated with your edge driver or not.
If it is possible, could you please explain the accurate calibration steps.
Thanks in advance.
Hi @Bernfp
I do not use any device of this type and I do not know how the calibration is actually done on the device.
Maybe another user like @dotan_shai can help you with this.
I’m not using this modules just helped others.
Quick Calibration - simply enter in to time in seconds to move from 0%, to 100%. No calibration for 100% to 0%
Accurate Calibration - Should automatically move your shutter to 0% and 100% , @Mariano_Colmenarejo driver should display the time it took your shutter to move.
Hi @Mariano_Colmenarejo
Hi @dotan_shai
Thanks a lot for your dedication to help others like me in to this matter.
@dotan_shai , Quick calibration is done following your instructions, but shutter movements up and down are not repetitive. I mean it moves several cm up or down more than other times.
That is why I’d like to preform accurate calibration, but when I select this option in settings menu, nothing happens. It doesn’t move automatically the shutter. Only the text calibration started in the main screen.
Some modules support accurate calibration and some don’t this is why we add the quick calibration. You can try send a CLI log to @Mariano_Colmenarejo for review while doing accurate calibration. You can also try to calibrate via Tuya ZigBee hub and then re-pair to ST. But I suspect this won’t help since this modules are sometimes don’t perform the calibration accurately. My advise is try another module and see if this work, if not consider to use Fibaro Roller Shutter module which a bit more expensive but have no issues when calibration is required.
Hi @Mariano_Colmenarejo, according @dotan_shai recommendation, find below log while Accurate calibration, started at 23:00 and finished manually (because it doesn’t finish alone) at 23:05
┌────┬──────────────────────────────────────┬────────────────────────────────────────┐
│ # │ Driver Id │ Name │
├────┼──────────────────────────────────────┼────────────────────────────────────────┤
│ 1 │ 73fc25c9-bc64-4744-a354-500dc1795cd0 │ Aeotec Nano Dimmer │
│ 2 │ c856a3fd-69ee-4478-a224-d7279b6d978f │ bose │
│ 3 │ 4eb5b19a-7bbc-452f-859b-c6d7d857b2da │ Harman Luxury │
│ 4 │ 9d00eaef-fd7f-4719-9af3-1392a23a0592 │ Hue Motion Sensor │
│ 5 │ 7beb8bc2-8dfa-45c2-8fdb-7373d4597b12 │ JBL │
│ 6 │ fba178cd-203e-4b7c-bfa0-d4f07197b527 │ Matter Sensor │
│ 7 │ 9894127d-bc7a-419a-9382-4b41827d6a97 │ Onkyo Receiver │
│ 8 │ a3f99eee-5802-4edd-888d-1fac080bc02e │ ONVIF Video Camera V1.3 │
│ 9 │ cd898d81-6c27-4d27-a529-dfadc8caae5a │ Philips Hue │
│ 10 │ dbe192cb-f6a1-4369-a843-d1c42e5c91ba │ SamsungAudio │
│ 11 │ c21a6c77-872c-474e-be5b-5f6f11a240ef │ Sonos │
│ 12 │ 0fd9a9a4-8863-4a83-97a7-5a288ff0f5a6 │ Virtual Devices V2 │
│ 13 │ 054cf51f-0171-4d25-acd2-9dc739cce921 │ Virtual Things Edge Driver [YG] │
│ 14 │ d9c3f8b8-c3c3-4b77-9ddd-01d08102c84b │ Wemo │
│ 15 │ 7ca45ba9-7cfe-4547-b752-fe41a0efb848 │ Z-Wave Device Config Mc │
│ 16 │ 7f7ffe18-2622-4f50-8783-a0cf2ea3dd03 │ Z-Wave Keypad │
│ 17 │ d58d8432-ea22-4d38-8300-2bd75fdf1358 │ Z-Wave Sensor │
│ 18 │ 2cbf55e3-dbc2-48a2-8be5-4c3ce756b692 │ Z-Wave Switch │
│ 19 │ 17c05c19-f008-42e2-aa12-f12f1aae5612 │ Z-Wave Switch and Child Mc │
│ 20 │ 8a5a5586-aa12-4cbb-b7ed-fa3ad735df0d │ Zigbee Aqara Water Leak Sensor Mc │
│ 21 │ 3fb97b6c-f481-441b-a14e-f270d738764e │ Zigbee Button │
│ 22 │ 78da112c-9b9c-4359-b1b7-202a8a040157 │ Zigbee Button Remote Driver [YG] 1.3.8 │
│ 23 │ a89371c4-8765-404b-9de9-e9882cc48bd8 │ Zigbee Dimmer Driver [YG] │
│ 24 │ c6008edc-9630-465a-a4ea-0c6432c677fc │ Zigbee Multi Gang Switch [YG] v2.1.6 │
│ 25 │ e9bfd289-1d51-499e-8c64-d564d1868ad2 │ Zigbee Multi Switch and Child Mc │
│ 26 │ 5ab64dc7-5d08-44a4-9806-5a5b823a18d2 │ Zigbee Sensors Edge Driver [YG] 1.8.16 │
│ 27 │ a2f7ec78-14c8-492d-9965-7544b0fc3b68 │ Zigbee Smoke/CO Detector Mc │
│ 28 │ f2e891c6-00cc-446c-9192-8ebda63d9898 │ Zigbee Switch │
│ 29 │ bc53adfe-d18f-4ea4-9610-6aade6696b7a │ Zigbee Switch Mc │
│ 30 │ 7fee6e41-26cc-49ef-b1f4-b30a43e02fe6 │ Zigbee Switch Power Mc │
│ 31 │ 3724840a-2b1d-4f6b-9683-e8e0155445ee │ Zigbee Thing [YG] v1.0.2 │
│ 32 │ a6994e70-93de-4a76-8b5d-42971a3427c9 │ Zigbee Valve Mc │
│ 33 │ f82dec82-e5fa-487f-8f0f-22c3e4a8bd89 │ Zigbee Water Leak Sensor │
│ 34 │ e7070ea0-2ed9-4802-b7e7-5912a75f20fa │ Zigbee Window Treatment Mc │
└────┴──────────────────────────────────────┴────────────────────────────────────────┘
? Select a driver. 34
2023-10-30T22:58:55.894067637+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T22:59:25.900037974+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T22:59:55.903773978+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:00:25.909702981+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:00:55.912942060+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:00:57.400442727+00:00 TRACE Zigbee Window Treatment Mc Received event with handler device_lifecycle
2023-10-30T23:00:57.406014394+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> received lifecycle event: infoChanged
2023-10-30T23:00:57.414376394+00:00 TRACE Zigbee Window Treatment Mc Found DeviceLifecycleDispatcher handler in zigbee_window_treatment
2023-10-30T23:00:57.415588727+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 15.0
2023-10-30T23:00:57.416794061+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 0
2023-10-30T23:00:57.417998394+00:00 PRINT Zigbee Window Treatment Mc << Preference changed name: performCalibration old value: 1 new value: 0
2023-10-30T23:00:57.429530061+00:00 PRINT Zigbee Window Treatment Mc <<< Write perform Calibration >>>
2023-10-30T23:00:57.430942061+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x0CE9, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0xF001, DataType: Enum8, data: 0x00 > > > >
2023-10-30T23:00:57.458251727+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 60
2023-10-30T23:00:57.472111394+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= No
2023-10-30T23:00:57.472950727+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 0
2023-10-30T23:00:57.474180727+00:00 PRINT Zigbee Window Treatment Mc Device ID <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)>
2023-10-30T23:00:57.475397394+00:00 PRINT Zigbee Window Treatment Mc Manufacturer >>> _TZ3000_1dd0d5yi Manufacturer_Len >>> 16
2023-10-30T23:00:57.482848061+00:00 PRINT Zigbee Window Treatment Mc Model >>> TS130F Model_len >>> 6
2023-10-30T23:00:57.484195727+00:00 PRINT Zigbee Window Treatment Mc <<<<< Firmware Version >>>>> nil
2023-10-30T23:00:57.485411394+00:00 PRINT Zigbee Window Treatment Mc Memory >>>>>>> 1116.6552734375 Kbytes
2023-10-30T23:00:57.486599394+00:00 DEBUG Zigbee Window Treatment Mc Persiana Habit. 2 device thread event handled
2023-10-30T23:00:57.600190061+00:00 TRACE Zigbee Window Treatment Mc Received event with handler zigbee
2023-10-30T23:00:57.609475728+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x0CE9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, lqi: 0xC2, rssi: -74, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x10, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2023-10-30T23:00:57.637494061+00:00 DEBUG Zigbee Window Treatment Mc Persiana Habit. 2 device thread event handled
2023-10-30T23:00:57.638358728+00:00 TRACE Zigbee Window Treatment Mc Received event with handler zigbee
2023-10-30T23:00:57.639712728+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x0CE9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, lqi: 0xCE, rssi: -75, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x6F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xF001, DataType: Enum8, Enum8: 0x00 > > > >
2023-10-30T23:00:57.671292394+00:00 TRACE Zigbee Window Treatment Mc Found ZigbeeMessageDispatcher handler in zigbee_window_treatment → Tuya Device Handler
2023-10-30T23:00:57.672166394+00:00 INFO Zigbee Window Treatment Mc Executing ZclClusterAttributeValueHandler: cluster: WindowCovering, attribute: 0xF001
2023-10-30T23:00:57.676428394+00:00 PRINT Zigbee Window Treatment Mc <<< Accurate calibration Value >>> 0
2023-10-30T23:00:57.677644394+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> emitting event: {“attribute_id”:“signalMetrics”,“component_id”:“main”,“visibility”:{“displayed”:false},“capability_id”:“legendabsolute60149.signalMetrics”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/10/30 Time: 23:00
DNI: 0x0CE9 LQI: 206 RSSI: -75dbm
”}}
2023-10-30T23:00:57.689211728+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> emitting event: {“attribute_id”:“deviceInfo”,“component_id”:“main”,“capability_id”:“legendabsolute60149.deviceInfo”,“state”:{“value”:“UTC Time: 23:00:57 Calibration started”}}
2023-10-30T23:00:57.703557394+00:00 DEBUG Zigbee Window Treatment Mc Persiana Habit. 2 device thread event handled
2023-10-30T23:01:25.920435074+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:01:55.929869089+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:02:25.933777103+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:02:55.940633451+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:03:25.966486798+00:00 INFO Zigbee Window Treatment Mc Doing health check read for [0CE9]:0102:0008
2023-10-30T23:03:25.967790132+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x0CE9, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0008 > > >
2023-10-30T23:03:25.981561465+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:03:26.120218465+00:00 TRACE Zigbee Window Treatment Mc Received event with handler zigbee
2023-10-30T23:03:26.121190465+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x0CE9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, lqi: 0xCE, rssi: -74, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x17, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0008, ZclStatus: SUCCESS, DataType: Uint8, CurrentPositionLiftPercentage: 0x19 > > > >
2023-10-30T23:03:26.161256465+00:00 TRACE Zigbee Window Treatment Mc Found ZigbeeMessageDispatcher handler in zigbee_window_treatment
2023-10-30T23:03:26.164314465+00:00 INFO Zigbee Window Treatment Mc Executing ZclClusterAttributeValueHandler: cluster: WindowCovering, attribute: CurrentPositionLiftPercentage
2023-10-30T23:03:26.174997132+00:00 DEBUG Zigbee Window Treatment Mc Persiana Habit. 2 device thread event handled
2023-10-30T23:03:55.959955479+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:04:25.959962827+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:04:55.969089798+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:05:02.628232134+00:00 TRACE Zigbee Window Treatment Mc Received event with handler device_lifecycle
2023-10-30T23:05:02.639823801+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> received lifecycle event: infoChanged
2023-10-30T23:05:02.671524134+00:00 TRACE Zigbee Window Treatment Mc Found DeviceLifecycleDispatcher handler in zigbee_window_treatment
2023-10-30T23:05:02.672368801+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 15.0
2023-10-30T23:05:02.673585467+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 1
2023-10-30T23:05:02.675096801+00:00 PRINT Zigbee Window Treatment Mc << Preference changed name: performCalibration old value: 0 new value: 1
2023-10-30T23:05:02.676404801+00:00 PRINT Zigbee Window Treatment Mc <<< Write perform Calibration >>>
2023-10-30T23:05:02.699983467+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x0CE9, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0xF001, DataType: Enum8, data: 0x01 > > > >
2023-10-30T23:05:02.705418134+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 60
2023-10-30T23:05:02.723028801+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= No
2023-10-30T23:05:02.724324134+00:00 PRINT Zigbee Window Treatment Mc device.preferences[infoChanged]= 0
2023-10-30T23:05:02.725526134+00:00 PRINT Zigbee Window Treatment Mc Device ID <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)>
2023-10-30T23:05:02.726730134+00:00 PRINT Zigbee Window Treatment Mc Manufacturer >>> _TZ3000_1dd0d5yi Manufacturer_Len >>> 16
2023-10-30T23:05:02.727935801+00:00 PRINT Zigbee Window Treatment Mc Model >>> TS130F Model_len >>> 6
2023-10-30T23:05:02.739364134+00:00 PRINT Zigbee Window Treatment Mc <<<<< Firmware Version >>>>> nil
2023-10-30T23:05:02.740786134+00:00 PRINT Zigbee Window Treatment Mc Memory >>>>>>> 1098.125 Kbytes
2023-10-30T23:05:02.743370801+00:00 DEBUG Zigbee Window Treatment Mc Persiana Habit. 2 device thread event handled
2023-10-30T23:05:02.810235134+00:00 TRACE Zigbee Window Treatment Mc Received event with handler zigbee
2023-10-30T23:05:02.811197801+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: ac0fecda-d74a-45f3-b652-06263d3ab8a1 [0x0CE9] (Persiana Habit. 2)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x0CE9, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, lqi: 0xCA, rssi: -74, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x1D, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2023-10-30T23:05:02.817862134+00:00 DEBUG Zigbee Window Treatment Mc Persiana Habit. 2 device thread event handled
2023-10-30T23:05:25.970971145+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:05:55.982280160+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:06:25.989862174+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:06:55.998310855+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:07:26.009347202+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:07:56.019723883+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:08:26.022948564+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:08:56.040007182+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:09:26.053044367+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:09:56.060193704+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:10:26.061879041+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
2023-10-30T23:10:56.069879044+00:00 DEBUG Zigbee Window Treatment Mc driver device thread event handled
listening for logs… doneA
Hi, @Bernfp
This device does not report the 0xF003 attribute that reports the time elapsed in the movement.
I also see that the Health Check is being executed because it does not periodically report the status of the blind level.
Device may not have been configured correctly when pairing with the controller, perhaps because you made a change from another driver instead of pairing it directly with this driver.
Uninstall the device and add it again as close to the hub as you can, so that it is paired and configured correctly.
Hello,
Device and driver uninstalled, driver installed and device paired again.
Calibrated quickly with 15" (it takes 14,5")
Select Accurate Calibration, the device doesn’t do anything.
Calibrated accurately based on other devices instructions:
. With blind 0%, Select Accurate calibration
. Move up the blind manually with the switch to 100% and push stop button.
. Move down the blind manually to 0% and push stop button.
. Move up the blind manually to 100% and press stop button.
. Select Run mode in the settings menu.
Following this process the device recorded calibration started and calibration finished with 14,1"
The only problem is that movements are still not repetitive, exactly the same as before deleting the device and the driver.
Hi @Mariano_Colmenarejo
See above tests after deleting the device and paired again.
Any idea?
Thanks in advance.
If it says it’s malfunctioning, I have no idea what’s wrong.
The device could be bad!
If you want to send logs I will look at them
Hello @Mariano_Colmenarejo
Hello @dotan_shai
I tested to calibrate with a second new moes MS-108ZR module and " Zigbee window Treatment Mc" driver. I did it based on a video received from Moes. In this video, the calibration is manual ussing switches and of course with Moes app. After calibration, same issue, when I move up or down in a percentage different from 0 or 100%, movements of the blind are not repetitive (several cm different one each other).
Also tested with a Fibaro module and “Zwave Window Treatment MC” driver. I did the autocalibration. It’s a fully automatic process. After that, the movements of the blind are always exactly the same.
Moes 24€ / Fibaro 58€, but they are not exactly the same
Thanks both for your support on this.