MTS200 floor heating thermostat

[Cully81]

Hello,

I have a MTS200 floor heating thermostat. I was able to integrate this as device without any problems and can see it as "Smart Thermostat". Unfortunately it does not work yet. For example, I can not select it as a thermostat and see no suitable entities. Has this not yet been integrated? If so, I am doing something wrong. Otherwise, I would be very happy about an integration.

Thank you

[krahabb]

Hello @Cully81 , This is the first time I see the mts200 and, after inspecting its feaures on the meross site I hardly expect this to be integrated correctly except it gets recognized as a meross device. This is good though since it allows us/you to collect a simple log trace which should be enough for me to provide an implementation for the thermostat. In order to do so, go to the meross_lan entry configuration in the integrations UI and enable 'tracing' on the entry. The trace will run for like 10 minutes and it could be useful to also 'trigger' some actions on the valve by the use of the meross app or by physically operate it by its panel while the trace is collecting data. After 10 minutes the tracing is stopped and you'll find the result under '.homeassistant/custom_components/meross_lan/traces' Please upload it so I can inspect the device capabilities/api

Thank you!

[Cully81]

Hello @krahabb

if I see this correctly, I can only enable tracing on detected devices, right? I have added MTS200 as integration. But I don't see it in the overview under integrations. There I see only my MSG100 and MRS100. The MTS200 does not appear there. But I can't add it again either, then I get the message "The device already exists".

[Cully81]

Here it is:

But I can't see it here:

[krahabb]

Wow..that's weird! Yes you should be able to see a related entry under integrations where you usually can configure the connection properties. Is it maybe 'ignored' or 'disabled' under integrations?

[Cully81]

It gets even weirder. After a reboot I got the message "New device detected". Then I click on "Configure" the window appears with the message "The device already exists".

But yes, it was actually also in the integration list as "disabled". (I don't remember doing that myself). How can I get the logs to you then?

[krahabb]

Ok, after re-enabling the configuration entry you'll be able to manage its configuration by hitting 'Configure' on the entry panel. Now, at the bottom, you should find a checkbox to enable tracing

[Cully81]

Here it is https://www.dropbox.com/s/72mifd0sivihrjo/mts200-1642425928.csv?dl=0

[krahabb]

Hello @Cully81 , the feature is now available on the dev branch. It is a accompanied by a big code refactor overall so I'll take some time to further test/review everything but if you're a git pro you could start cloning the dev branch rightaway into your HA. I'm going to publish a 'preview' anyway so it could be easily installed from HACS in the next few days

[Cully81]

Hi, I just installed the latest version. Looks great, thanks a lot. As far as I could see in my first tests, everything works perfectly. Only one small thing I noticed: The name of the middle button with the flame is "Heizen" (heat). But the function behind it would be "Manuell" (Manually). Can this be changed?

[krahabb]

Hello @Cully81 , Thank you for reporting it works: your trace was invaluable to get it right! As for the 'Heizen' flame, if you refer to the small flame icon right under the big temperature reading on the thermostat physical panel, that should be indicating the current 'state' of the heating circuit i.e. heating (active) or not heating (inactive) In HA/meross_lan that is reported by the climate entity attribute 'hvac_action' which is the one telling HA what the device is doing (beside its working mode). The value of this attribute is reported in the lovelace climate panel right under the temperature setpoint together with the current working mode (preset): you usually read 'Idle' in the panel when the flame icon is off while you get 'Heating' while the flame is on. The term right to the hvac_mode is the actual 'preset' or working mode which could be: custom (manual) - comfort (heat) - sleep (cool) - away (eco) - auto (schedule) There's a bit of mismatch between meross and HA/meross_lan regarding the mts heating modes: the meross uses terms like cooling or so which are not really correct since it is not capable of cooling: I take these 'meross modes' as 'presets' in meross_lan in order to comply with the HA climate entity behaviour. There's a deeper explanation of these choices here: even if there were some tweaks to the code this describes the reasoning behind the way meross_lan implements the thermostat/climate and how to translate meross idioms to HA ones.

EDIT: I might have got it wrong about the 'Heizen' flame you were referring to: if you're talking about the 'Heat' mode icon in the HA lovelace panel then this thread is definitely the answer: that icon is HA stuff anyaway and there's no way (at least no one I know) to add a 'Manual' labeling there

[Cully81]

Yes exactly, I mean this button

But if that can't be changed, it's not much of a problem.

[cagnulein]

@Cully81 is this integration still working to you with the last HASS? I'm getting no entites for a mts200 like yours.