Not sure where to post this request, as I couldn’t find a thread specific to the driver in question: I have an old Alloy MH-4 floor heating thermostat (I think it’s the same as the MCO MH-4 thermostat, but rebranded for Alloy), for which I need a Z-wave driver. I’m hoping the generic “zwave-thermostat-mc” driver by Mariano Colmenarejo will work, but would need Mariano to add the device fingerprint to the driver:
Mariano, if you could add this device fingerprint to the driver so I can try it out, I’d very much appreciate it. And I’ll of course report back on whether it works.
These devices don’t just need to add fingerprints to make them work.
I’ve looked at the documentation a bit and it has an away mode and temperature setpoints for each mode, which are not handled in the default lua libraries and a specific subdriver would have to be developed to handle all this and doing it without having a device to debug it is not possible or very complicated.
Thanks Mariano. The main thing I want to be able to do remotely is to change the temperature setting (e.g. turn it way down if I forget to put it into “away” mode).
Once the temperature is changed manually, the thermostat enters a “manual” mode. So a generic driver would still be useful even if it can’t change the thermostat between its various modes.
Added to this TEST driver the fingerprints, created a new profile and subdriver for this device.
If it is true that it uses these thermostat modes that the manual says, it should work for the modes “off”, “heat” (Manual), “away” (vacations), “auto” (Energy Saving heating).
The heating set points shown in the app should be the corresponding ones for each Mode (heat or away or auto)
Command Class supported by the device:
COMMAND_CLASS_BASIC;
COMMAND_CLASS_THERMOSTAT_SETPOINT;
COMMAND_CLASS_THERMOSTAT_MODE;
COMMAND_CLASS_THERMOSTAT_OPERATING_STATE;
COMMAND_CLASS_SENSOR_MULTILEVEL;
COMMAND_CLASS_ASSOCIATION;
COMMAND_CLASS_VERSION;
COMMAND_CLASS_MANUFACTURER_SPECIFIC
Note:
This device supports 4 kinds of modes in Z-Wave: Off mode; Heating mode (Manual);
Energy Saving heating mode (Auto) ; Away heating mode (Vacation).
Users can set these 4 modes via COMMAND_CLASS_THERMOSTAT_MODE. And
COMMAND_CLASS_BASIC can switch among Heating mode & Energy saving heating mode.
COMMAND_CLASS_THERMOSTAT_SETPOINT can be used to set the heating
temperature threshold value in Heating mode or Energy saving heating mode.
Try to see if it works and if something doesn’t work you would have to send me the logs with the CLI so I can debug it.
Thanks Mariano – I’ll give it a try when I get home and report back.
By the way, the full list of supported command classes isn’t shown on the MCO webpage, but is in the downloadable PDF manual. Here’s the list for reference:
Command Class supported by the device:
COMMAND_CLASS_ZWAVEPLUS_INFO,
COMMAND_CLASS_VERSION,
COMMAND_CLASS_MANUFACTURER_SPECIFIC,
COMMAND_CLASS_DEVICE_RESET_LOCALLY,
COMMAND_CLASS_ASSOCIATION,
COMMAND_CLASS_ASSOCIATION_GRP_INFO,
COMMAND_CLASS_POWERLEVEL,
COMMAND_CLASS_BASIC,
COMMAND_CLASS_FIRMWARE_UPDATE_MD_V2,
COMMAND_CLASS_CONFIGURATION,
COMMAND_CLASS_SENSOR_MULTILEVEL_V5,
COMMAND_CLASS_THERMOSTAT_SETPOINT,
COMMAND_CLASS_THERMOSTAT_MODE,
COMMAND_CLASS_THERMOSTAT_OPERATING_STATE,
COMMAND_CLASS_TIME,
COMMAND_CLASS_TIME_PARAMETERS
Note: Basic CC is used to control energy saving mode and comfort mode:
· Basic Set (Value = 0x00) = Set Energy Saving Mode
· Basic Set (Value = 0xFF) = Set Comfort Mode
· Basic Get = Get Report
· Basic Report (Value = 0x00) = Report Energy Saving Mode
· Basic Report (Value = 0xFF) = Report Comfort Mode
The other values besides the two above will be ignored.
Note:
This device supports 4 kinds of modes in Z-Wave: Off mode; Heating mode (Manual); Energy Saving heating mode (Auto) ; Away heating mode (Vacation).
Users can set these 4 modes via COMMAND_CLASS_THERMOSTAT_MODE. And
COMMAND_CLASS_BASIC can switch among Heating mode & Energy saving heating mode.
COMMAND_CLASS_THERMOSTAT_SETPOINT can be used to set the heating temperature threshold value in Heating mode or Energy saving heating mode.
I’ve installed the driver and the device. Smartthings says it is connected. But when I tap on the device, I get a message “The device hasn’t updated all of its status information yet. Check again later.”
I’ve checked again later, and this message still appears. I’ve tried a few things which haven’t helped:
tapped on various buttons on the thermostat to change its set temperature and mode (so this information gets sent to Smartthings)
turned the thermostat off and on
rebooted the SmartThings hub
uninstalled the thermostat and reinstalled it
reinstalled the driver, then reinstalled the thermostat
I got the same error message when using the generic Z-wave switch driver with this thermostat.
Any idea why Smartthings isn’t able to read information from the device?
Thanks – if this is too difficult to debug remotely, I’ll understand. I can try to set myself up to code drivers, but probably won’t have time until the holidays.
@Mariano_Colmenarejo I have several Qubino 1d relays and just came across this thread. I would love to be able to get the i2 sensor input working in my setups again. Did you ever get confirmation that your driver change worked? If not, I would be eager to test things out if you made a modified driver available again. Thanks!
I’ll need as much information about it as you can provide. Data sheet or instructions, model numbers, manufacturer code. It will likely be end of March before I can get to it.
See below information…
I think my issue isn’t with the driver as today I connected the same ring zwav outdoor contact sensor to an other hub in different location and it works perfectly with the same driver which is Z-Wave sensor driver from Smartthings developer.
Its the same device with same driver in both hubs in different locations, one location works fine and the other location it gave me an error says “the device hasn’t updated al of its status information yet. Check again later.”
What could be the issue? and how to resolve it?
$5 says that if you go to Samsung account, look at the Manufacturing Code for the device (it’s in the form xxxx-yyyy-zzzz) and it will be all zeros. If it is, the device wasnt included properly and you should exclude/include it again.
As an aide, in the future it would help if in your initial request you explained that you had other similar devices that functioned correctly, only this new one didn’t. When I saw your initial request it reads as if you had a brand new device of a type you’ve never had before and it never worked in the past. So I’m looking at the code trying to figure out “did this ever work? is this a new device that just came out? did i break something that caused a previously working device to stop working?” Those little details help figure out what someone is actually asking for and a debugging/diagnosis path.