More Configuration Entities for MTS200 #242
Replies: 9 comments 23 replies
-
|
Hello @BlackDragon7402, |
Beta Was this translation helpful? Give feedback.
-
|
Hello @krahabb, Following are the traces with their respective events in the offical Meross App. Trace A: Turning the brightness up Note: The "Im Standby Modus" (en: in standby mode) cant exceed the "Im Betrieb" (en: in operation mode). Needs to be standby <= in operation Trace A: Below a picture of the Meross App where I did the above changes: Trace B:
Below a picture of the Meross App where I did the above changes: Trace C:
Note: If child lock is enabled. A press on the displays shows the symbols "LOc" for locked Below a picture of the Meross App where I did the above changes: Hope this helps. If you need anymore traces/ information feel free to ask. Have a great day |
Beta Was this translation helpful? Give feedback.
-
|
Hello @BlackDragon7402, |
Beta Was this translation helpful? Give feedback.
-
|
@BlackDragon7402,
If you go the route of trying the service I suggest you to use the yaml interface in HA in order to bypass some UI checks and 'freely' enter those values. It will be a bit cumbersome especially since it isn't well refined but it usually works when you get the hang of it |
Beta Was this translation helpful? Give feedback.
-
|
I will have to take a more detailed look into that. I am not that familiar with the service interface in HASS (neither the yaml interface). |
Beta Was this translation helpful? Give feedback.
-
|
I can help here. The "in operation" brightness goese from 1 to 8. The steps aree with percentages in the MQTT messages. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! |
Beta Was this translation helpful? Give feedback.
-
|
This device is supposed to be an underfloor heating controller, and has an internal sensor for air temperature and an external sensor for floor temperature. The FAQ at meross website states that this can work in two ways: All this happens via this namespace: Messages coming from the device (or cloud) via this namespace look like this:
currentTemp here is the floor sensor temperature and value is the overheating limit. min/max are self explanatory. Would be nice if the integration added a temp sensor entity this and a slider to adjust the limit, as it is one of the main features of this device! Moreover, the thermostat supports one other very important mode of operation: It can thermostatically control the on/off relay based exclusively on the floor sensor temperature instead of the air temperature. To switch to that mode of operation all it takes is this
(the default mode is 0) The state can be retrieved by using After doing this, the thermostat is going to report the floor temperature as the normal climate temperature and control based on that. Overheating protection is also disabled automatically in mode 1. This is very important for anyone who has this thermostat for a bathroom floor, since the thermostat is usually fitted outside the bathroom but the floor is inside. There's no point in using the internal sensor in that case. It would be great if the appropriate switches to turn this on and off get created in this integration. |
Beta Was this translation helpful? Give feedback.
-
|
Looks pretty clear, |
Beta Was this translation helpful? Give feedback.
-
|
Current alpha (2.7.0-alpha.2) contains a basic implementation of 'screen brightness' control. It should work except I didn't put any check regarding the relative values between the 'operation' and the 'standby' levels so you could manually mix-mismatch those. I'll wait for feedbacks |
Beta Was this translation helpful? Give feedback.
-
|
Quick early testing: Looks like steps are forced to be in 12.5% increrments, and there's also some minimum logic on the device. setting standby to 98 reverts to 87.5 seetting operation to 11% reverts to 25 Setting operation to 27 reverts to 25 setting standby to 10 reverts to 0 setting operation to 10 reverts to 25 setting operation to 12.5 remains the same |
Beta Was this translation helpful? Give feedback.
-
|
The 'operation' rounding looks a bit weird..I can't get the logic behind those rounding at 25. |
Beta Was this translation helpful? Give feedback.
-
|
more samples I think operation cannot be set to 0 at all (just like in the app it cannot go to step 0, the range is 1-8). Both standby brightness and operation brightness do change the brightness (in steps). They are independent indeed - a high stand by and low operation makes the screen dim when you touch it. operation to 40 -> 37.5 operation to 12.5 -> 12.5 operation to 1 -> 12.5 setting operation to 0 -> 12.5 |
Beta Was this translation helpful? Give feedback.
-
|
In current (beta) implementation I'm going to just fix the 12.5 % step and leave the values unrelated between each other seeing the device is reflecting that. |
Beta Was this translation helpful? Give feedback.
-
|
In the meross app there eare two horizontal sliders and both are set up to go from 0 to 8. But infact the first one (for operation) can only be dragged left to 1 at runtime. |
Beta Was this translation helpful? Give feedback.
-
|
Here a screenshot how the hard limit has been „solved“ in the merross app |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Regarding the newly added overheat support. Attached some picture showing the "issue".
|
Beta Was this translation helpful? Give feedback.
-
|
If you're not using any external sensor you could just disable those entities (external temp and overheat warning) so they don't clutter your UI. Out of curiosity: under 'Configuration' entities in the device page you should be able to access 2 switches to enable/disable overheat and external sensor mode. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like the device must have a mechanism to detect if the external sensor is connected or not. Moreover, floor overheat protection switch (on/off) cannot be turned to "On" if the external sensor is not connected. edited: My understanding is that the check that is performed is based on a function called So it looks like the check happens via parsing the result of Separately, when the external sensor is connected, and The response to The response i got while the external sensor is not connected is this: so I think that overheat.warning=2 means the external sensor is not connected, while warning=1 should mean that the floor temperature has exceed the maximum set in the overheating protection while the external sensor is connected (assuming onoff=1 as well). So warning is not a pure binary sensor, it is tri-state |
Beta Was this translation helpful? Give feedback.
-
|
Ok probably will just deactivate the entity then :D |
Beta Was this translation helpful? Give feedback.
-
|
In my latest test I was not able to set the thermostat to 'external sensor mode' using the integration. When I switch it in HA, it reverts back to normal mode after a few minutes, the setting doesnt "stick" for some reason. Doing more testing to see what is happening. With the meross app it can be switched to external sensor mode without a problem. |
Beta Was this translation helpful? Give feedback.
-
|
i think the reason is that the integration sends this (according to the logs) and receives this: i think correct message to send is The same is true for i think it should be |
Beta Was this translation helpful? Give feedback.
-
|
Hi, The only hint at some point of "lock" seems to be at the "header": But I guess thats not related to it? Probably useless, but just in case :D |
Beta Was this translation helpful? Give feedback.
-
|
Ok will give this a try later today |
Beta Was this translation helpful? Give feedback.
-
|
Sadly no success as far as I can tell. Can I try something else/different? The GETs: Same for the first one provided by you: Also tried the SET: |
Beta Was this translation helpful? Give feedback.
-
|
did you get any notification in the side panel of HA? |
Beta Was this translation helpful? Give feedback.
-
|
No but just to be sure I am not looking at the wrong notifcations Here pictures:
|
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'll reviewed the code (since I don't even know what works and how ;) and the notification is only shown when the device replies. |
Beta Was this translation helpful? Give feedback.
-
I have been using your HACS Integration for the past months and I am really happy with it.
Not quite sure how active you manage it or still add features.
I really like your "Configuration Feautures" like the DND Mode.
I would love to see that light control for the MTS200 Display as I would like to automate this entity which is not possible in the official Meross App. eg.: Turn down the brightness based on the outside light, day or night
Same goes for the child lock feature with locks the inputs from the device itself. It is just kinda annoying to go into every device and change it manually in the meross app :D
Love the integration and keep up the good work
Beta Was this translation helpful? Give feedback.
All reactions