Indigo Domotics

Is the Qubino ZMNHID3 supported by Indigo? I'm specifically looking to use the external temperature sensor. Has anybody used it with Indigo to read temperature?

It doesn't look like anyone has tried it with Indigo yet (and submitted a device report). I did find some submitted device reports from users with the older ZMNHID1. It sounds like it was at least partially or mostly functional with Indigo, but there wasn't enough detail to know for sure.

I don't like being the first one, but really could use a temperature sensor with external probe. (Pool, sauna, hot tub, fridge). I might take a plunge so I can send you the device report. Are there any other z-wave devices that would have an external temperature probe and work with Indigo.

On is on order. Should receive soon and report how/if it works. I will also submit device definition and logs from inclusion.

I got it and added it to indigo. It shows up as a thermostat. So sort of works. At least I can get the temperature from it. But I'm not sure how to controll/ read the output and the two inputs. Also I tried to submit the device definition to indigo but the form doesn't seem to accept it. Yes, I do invoke it from the server computer.

Here is the log as it is being added (other entries removed):

controller included module: 037 - General Thermostat (v2)
Z-Wave stopped controller inclusion mode
Z-Wave Syncing - started for "037 - General Thermostat (v2)"
Z-Wave Syncing - retrieved module neighbors list: 2, 5, 7, 11, 14, 16, 18, 22, 30
Z-Wave Syncing - assigning return route to "037 - General Thermostat (v2)"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Qubino - 0159, General Thermostat (v2) - 00050051
Z-Wave Syncing - retrieved protocol version 4.05, app version 5.02
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Thermostat : General Thermostat (v2) (04 : 08 : 06, base 40)
Z-Wave Syncing - retrieved command classes: 20v1 40v1 43v1 85v1 86v1 27v1 32v4 8Ev1 70v1 31v7 72v1 73v1 59v1 5Av1 5Ev1
Z-Wave Syncing - retrieved encrypt commands: - none -
Z-Wave Syncing - retrieved capabilities: routing, beaming
Z-Wave Syncing - retrieved group 1 associations: []
Z-Wave Syncing - retrieved group 2 associations: []
Z-Wave Syncing - retrieved group 3 associations: []
Z-Wave Syncing - retrieved group 4 associations: []
Z-Wave Syncing - retrieved group 5 associations: []
Z-Wave Syncing - retrieved group 6 associations: []
Z-Wave Syncing - retrieved group 7 associations: []
Z-Wave Syncing - retrieved group 8 associations: []
Z-Wave Syncing - retrieved group 9 associations: []
Z-Wave Syncing - retrieved group 10 associations: []
Z-Wave Syncing - added group 1 association to interface
SQL Logger creating table device_history_1789669507 for "037 - General Thermostat (v2)"
Z-Wave Syncing - created device "037 - General Thermostat (v2)"
Z-Wave Syncing - complete
SQL Logger adding column "accumenergytimedelta" to table device_history_1789669507 ("037 - General Thermostat (v2)")
SQL Logger adding column "accumenergytotal" to table device_history_1789669507 ("037 - General Thermostat (v2)")
SQL Logger adding column "curenergylevel" to table device_history_1789669507 ("037 - General Thermostat (v2)")
Z-Wave sent "037 - General Thermostat (v2)" mode status request
Z-Wave received "037 - General Thermostat (v2)" mode is off
SQL Logger adding column "hvacoperationmode_ui" to table device_history_1789669507 ("037 - General Thermostat (v2)")
Z-Wave sent "037 - General Thermostat (v2)" temperature status request
Z-Wave received "037 - General Thermostat (v2)" temperature update to 23.6 °C
Z-Wave received "037 - General Thermostat (v2)" units changed to °C
SQL Logger adding column "temperatureinput1_ui" to table device_history_1789669507 ("037 - General Thermostat (v2)")
Z-Wave sent "037 - General Thermostat (v2)" heat setpoint status request
Z-Wave received "037 - General Thermostat (v2)" heat setpoint is 23.0 °C
SQL Logger adding column "setpointheat_ui" to table device_history_1789669507 ("037 - General Thermostat (v2)")
Z-Wave sent "037 - General Thermostat (v2)" cool setpoint status request
Z-Wave Error rcvd incomplete interface packet: 01 0A 00 04 00 25 04 43 03 02 00 92 (missing 1 bytes)

peszko wrote:

I don't like being the first one, but really could use a temperature sensor with external probe. (Pool, sauna, hot tub, fridge). I might take a plunge so I can send you the device report. Are there any other z-wave devices that would have an external temperature probe and work with Indigo.

You could always use a pi zero as they have waterproof temperature probes and use pibeacon.

Unless you are using those probes already?

siclark wrote:

You could always use a pi zero as they have waterproof temperature probes and use pibeacon.

Interesting idea. Although still seems like a complicated setup to just read temperature.

Although not 100% supported (indigo treats it as a thermostat, which I guess in some way it is), Indigo can read temperature from the Qubino. So this is a natively supported solution. Qubino has an external probe and it is using the standard DS18B20 temperature sensor, so plenty of them around in all kind of configurations including plumbing threaded ones.

But I need to setup a raspberry pi to investigate lots of other things it can do together with pibeacon.

Every time, I initiate status request to the module, I get the following error:

Code: Select all

   Z-Wave                          sent "BY_Pool_In_TEMP" temperature status request
   Z-Wave                          received "BY_Pool_In_TEMP" temperature update to 30.6 °C
   Trigger                         BY_PoolTempChangeVar_TR
   Z-Wave                          sent "BY_Pool_In_TEMP" heat setpoint status request
   Z-Wave                          received "BY_Pool_In_TEMP" heat setpoint is 23.0 °C
   Z-Wave                          sent "BY_Pool_In_TEMP" cool setpoint status request
   Z-Wave Error                    rcvd incomplete interface packet: 01 0A 00 04 00 26 04 43 03 02 00 91 (missing 1 bytes)


Which version of Indigo Server are you running?

matt (support) wrote:

Which version of Indigo Server are you running?

7.4.1.

I believe the latest.

So from the technical docs I found for this one (PDF Manual) it looks like it supports operating either as a heating-only thermostat or a cooling-only thermostat. I think it defaults to heating, so when Indigo tries to ask for the cool setpoint it is returning a packet Indigo cannot handle. I imagine if you change parameter #59 from 0 to 1 (using Interfaces->Z-Wave->Modify Configuration Parameter... menu), you would then get an error when Indigo sends the status request for the heat setpoint (and cool setpoint will work). Can you try that and see?

Regardless, I believe you can just ignore the error message in this case. It looks like it is reading both the temperature and the setpoint value out correctly (at least for the heat setpoint).

What does Indigo show occurs when you press the switch? Does that control turning the heat or valve ON/OFF, and does Indigo reflect that somehow?

Right on the cool/heat set point. After changing the parameter I now get the error on heat setpoint:

Code: Select all

   Z-Wave                          sent "L4_Attic_TEMP_Z" heat setpoint status request
   Z-Wave Error                    rcvd incomplete interface packet: 01 0A 00 04 00 25 04 43 03 01 00 91 (missing 1 bytes)
   Z-Wave                          sent "L4_Attic_TEMP_Z" cool setpoint status request
   Z-Wave                          received "L4_Attic_TEMP_Z" cool setpoint is 23.0 °C
   SQL Logger                      adding column "setpointcool_ui" to table device_history_1789669507 ("L4_Attic_TEMP_Z")

If I change the cools set point, it shows up in indigo, and is returned correctly when the module is queried.

In the end, I only want to read the temperature using an external probe, and it works properly for that. I just really don't like to see errors in the logs. Is there a way to tell indigo to ignore this and not log it?