ZWave MCOHome Thermostat additional device type

Hi,
Just got an MCO Home Thermostat. The device type/id does not match the zwave database entry. Can someone please update? See attached xml

Thanks, Geir

node26.xml (8.7 KB)

Please can you at least provide the name of the device, or the link to the database. There are multiple thermostats from this supplier, so we somehow need to know what you have actually bought.

Link

image

Thanks. I’ve updated the database.

1 Like

I have used Z-Wave MCOHome Thermostat with OH2.4 for several months without problems.
Today I upgraded to Z-Wave bundle “2.5.0.201909260727” from “2.5.0.201906151852” and is listed as unknown device (Node 5).

History:
After problems with Fibaro roller shutter 3, I upgraded to Z-Wave bundle “2.5.0.201906151852”. After that upgrade the MCOHome Thermostat was still working … but include / dicovery of additional Z-Wave devices worked only after restart of OH.

Today I wanted to include Fibaro RGB controller with new firmware 27.27 which does not work (I already use 3 Fibaro RGB controllers but with firmware 25.25) T solve that issue I tried to upgrade Z-Wave bundle again:

openhab> bundle:list|grep -i zwave
240 x Active x 80 x 2.5.0.201906151852 x openHAB Add-ons :: Bundles :: ZWave Binding
openhab> bundle:update org.openhab.binding.zwave https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
openhab> bundle:list|grep -i zwave
240 x Active x 80 x 2.5.0.201909260727 x openHAB Add-ons :: Bundles :: ZWave Binding
openhab>

After the upgrade the log showed the following warning:

2019-09-27 16:52:22.105 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 015F:0702:5102::2.6

I deleted and discoved the item (device) again but the item show up with “unknown device”

Has the device been removed from the database?

I have exactly the same device - 0702:5102. The zwave jar #769 https://ci.openhab.org/job/openHAB2-Bundles/ws/bindings/org.openhab.binding.zwave/target/ is missing the mh7h…xml file.
I assume that is the reason for your unknown device.

The database entry https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/773# for MH7H currently reports an error. It complains about a duplicate CONFIGURATION entry.

BTW, but unrelated: There is a new Version2 of the MH7H available now which supports three association groups. Apart from Lifeline there are two others which can be used to control switchs.

@chris is the only one that can fix that.

Yeah, he has the superpowers to remove entries :slight_smile:

1 Like

I flagged a couple of others like that & it appeared he needed to do some database work to correct them.
I am trying to clean up the database to help others.

With great power comes great responsibility… :smiley:

No - not just me - there are a few others with the same power…

Fixed.

3 Likes

Thank you @sihui that you fixed the database.
I have updated Z-Wave bundle again

openhab> bundle:list|grep -i zwave
240 x Active x 80 x 2.5.0.201909260727 x openHAB Add-ons :: Bundles :: ZWave Binding
openhab> bundle:update org.openhab.binding.zwave https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
openhab> bundle:list|grep -i zwave
240 x Active x 80 x 2.5.0.201909290432 x openHAB Add-ons :: Bundles :: ZWave Binding
openhab>
… deleted the device and searched for it again … but the device still show up as “unknown device”

I also got two warnings:

2019-09-29 07:34:50.236 [WARN ] [.ZWaveThermostatSetpointCommandClass] - Reached max tries to init the setpont Moist Air, this will be our last attempt
2019-09-29 07:34:50.241 [WARN ] [.ZWaveThermostatSetpointCommandClass] - Reached max tries to init the setpont Furnace, this will be our last attempt

Do I need to do anything else to get the fixed database?

Although it was fixed in the database, the next step is when it is exported to GitHub, usually once a week or so.

It then needs to get picked up by the OH build system, Only after all that happens will the changes be available.

1 Like

I did another Z-Wave bundle update “2.5.0.201910111149” today and now the MCOHome Thermostat is no longer listet as “unknown device” but as “MH7H Water / Electrical Heating Thermostat”. Great!
Thank you @couriersud, @Bruce_Osborne, @chris and @sihui for your feedback and help!

3 Likes

Did anyone have an issue with wrong date and time on the MCO? How can I send this? Also tried to reinitialise the device without luck…