Domoticz

Setpoint of the Qubino on/off thermostat ZMNHIA2 isn't updating the Qubino Module when entering a number, it is in the interface.
And isn't update with the up- and down arrows in the interface.
Getting this error in OpenZWave control panel:
2015-09-09 18:51:22.473 Error, Node006, ERROR: Dropping command, expected response not received after 1 attempt(s)

Then it reset to 0 again.

Any news about this issue?

up.

Regards.

Same problem for me.

Switch to beta version for some improves but still can't use my Qubino on/off thermostat ZMNHIA2

The cooling 1 value never change even after modifying the value on domoticz

Changing value from open zwave control panel result on 0.0 value after any refresh

Hi,

Same problem for me !

hi all,

same probleme for me ... please help !

Has anyone fixed the issue with this unit ? I have the same issue. When I look in the OZW i Can see the option for a THERMOSTAT_SETPOINT ?

Output from OZW,
-30 12:08:42.466 Detail, Node011, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x0b, 0x06, 0x43, 0x03, 0x01, 0x22, 0x00, 0xe6, 0x7f
2015-12-30 12:08:42.469 Info, Node011, Response RTT 57 Average Response RTT 63
2015-12-30 12:08:42.470 Detail, Node011, Expected reply and command class was received
2015-12-30 12:08:42.470 Detail, Node011, Message transaction complete
2015-12-30 12:08:42.472 Detail, Node011, Removing current message
2015-12-30 12:08:55.803 Info, Node011, Value::Set - COMMAND_CLASS_THERMOSTAT_SETPOINT - Cooling 1 - 2 - 1 - 20.0
2015-12-30 12:08:55.806 Detail, Node011, Queuing (Send) ThermostatSetpointCmd_Set (Node=11): 0x01, 0x0c, 0x00, 0x13, 0x0b, 0x05, 0x43, 0x01, 0x02, 0x21, 0xc8, 0x25, 0xdd, 0xbf
2015-12-30 12:08:55.808 Detail, Node011, Queuing (Send) ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x02, 0x25, 0xde, 0x56
2015-12-30 12:08:55.812 Info, Node011, Sending (Send) message (Callback ID=0xdd, Expected Reply=0x13) - ThermostatSetpointCmd_Set (Node=11): 0x01, 0x0c, 0x00, 0x13, 0x0b, 0x05, 0x43, 0x01, 0x02, 0x21, 0xc8, 0x25, 0xdd, 0xbf
2015-12-30 12:08:55.822 Detail, Node011, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-12-30 12:08:55.824 Detail, Node011, ZW_SEND_DATA delivered to Z-Wave stack
2015-12-30 12:08:55.835 Detail, Node011, Received: 0x01, 0x05, 0x00, 0x13, 0xdd, 0x00, 0x34
2015-12-30 12:08:55.837 Detail, Node011, ZW_SEND_DATA Request with callback ID 0xdd received (expected 0xdd)
2015-12-30 12:08:55.840 Info, Node011, Request RTT 25 Average Request RTT 23
2015-12-30 12:08:55.845 Detail, Node011, Removing current message
2015-12-30 12:08:55.848 Info, Node011, Sending (Send) message (Callback ID=0xde, Expected Reply=0x04) - ThermostatSetpointCmd_Get (Node=11): 0x01, 0x0a, 0x00, 0x13, 0x0b, 0x03, 0x43, 0x02, 0x02, 0x25, 0xde, 0x56
2015-12-30 12:08:55.858 Detail, Node011, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2015-12-30 12:08:55.860 Detail, Node011, ZW_SEND_DATA delivered to Z-Wave stack
2015-12-30 12:08:55.871 Detail, Node011, Received: 0x01, 0x05, 0x00, 0x13, 0xde, 0x00, 0x37
2015-12-30 12:08:55.873 Detail, Node011, ZW_SEND_DATA Request with callback ID 0xde received (expected 0xde)
2015-12-30 12:08:55.876 Info, Node011, Request RTT 24 Average Request RTT 23
2015-12-30 12:08:55.906 Detail, Node011, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x0b, 0x06, 0x43, 0x03, 0x01, 0x22, 0x00, 0xe6, 0x7f
2015-12-30 12:08:55.910 Info, Node011, Response RTT 58 Average Response RTT 60
2015-12-30 12:08:55.911 Detail, Node011, Expected reply and command class was received
2015-12-30 12:08:55.914 Detail, Node011, Message transaction complete
2015-12-30 12:08:55.917 Detail, Node011, Removing current message
2015-12-30 12:09:08.940 Detail, Node011, Polling: COMMAND_CLASS_SENSOR_BINARY index = 0 instance = 1 (poll queue has 0 messages)
2015-12-30 12:09:08.943 Detail, Node011, Queuing (Poll) MultiChannel Encapsulated (instance=1): SensorBinaryCmd_Get (Node=11): 0x01, 0x0d, 0x00, 0x13, 0x0b, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x30, 0x02, 0x25, 0xdf, 0x49
2015-12-30 12:09:08.947 Info, Node011, Sending (Poll) message (Callback ID=0xdf, Expected Reply=0x04) - MultiChannel Encapsulated (instance=1): SensorBinaryCmd_Get (Node=11): 0x01, 0x0d, 0x00, 0x13, 0x0b, 0x06, 0x60, 0x0d,

How do I confirm if the COMMAND_CLASS_THERMOSTAT_SETPOINT is not getting applied correctly ?

Cheers
Rich

interesting, sounds alot like my issue here: viewtopic.php?f=6&t=9510

Hello,

If the ZMNHIA2 behaves the same as my new ZMNHID1 (the ZWave Plus equivalent of the ZMNHIA2), then the problem is that domoticz does not expose the "Mode" parameter of the thermostat.

This parametr can be set from the openzwave control panel, which you can access from domoticz's zwave setup screen.

By default, this parameter is set to Off, meaning that the thermostat won't turn on, and that it rejects setpoint changes.

So open the openzwave control panel, click on your ZMNHIA2 (or ZMNHID1), and change Mode from Off to Auto.

Now back to domoticz, and voilà, your device accepts setpoint changes, the relay clicks ON when the temperature measured by its attached sensor is below setpoint - hysteresis, and clicks OFF when above setpoint + hysteresis.

At least this works for my ZMNHID1, so give it a try, and i bet a goat that it will work.

Now why domoticz is not showing the Mode parameter is my next quest

Ps: there are errors in the ZMNHIA2.xml config file, which won't prevent using it. I have made a fixed version which I will upload to openzwave github, along with my working ZMNHID1.xml

Regards,
--
Stéphane

Good evening,
I'm beginner in Domoticz and Z-Wave, please can you explain very simply how to use your version in github with ZMNHID1.xml

I understand this is a configuration file I must introduce in my Raspberry (with Debian), but where and how ?
Then, does Domoticz will use this new configuration automatically (after a reboot for example ?).

Many thanks
Olivier

Ok, found why the "Mode" (Off / Auto) parameter is visible in OpenZWave control panel but not in domoticz, preventing turning to Auto from domoticz.

Just remove those 2 lines from domoticz/Config/qubino/ZMNHIA2.xml:

<!-- Remove COMMAND_CLASS_BASIC -->
<CommandClass id="32" action="remove" />

Then stop domoticz, delete domoticz/Config/zwcfg_0x$$$$$$$$.xml (replace with your unique zwave home id number) and restart domoticz. You will see a new unused device: the thermostat Mode switch, with two possible values: Off and Auto. Yay!

Same is true for the new ZMNHID1 ZWave+ replacing the ZMNHIA2.

Looking at OpenZWave documentation, I can't seem to find a reason for the lines below, which I may try removing aswell later:

<!-- Map endpoints to instances -->
<CommandClass id="96" mapping="endpoints" />

There are other errors in the ZMNHIA2.xml file but at least the change above will allow you to use your thermostat

Regards,
--
Stéphane

I just started a new project in my RPi 2B, adding the Qubino ZMNHIA2 thermostat to control my electric floor heating unit in my bathroom. Naturally I am hitting a few issues.

The things I like to accomplish are:
1. Use the set-point and temperature measured by the sensor to power on/off the floor heating.
2. Create a time schedule that changes the setpoint value for each day of the week.
3. Control and view values of the thermostat using Domoticz
4. Hardwire a (bi-stable) switch to the ZMNHIA2 to manually change the setpoint to a high and low value

I have read the related posts on the forum which give me some insight. Still I got quiet a few question regarding the ZMNHIA2 thermostat. I hope some of you can help me with a couple of them.

The basic set-up is a RPi2B running Raspbian with a Razberry Z-Wave module and a RFXtrx433E. Raspian and Domoticz are running on a 16GB Sandisk USB drive (not on the SD card)

Initially I had 2 Fibaro smoke detectors connected but I removed them and instructed a hard reset on the Razberry before I started adding the ZMNHIA2 so no other Z-Wave devices in Domoticz except when I started for the Razberry.
Including the Qubino ZMNHIA2 went smooth, no issue at all.

The challenges are how to activate the relay using domoticz, manually and via the setpoint, and how to get the ZMNHIA2 values (power, setpoint, temperature,…) reported in Domoticz .

Below a list of all my questions (format may look like a school test but it isn’t one )

Starting with the most essential probably…. :

• In my domoticz folder I see 2 versions of the ZMNHIA2.xml file. One in pi/domoticz/Config/qubino and 1 in pi/open-zwave-read-only/config/qubino. And I see a 3rd version on github.
Q1. Which xml file is used by Domoticz (I assume the one in pi/domoticz/Config/qubino)
Q2. Which file is best?
Q3. Is there an ever better/newer one?

• When changing the xml files I read in the post I need to delete the file domoticz/Config/zwcfg_0x$$$$$$$$.xml. Actually I have 2 of these files in my /domoticz/Config folder: (zwcfg_0xc1404bcf.xml and zwcfg_0xd43b2e06.xml)
Q4. Which file should I delete (both?)
Q5. Any idea why I have 2?

After adding the Qubino ZMNHIA2 in my Z-wave network I see there are 8 new entries in the Domoticz Devices overview:
Sensor 2x
Thermostat mode
Power 2x
kWh meter
Temperature
Setpoint

• So the “mode” is visible in the device overview. It is NOT visible in the OpenZWave control panel. I can add it in the devices overview which results in a new “Mode” section in the Utility panel.
Q5. Should the “mode” by visible in the OpenZWave control panel? (The post suggest it should)
Q6. What is the function of this mode “switch”

• I see 2 sensors (subtype switch) in the Domoticz devices overview. Sometimes the on/off status changes but I can’t see what triggers the change..
Q7. What is the function of the 2 sensors.
Q8. What action setting the ZMNHIA2 influences their values and vice versa what is triggered on the ZMNHIA2 by changing these (on/off) in Domoticz

• Temperature sensor very rarely gives a new value in Domoticz. I see one at around 17:40, 17:45 and 17:55 and thereafter only1 at 13:15h When I test the sensor it by putting it in warm water the value does not change in Domoticz.
Q9. What can explain this behavior.

• I see 2x a power entry (subtype electric) in the Domoticz devices overview. Only 1 of them gives a power value in Domoticz. And there is only 1 output on the ZMNHIA2 so its logical there is only 1 power entry.
Q10. What is the function of the 2nd power entry

End of list (for now)

Dutchsea

• When changing the xml files I read in the post I need to delete the file domoticz/Config/zwcfg_0x$$$$$$$$.xml. Actually I have 2 of these files in my /domoticz/Config folder: (zwcfg_0xc1404bcf.xml and zwcfg_0xd43b2e06.xml)
Q4. Which file should I delete (both?)
Q5. Any idea why I have 2?

In zwcfg_0x$$$$$$$$, digits $$$$$$$$ are the home_id, you cans see this value in Control Panel.

You have two of them: perhaps you reset all your net then another zwcfg file was created.

• So the “mode” is visible in the device overview. It is NOT visible in the OpenZWave control panel. I can add it in the devices overview which results in a new “Mode” section in the Utility panel.
Q5. Should the “mode” by visible in the OpenZWave control panel? (The post suggest it should)
Q6. What is the function of this mode “switch”

Mode is visible in Control Panel
Mode Auto: switch power ON when set point temperature is reached.
Mode OFF: thermostat is disconnected

I have the ZWavePlus version ZMNHID1. It reportas just 4 devices: Electric (power watts), KWh (Energy), Thermostat Mode (Thermostate), LaCrosse TX3 (Temperature sensor), SetPoint (Thermostat)
Bye

Thx, I found the ID in the control panel (c1404bcf). The other one must be an older obsolete copy.

I hope the other questions in my long post can also be addressed by someone.

Additionally I have concluded that the ZMNHIA2.xml file located in pi/domoticz/Config/qubino folder is the best one though it contains errors.

Below the errors I fixed and a copy of my new ZMNHIA2.xml.

Still the thermostat does not work. I am going to try it again with a new RPi 3B tomorrow using an Aeon Labs Z-Wave stick as opposed to the Razberry I use now. To be continued...

Changes/corrections in the ZMNHIA2.xml based on the Qubino manual I received with the thermostat and the post from StephaneG:

1. For parameter (index) no. 3 changed default value from 0 to 1
2. For parameter (index) no. 44 changed default value from 132 to 5
3. For parameter (index) no. 45 corrected help text
4. For parameter (index) no. 63 changed default value from 1 to 0
5. For parameter (index) no. 63 changed text for both labels
6. Removed code:
<!-- Map endpoints to instances -->
<CommandClass id="96" mapping="endpoints" />