Moes TRV - missing attributes

[jon11]

Hello,

I've bought one of these as a trial: trv

After researching on this forum, I've added the following drivers and tried associating the TRV with each in turn:
Tuya wall thermostat
Tuya Zigbee thermostats and TRVs

The TRV is connected and I see logging updates. However in the dashboard there are complaints of missing attributes. The exact parameters change depending on the driver used.

currently using Tuya Wall thermostat, with 'model group' = Moes. The attributes missing are : thermostatOperatingState, supportedThermostatFanModes, supportedThermostatModes. But these are not definable in the device page.

In the logs I see the following entry recurring: 2024-10-23 08:50:43.658 AMerrorgroovy.lang.MissingMethodException: No signature of method: java.lang.String.call() is applicable for argument types: (java.util.HashMap) values: [[cmdTime:1729669443756, pingTime:1729669412054]]
Possible solutions: wait(), chars(), any(), wait(long), take(int), each(groovy.lang.Closure) on line 1471 (method setHeatingSetpoint)

Any pointers? Am I using the correct driver?

[kkossev]

Hi Jon,

There are several different thermostats sold under 'MOES' white label, so the first thing to do is to identify what device you have. Please read and follow the instructions from this page :

HowTo Identify a Zigbee Device

Next, make sure you are using this driver :

[RELEASE] Tuya Zigbee Thermostats and TRVs driver

Update June 2024 : This driver uses a lot of common code with the other TRVs and thermostats drivers ( Sonoff TRVZB, Aqara E1 thermostat, but because of the Tuya specifics I decided to maintain a separate driver for it. [image] Moes BRT-100 TRV can be purchased from here : AliExpress : (link1) AliExpress : (link2) AliExpress : (link3) Amazon .de : (link4) Amazon .co.uk : (link5) Amazon. fr : (link6) Amazon .ca : (link7) Features: thermostatMode: heat : 5.0 .. 45.0 degrees C (step i…

Because you have paired the thermostat before installing the driver, you need to initialize it manually - select "LOAD ALL DEFAULTS" from the dropdown menu and then click on the button above :

But first, lets see what is your Zigbee device model and manufacturer data..

[jon11]

Hi @kkossev ,

The device information is:

• manufacturer: _TZE200_ywdxldoj
• model: TS0601
• outClusters: 0019,000A
• softwareBuild:
• tuyaVersion: 1.1.5

[kkossev]

This TRV should work with the new driver referenced in my previous post. Please configure it with loading by the default values and let me know if it works or not.

[jon11]

I did as you suggested. I can see the device communicating with the HE, but the dashboard is still complaining of Missing Attributes: thermostatOperatingState, supportedThermostatFanModes, supportedThermostatModes

The referenced missing attributes don't appear in the device page?

[kkossev]

From the screenshot I see that you still have a wrong deviceProfile MOES_BRT_100
Are you sure from the Configure drop-down menu you did the following :

1. First click on the dop-down menu (below the button), the drop-down list should become visible as in the picture in my previous post

2. You clicked on the '*** LOAD ALL DEFAULTS ***' menu item. Then, the dropdown menu will collapse and the selected option will become visible, like this :
   

3. You clicked on the 'Configure' button above.
   From your screenshot above, I see you have the default 'Configure the device' option selected, not the '*** LOAD ALL DEFAULTS***'

Hubitat device page UI is not very user friendly ... and this complicated driver has made it even more complicated.

[jon11]

That did the trick. I no longer get missing attribute errors. In the log file I do see the following line; java.lang.NullPointerException: Cannot get property 'name' on null object on line 4819 (method autoPollThermostat). Might you know what that is pointing to? I guess line 4819 is a point in the driver code?

[kkossev]

Yes, 4819 is the line number in the driver code. I see where the problem is (missing 'level' attribute - this TRV does not report the valve opening percentage 0..100, so no level attribute), It is too late here, will fix it in the next days. For now you can simply ignore this error, it does not affect the functionality.