I have been using a Meross mts300 thermostat to send temperature and humidity events to my C7 hub. A few days ago the events stopped and I saw the following error in the log multiple times.
This started soon after I upgraded the hub firmware from 2.4.3.137 to 2.4.3.149. Reverting to the 2.4.3.137 version solved the problem, looks like a Hubitat Firmware bug?
Is there any particular reason that you switched from the dedicated Meross thermostat driver to the new generic driver and then back again?
I ask as the new generic driver uses a new parse method that's under development.
The generic driver sets a data flag "newParse": true which routes the mater data as a map, since existing drivers parse methods only accept strings it's throwing an error.
For now you will need to stay on 137, or switch back to the generic driver.
The next release will reset this allowing switching between the two drivers.
I tried all three Matter Thermostat drivers, Meross, Google and Generic. I think the Generic driver "worked" but it did not report any changes in the thermostat humidity. I use the humidity value to control the HVAC cooling, so it is needed.
I will be switching to a C8 hub in a few days, presume that would have the same issue?
Interesting, I built the generic driver using an MTS300 and it was (and still is) reporting humidity, when changing drivers did you click configure?
Yes
I have been having some issues with the Meross not updating maybe that was the problem. I'll let it run for a few hours to check it is all working then I'll change to the generic driver and report back.
I have upgraded the hub firmware to V2.4.3.149 and swapped to the generic driver - and it works, it does provided humidity change events. Apologies for my mistake.
I went down this driver path because I loose thermostat -> hub communication if the power fails. At the moment I have to delete the Matter Service in the thermostat and recreate it to re-establish communication. Would either the Configure/Initialize/Refresh commands in the generic driver re-establish that communication?
both configure and initialize will renew the device subscriptions
configure does some device queries for options, then renews the subscriptions, initialize simply renews the subscriptions
next time this happens, click initialize, see if that fixes the issue
if you're having frequent power issues you should get your hubitat on a ups
if its already on a ups, and the thermostat gets stupid on power loss, then initialize should sort things out on a power restore
Download the Hubitat app
