MOES Zigbee Radiator Actuator HY368

[schoven]

See #3024, similar device

Was told to create a new issue, so here we go:

Device

• Product name: MOES Zigbee Radiator Actuator.

  • specs on package:

• Manufacturer: _TZE200_ckud7u2l

• Model identifier: TS0601

• Device type :

  • Sensor
  • Thermostat

Screenshots

[GuillaumeP01]

I collected used batteries and I confirm that the low battery is working.

[Smanar]

Nice thx, and I remove the "battery" in same time, this one seem not be used.

[GuillaumeP01]

On the other hand I put the new batteries back, no longer have an alert on the TRV but the low battery always remains at 1

Do you have a way to add a refresh?

[Smanar]

Yep, just need to wait, for the device send a new message (if you still have the problem it s strange).

And pls don't restart deconz , it will force the "false" state, but I prefer be sure the device send it.

[GuillaumeP01]

Ok I have to redo a test because I have included the valve again and everything is back to normal, but it's not the right solution.

[GuillaumeP01]

I redo the test after more than 3 hours the low battery information is still at 1

[rotragit]

When you change the batteries, the TRV should send the message lowbattery=0 once. Can you check the logs to verify the message is sent? lowbattery=0 is sent only once. If deconz misses it, the value will never be updated.

[Smanar]

Seriously ? There is no periodic return at least one time every 24 h ?

Imagine for exemple if you replace the battery when the gateway is off ...

[GuillaumeP01]

I will leave 24 hours and we will see

[rotragit]

@Smanar I have the log still active and in more than a week there is no message from my device when the battery is OK. Yes, that's the reason I asked the default true. If I change the batteries when the gateway is off then the status will be correct when the gateway come back on. Instead, if the batteries are low, the lowbattery message is sent quite often (minutes). On my device is "flapping" from lowbattery=0 to lowbattery=1:

01:28:32:750 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
01:29:32:652 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
01:41:32:708 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
01:42:34:464 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
01:53:32:653 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
01:54:32:752 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
02:10:32:753 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
02:11:32:653 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
02:27:32:653 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
02:28:32:752 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
02:52:32:652 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
02:53:32:750 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
03:09:32:652 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
03:10:32:749 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
03:26:32:650 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
03:31:32:632 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
03:35:31:657 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
03:39:32:743 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0
04:04:32:749 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 1
04:05:32:646 Tuya debug 5 : Status: 0 Transid: 4 Dp: 1385 Fn: 0 Data 0

It's like after a while the device tries to "work" and after a few seconds it detects the batteries are low. Or that is a strategy to bring the batteries to dead faster ^^

I suspect the behavior is the same for every tuya device, but I can be wrong.

[Smanar]

Lol. Ok, so I think it s possible to add a timer than switch the value to "false" after 1 h without message. But it s lot of code for that, and just need to restart deconz after changing batteries.

BTW I have almost finished the code to change window open setting. You need to send at config/ID the Json { "windowopen_set" : [true,20,20] }

It s same command than for enable/disable it, just parmeter are changing : [valve, temperature, minute]

But it s realy experimental ^^, so not sure that can happen.

[GuillaumeP01]

Good after almost 24 hours the low battery information is correctly returned to null in the raw information but not the reading of the strange information

Smanar you will tell me when I can install your new version for the tests on the window opening

[Smanar]

To null ? From the code is not possible, or I m wrong somewhere

You can make pull, it will not be dangerous, but idk what will happen.

[GuillaumeP01]

yes the value is null see screenshot

Sorry, I didn't understand how to make pull. I'm a newbie, can you tell me about the different orders? thank you

[Smanar]

You have the procedure here https://github.com/dresden-elektronik/deconz-rest-plugin at "Install deCONZ development package (optional, Linux only)"

Just replace the step 1 by git clone --branch tuya2 https://github.com/Smanar/deconz-rest-plugin.git

Can skip "git checkout -b mybranch HEAD"

[GuillaumeP01]

Ah ok sorry I did not understand I update and keep you posted

During compilation I have the following errors: make[1]: *** [Makefile.Release:656: release/de_web_plugin.o] Error 1 make[1]: *** Attente des tâches non terminées.... make[1] : on quitte le répertoire « /home/guillaume/deconz-rest-plugin » make: *** [Makefile:40: release] Error 2

what do I have to do ?

[Smanar]

Ha, I think you have error displayed before this message, on diffrent color

[GuillaumeP01]

I have this:

de_web_plugin.cpp: In member function ‘void DeRestPluginPrivate::addSensorNode(const deCONZ::Node*, const deCONZ::NodeEvent*)’:
de_web_plugin.cpp:4419:84: error: expected ‘;’ before ‘{’ token
                     else (node->nodeDescriptor().manufacturerCode() == VENDOR_NONE)

[Smanar]

Ok c'est ma faute, j'ai corrigé, tu peux re tenter.

[GuillaumeP01]

tu es français ? Je fait un nouvel essai

[GuillaumeP01]

It's good the compilation, it went well this time I re-included the TRV and here is the new raw information:

    Configuration
    Informations brutes

{
    "21": {
        "config": {
            "heatsetpoint": 2350,
            "locked": false,
            "mode": "auto",
            "offset": -100,
            "on": true,
            "preset": "manual",
            "reachable": true,
            "schedule": [],
            "schedule_on": false,
            "windowopen_set": false
        },
        "ep": 1,
        "etag": "75c86eb775165cfb0a65664ea20e7405",
        "lastseen": "2020-08-23T18:31Z",
        "manufacturername": "_TZE200_ckud7u2l",
        "modelid": "TS0601",
        "name": "TS0601",
        "state": {
            "lastupdated": "none",
            "lowbattery": null,
            "on": null,
            "temperature": 2400,
            "valve": null
        },
        "type": "ZHAThermostat",
        "uniqueid": "84:2e:14:ff:fe:f1:54:bb-01-0201"
    }
}

[GuillaumeP01]

For the window opening I added the time and temperature settings but it did not change on the valve. 01-0201.config::windowopen_set::1,20,20

[Smanar]

you need to use the bracket (like for "xy" for color). And yes I m french, and I don't understand why you still have "null" at low battery ...

[GuillaumeP01]

can the null value be because of jeedom? can i see some other way?

Do you have a link for the sample order for the color? Thank you

[Smanar]

I have checked the code, and I m sure you can't have "null", so not sure the procedure to change the lib have worked, you have restart deconz, after having changed the file ?

I realy don't know how work jeedom, but you can mimic the command to change color "XY" Or use curl

curl -H 'Content-Type: application/json' -X PUT -d '{"windowopen_set":[true,20,20]}' http://IP:PORT/api/KEY/sensors/21/config

If something is wrong you will have an error message using curl. IP and PORt are the same than for phoscon, for the KEY you have it in jeedom confog (can use the same)

[GuillaumeP01]

yes i restarted deconz. I even restarted my machine. I did not have any new errors during the procedure. I can do it again if necessary. but first I'll test the curl command and let you know.

{
    "21": {
        "config": {
            "heatsetpoint": 2300,
            "locked": false,
            "mode": "auto",
            "offset": -100,
            "on": true,
            "preset": "manual",
            "reachable": true,
            "schedule": [],
            "schedule_on": false,
            "windowopen_set": false
        },
        "ep": 1,
        "etag": "d3f76a92a1b12ab0d045844cdcd4a48b",
        "lastseen": "2020-08-24T16:44Z",
        "manufacturername": "_TZE200_ckud7u2l",
        "modelid": "TS0601",
        "name": "TS0601",
        "state": {
            "lastupdated": "none",
            "lowbattery": null,
            "on": true,
            "temperature": 2250,
            "valve": 100
        },
        "type": "ZHAThermostat",
        "uniqueid": "84:2e:14:ff:fe:f1:54:bb-01-0201"
    }
}

[GuillaumeP01]

The curl command works and changes parameters on the valve well. thank you so much

[GuillaumeP01]

I just redo the install procedure, restart the PC and it's always the same thing All state values are null.

"state": {
            "lastupdated": "none",
            "lowbattery": null,
            "on": null,
            "temperature": null,
            "valve": null

[Smanar]

Ok, so no more idea for this problem, I will ask to other ...

[GuillaumeP01]

after the feedback, there is only low battery on null

"state": {
            "lastupdated": "none",
            "lowbattery": null,
            "on": false,
            "temperature": 2150,
            "valve": 0

[Smanar]

I have perhaps an answer from ebaawn. It seem the value set during my initialisation is overwritted with the values from the database shortly after. so if you already have the value "null" in the database it can be an explanation.

You don't have deleted the device, just re-included ?

[GuillaumeP01]

yes that's it, no deletion just re-included the trv

[Smanar]

Ok so it s a possible reason, will see later, not realy dramatic ^^

[GuillaumeP01]

if you want I can do one by removing the trv and re-included it

[GuillaumeP01]

I did a test by removing the TRV but it doesn't change anything there is always null on opening window

 "state": {
            "lastupdated": "none",
            "lowbattery": null,
            "on": true,
            "temperature": 2450,
            "valve": 65

[killeriq]

Adding also details pics + link https://www.moeshouse.com/collections/trv-radiator-valve/products/tuya-zigbee3-0-new-mini-wifi-radiator-actuator-smart-programmable-thermostat-temperature-trv-controller

[schoven]

The work you guys put in is very much appreciated. Once finishes PM me so i can gift you guys a digital cup of Coffee :)

[GuillaumeP01]

despite several attempts, I failed to create the commands with the parameters for the window opening detection in jeedom. After having tested for a good week, the operation chosen for me will be the auto mode and the manual preset because in jeedomle plugin thermostat really allows a lot of things.

Could you tell me Smanar when the integration of TRV in the stable branch will be available?

[Smanar]

The PR is submitted (the link is just above), need to wait if it will be accepted, the next deconz version will be in 10 days. Do you use deconz in stand alone or the one integrated in the jeedom plugin ?

For the command use in jeedom, you can try to compare the values send using the log, but I remember another user have failed to use the "stop" command for a roller shutter too. something not possible to create the JSON.

[GuillaumeP01]

I use deconz from home assistant as a gateway and jeedom as a receiver deconz is not installed locally on jeedom. I noticed that the home assistant version was updated more regularly but I may be wrong.

I tried to see the values send from the log but even if I hardened [true, 20,20] only true is sent.

Thank you very much for all your help

[Smanar]

Take a look how jeedom change the color, it need to use a json like [x,y]

[GuillaumeP01]

I looked at this track but in jeedom there is a color function directly

[Smanar]

Have you ask to the plugin dev ? As value you can use bool (true/false) number , string just need to ask how to use array.

[GuillaumeP01]

I made the request and it is incurring of addition

[Abbadon89]

deconz version will be in 10 days.

Where i can find this information?

[Smanar]

I don't find a link for the information, about beta/alpha/release version.

But you have at least one version every 15th of the month

[Mimiix]

@Smanar Readme file contains it.

[Smanar]

The sheduled date ?

[Abbadon89]

This is a beta release. As recently decided in Discord, beta releases are now scheduled for every 15th of a month. https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_78

[Mimiix]

@Smanar @Abbadon89

@manup didn't merge my PR yet: https://github.com/dresden-elektronik/deconz-rest-plugin/pull/3241