Edge Driver for the Third Reality Smart Blind

Try with this driver version

───────────────────────────────────────────────────
 Name         Zigbee Window Treatment Mc
 Version      2022-10-16T13:32:24.666215259         
───────────────────────────────────────────────────
  - name: "quickCalibration"
    title: "Perform Quick Calibration (Sec)"
    description: "Perform Quick Calibration- (default: 30 Sec)"
    required: false
    preferenceType: number
    definition:
      minimum: 3
      maximum: 900
      default: 30

Thanks Marino looking great !!
Few improvements:

  1. Let’s add the QuickCalibration and the AccurateCalibration to all modules. not only MOES. What do you think ?
  2. You didn’t emit the status during calibration according to 0xF000 cluster. Can this be improved ?
    Here is a picture with success calibration data
    And Log File during calibration. Not MOES type

    zigbbelog.txt - Google Drive

Hi @dotan_shai

If the Moes does not have and does not work the accurate calibration, why is it going to be added?

In the Moes I don’t know what the calibration sequence is like, so I can’t write the steps anywhere.
If you send me the Moes calibration log, then I can see what the sequence is like and try to show it in the custom capability

When you reply, click on reply to my post or tag me, if not don’t let me know what you wrote

  • The device sends the information of the attribute 0x0008 (%)n and the attribute 0xF000 (status) in the same message.

The 0x0008 attribute is handled by the default libraries and they issue the status open or close and the %
I handle the 0xF000 attribute manually and it seems that the code to handle it manually is not executed when a message with multiple attributes proceeds, I don’t know if it will be because of this @nayelyz .

2022-10-17T08:23:15.850034150+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: 10b8dda6-1a26-4b9c-8866-fbd48d0a22d4 [0x3223] (Parents shutter)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3223, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, lqi: 0x6C, rssi: -73, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x35, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0008, DataType: Uint8, CurrentPositionLiftPercentage: 0x00 >, < AttributeRecord || AttributeId: 0xF000, DataType: Enum8, Enum8: 0x01 > > > >
2022-10-17T08:23:15.872967150+00:00 TRACE Zigbee Window Treatment Mc Found ZigbeeMessageDispatcher handler in zigbee_window_treatment
2022-10-17T08:23:15.880818483+00:00 INFO Zigbee Window Treatment Mc Executing ZclClusterAttributeValueHandler: cluster: WindowCovering, attribute: CurrentPositionLiftPercentage
2022-10-17T08:23:15.887305483+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: 10b8dda6-1a26-4b9c-8866-fbd48d0a22d4 [0x3223] (Parents shutter)> emitting event: {“attribute_id”:“shadeLevel”,“capability_id”:“windowShadeLevel”,“component_id”:“main”,“state”:{“value”:0}}
2022-10-17T08:23:15.957590816+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: 10b8dda6-1a26-4b9c-8866-fbd48d0a22d4 [0x3223] (Parents shutter)> emitting event: {“attribute_id”:“windowShade”,“capability_id”:“windowShade”,“component_id”:“main”,“state”:{“value”:“closed”}}

  • In the second case, the message sends the attribute 0XF001 (Calibration status) and 0xF003 (Total calibration time).
    Here the two attributes are handled manually, but it only executes the handler of the attribute 0xF003 and emits the total time only.

2022-10-17T08:23:26.119873154+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: 10b8dda6-1a26-4b9c-8866-fbd48d0a22d4 [0x3223] (Parents shutter)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3223, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: WindowCovering >, lqi: 0x74, rssi: -71, body_length: 0x000C, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x37, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xF001, DataType: Enum8, Enum8: 0x01 >, < AttributeRecord || AttributeId: 0xF003, DataType: Uint16, Uint16: 0x00C7 > > > >
2022-10-17T08:23:26.144171154+00:00 TRACE Zigbee Window Treatment Mc Found ZigbeeMessageDispatcher handler in zigbee_window_treatment → Tuya Device Handler
2022-10-17T08:23:26.160699488+00:00 INFO Zigbee Window Treatment Mc Executing ZclClusterAttributeValueHandler: cluster: WindowCovering, attribute: 0xF003
2022-10-17T08:23:26.166457821+00:00 PRINT Zigbee Window Treatment Mc <<< Travel time Value >>> 199
2022-10-17T08:23:26.172431154+00:00 INFO Zigbee Window Treatment Mc <ZigbeeDevice: 10b8dda6-1a26-4b9c-8866-fbd48d0a22d4 [0x3223] (Parents shutter)> emitting event: {“attribute_id”:“deviceInfo”,“capability_id”:“legendabsolute60149.deviceInfo”,“component_id”:“main”,“state”:{“value”:“Calibration Total Time: 19.9 Sec”}}

These are the zigbee handlersdeclared in subdriver @nayelyz

zigbee_handlers = {
    attr = {
      [zcl_clusters.WindowCovering.ID] = {
        [0xF000] = curtain_switch_handler
      },
      [zcl_clusters.WindowCovering.ID] = {
        [0xF001] = accurate_calibration_handler
      },
      [zcl_clusters.WindowCovering.ID] = {
        [0xF003] = travel_time_handler
      }
    }
  },

Hi Mariano,
According to my friend he was able to calibrate his MOES MS-108ZR module with accurate calibration using Tuya hub.
But according to users in HA only quick calibration is available and working as I showed in the picture above. I suggest give both abilities whatever works for the ST users with Tuya modules.

Added accurate calibration to MOES MS-108ZR profile

  • name: “performCalibration”
    title: “Perform Accurate Calibration”
    description: “Perform Accurate Calibration- (default: Run Mode)”
    required: false
    preferenceType: enumeration
    definition:
    options:
    “0”: “Perform Calibration”
    “1”: “Run Mode”
    default: “1”
  • name: “quickCalibration”
    title: “Perform Quick Calibration (Sec)”
    description: “Perform Quick Calibration- (default: 30 sec)”
    required: false
    preferenceType: number
    definition:
    minimum: 3
    maximum: 900
    default: 30
───────────────────────────────────────────────────
 Name         Zigbee Window Treatment Mc
 Version      2022-10-17T16:03:00.754793646
───────────────────────────────────────────────────

1 Like

@Mariano_Colmenarejo can you add the ThirdReality Temp & Humidity sensor to your driver? TIA

Hi @Drknght4

Added to these drivers versions

  - id: "Third Reality/3RTHS24BZ"
    deviceLabel: Third Reality 3RTHS24BZ
    manufacturer: Third Reality, Inc
    model: 3RTHS24BZ
    deviceProfileName: temp-humid-battery
────────────────────────────────────────────────────
 Name         Zigbee Temp Sensor with Thermostat Mc 
 Version      2022-10-18T14:48:00.997601618
────────────────────────────────────────────────────
─────────────────────────────────────────────────────────      
 Name         Zigbee Temp Sensor and Child Thermostat Mc 
 Version      2022-10-18T14:48:42.231017451
─────────────────────────────────────────────────────────
───────────────────────────────────────────────────
 Name         Zigbee Temp Humidity Sensor Mc            
 Version      2022-10-18T14:48:50.461198201        
───────────────────────────────────────────────────

@Drknght4 where did you get that from?
Been looking for a while and was told they werent for sale yet (some YouTubers had early access)

The Third Reality Temp & Humidity Sensor is now available on Amazon.

Note: I am an Amazon Associate and and the link provided is an Amazon link. I may receive a small commission for purchases made using the link. There is no additional cost to anyone that purchases a product via my link.

I have a setup video that will publish in November. The current version now sold on Amazon is improved based on input from several influencers. Namely, the sensors are more accurate and the bracket stand on the back is sturdy now and does not detach easily.

1 Like

I see that now.
Hopefully it’ll become available on the Amazon Canada site soon.

Mine was sent directly to me by ThirdReality to test it. But it is now available on Amazon

1 Like

@Mariano_Colmenarejo i will try it as soon as I get home. You the best… thank you

Here are some log from calibration of two MOES MS-108ZR devices.

  1. There are some Errors and Warnings
  2. Quick Calib. works fine (not in LOG)
  3. Acc. Calib. also works but never send Attrib 0xF003 with calibration time
  4. Although it seems that the 2nd device seems stack on calib. , we successfully changed to Run Mode and manage to control the shutter. But this didn’t appear on LOG.

We can live with that version, But as I know you… My guess , you will try to solve the errors with a new version :grinning:

Sorry!

I made a mistake when sending the data_type of the attribute 0xF003, they have to be uint16 (0x21) and by copy and paste I sent enum8 (0x30) as in 0xF001 and 0xF002 :man_facepalming:

I also forgot to activate the capability device Info to show the messages :man_facepalming:

Fixed in this version

───────────────────────────────────────────────────
Name Zigbee Window Treatment Mc
Version 2022-10-18T20:14:26.525048285
───────────────────────────────────────────────────

1 Like

@Mariano_Colmenarejo i just tried the ThirdReality Humidity Sensor and it worked perfect. Battery is also showing . Great Job! Thank you

Uploading: 52EAFAF8-D0FE-45D3-8444-E22523921F0A.png…


2 Likes

Hi, @Mariano_Colmenarejo

I have been talking to the team. Currently, there is a limitation that multiple attribute reports in the same message can’t be handled by different levels. So for the time being you would need to duplicate the handler for attribute 0x0008 into the subdriver. It is a known bug, but low priority so it hasn’t been worked on yet.

Seems that all sorted now. I’m even getting Calibration Time from MOES MS-108ZR.
Great job… NO MORE TUYA HUBS REQUIRES FOR CALIBRATING
I’m attaching a picture for success window calibration
THANK YOU VERY MUCH !!

I have a friend that uses your driver with MOES MS-108ZR that didn’t receive the calibration time as shown in Moes_2_calib.txt file. I suspect that this is because the poor RSSI reception. He said that, still all works and calibrate.

1 Like

Thanks for your reply @andresg

So handling each attribute in different subdrivers would it work, even if the two attributes are reported in the same message?

@Mariano_Colmenarejo not sure if you have another thread for your zigbee shade driver, but here’s another request :grin: Zemismart ZM85EL-1X