Qubino Z-Wave weather station ZMNHZD1

I tested to include the ZMNHZD1 into Z-Way server that I run on my PC under Windows 10 and with the Z-Wave.me UZB stick.

The only difference I see is that I can now get temp and humidity to work for channel 2 (which did not work in Indigo) and that I can also get humidity for channel 1 (which did not work in Indigo either).
However, Z-Way server has the same problem with not receiving any data at all for the rain or wind sensors.

In Z-Way server the Indigo equivalent sync process is called Device Interview and the "interview" takes a long time and I can see in the log there are some packets that seems to be erroneously formatted causing the interview to not complete in full. I can see the interview details in Z-Way server for each command class and Z-Way server seems to have problems to complete the interview for the version info for each node.

With both now Indigo and Z-Way server having problems with this device and as I have seen, people using Domoticz (see my link above) also having problems then all this points towards a device that does not follow its own documented protocol or a firmware bug.

I have emailed Qubino support yesterday but no response back yet.

[matt (support)]

Indigo should be able to catch all the data sent by the ZMNHZD that you are seeing on the Windows machine. Do you have any logs you can copy/paste that show the raw bytes that are being received there?

It is possible that Indigo's device definition isn't correct and it isn't matching the incoming data correctly to the devices it has created. However, you should still see the data coming in if you have the debug logging turned on. That said, based on the ZMNHZD1's manual, it sounds like it only sends the data if it has changed from the previous value. So maybe just because the ZMNHZD1's LED blinks showing it has received sensor data doesn't necessarily mean it has then relayed that data onto the Z-Wave network.

Have you tried running Indigo with debug logging on for an extended period of time (hours) just to make sure there isn't some additional data coming from the ZMNHZD?

We´ll I am not seeing that much more on the Windows machine and the logging there does not show raw bytes there even if I run in debug mode.

I have also made sure to turn the wind sensor around to generate changing data and I have also moved around both temp sensors ch 1 and ch 2 to create changing temps and humidity but still no events in the Indigo log in debug mode.

I have included back the device into Indigo yesterday and run Z-Wave in debug mode for maaaany hours and the only raw bytes for node 213 (D5) I see in the Z-Wave log in debug mode are the following:

-----
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 D5 06 31 05 01 22 00 ED DE
Z-Wave Debug . . requestVarSensorStatus: node 213, endpoint None, type 1, raw value 2200...
Z-Wave Debug . . requestVarSensorStatus: 23.7 °C (float: 23.700000)
Z-Wave received "213 - Temp 1" sensor update to 23.7 °C

-----

Strange that it first of all points to endpoint = None? According to the manual the temp for channel 1 should be endpoint 1.

Just to be sure I did a search for 01 0C 00 04 00 D5 in the whole log file but the only hits I get are the one I listed above.

I am including the full inclusing log from my Windows machine running Z-Way server and I am also including the inclusion long when including the device into Indigo.
If you search in the Z-Way server log for the text "error" you should be able to find the following strange Z-Wave error:

-----
"Error returned from _zway_cc_call_handler(zway, cmd, node_id, data[3], length - 4, &data[4]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)"
-----

I don´t see them in the Indigo inclusion log though. Remember also that I am experiencing quite much syncing ("interview") problems in my Windows machine as well when I am trying to create the device in Z-Way Server on my Windows machine. This weather station ZMNHZD1 is indeed doing something strange/erroneous/odd.

I have attached the full inclusion log in debug mode for Indigo Domotics as well. (Device node id is 212 in this log while it is 213 in the log printout above.)
Looking in that log it does look like Indigo creates 10 endpoints when syncing in the device:

-----
Z-Wave Syncing - retrieved multi-endpoint types: 1:(21 : 01), 2:(21 : 01), 3:(21 : 01), 4:(21 : 01), 5:(21 : 01), 6:(21 : 01), 7:(21 : 01), 8:(21 : 01), 9:(21 : 01), 10:(21 : 01)
Z-Wave Syncing - retrieved multi-endpoint classes: 1:[5E 86 31 85 8E 59 80], 2:[5E 86 31 85 8E 59 80], 3:[5E 86 31 85 8E 59 80], 4:[5E 86 31 85 8E 59 80], 5:[5E 86 31 85 8E 59 80], 6:[5E 86 31 85 8E 59 80], 7:[5E 86 31 85 8E 59 80], 8:[5E 86 31 85 8E 59 80], 9:[5E 86 31 85 8E 59 80], 10:[5E 86 31 85 8E 59 80]

-----

[matt (support)]

That is strange that the temperature value doesn't come in on endpoint 1, as the instructions say it will.

One thing to try, which is a long shot, would be to modify the config parameters #1 to #14 and set them all to 0 (disable reports). After that, presuming it doesn't suddenly start working, try setting them all back to 1 to enable them. Maybe it just needs a swift kick in the shins to start working?

Hopefully Qubino support will have some suggestions...

I did as you suggested but unfortunately no difference. Only temp for ch 1 updating.

I excluded the device from my PROD system and included it into my DEV machine where I also now have Indigo 7.0.2. On the DEV machine I have the newer Aeon Labs Gen5/S5 USB Z-Wave stick.
No difference there either. Still the same issue.

I have received back an answer from Qubino now.

They tested first with the open source system Domoticz and experienced similar problems as we have here in the Indigo system. They can see both temp and humidity sensors though but not the wind and rain sensors. Their explanation to that is that Domoticz might be using an older version of the OpenZWave library.
See attached screenshot no 1 for the above test.

After that they tested with Zensys Tool from Aeon Labs (runs only on Windows machines) and they see the data attached in the second screenshot.

Then they tested with OpenZWave Control Panel (version v0.2a 8/8/2011) together with the latest OpenZWave library (version 1.4.2261) and they sent me the full inclusion log for that (attached here as file number 3) as well as a screenshot showing that they indeed receive updates for all sensors (attached as file number 4).

I will do the same test here during the weekend and compile OpenZWave library 1.4.2261 on my Ubuntu machine and the use OpenZWave Control Panel to do the inclusion of the weather station and see if I get the same results as they did.

[matt (support)]

That would be great if you could try it with OZW. The screenshots they sent you look great – that is exactly the data Indigo wants to see, but isn't.

If you can get it working with OZW then I'm confident we can get Indigo working with it. The only thing that jumps out at me that OZW is doing that Indigo doesn't do is polling the values out of the module during the sync. Perhaps the ZMNHZD1 needs that before it starts broadcasting out changes. It shouldn't, but maybe that is the issue with the ZMNHZD1.

Let us know how it goes...

Alright, it was somewhat troublesome to get Open-Zwave-Control-Panel (OZWCP) compiled without problems on my Ubuntu machine (I am no good at Linux! ).
After successful compilation of OpenZWave library first (that was the easy part) and then compilation of OZWCP I was also eventually able to connect the OZWCP to the Z.Wave.ME UZB1 Z-wave stick that I am testing with on the Ubuntu machine.

As soon as I had OZWCP working properly there was no issue at all to include the ZMNHZDx into OZWCP and the Z-Wave.ME UZB1 stick.
I also get updates for all 10 endpoints (sensors) without problems and they also show proper values.

I have attached the FULL inclusion log from OpenZwave.

Here is some examples from the OZWCP log file where you can see update events for all 10 sensors (10 endpoints):

2016-11-27 15:39:53.871 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x02, 0x01, 0x31, 0x05, 0x07, 0x22, 0x03, 0x84, 0x1b
2016-11-27 15:39:53.871 Detail,
2016-11-27 15:39:53.871 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 2 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 15:39:53.871 Info, Node002, Received SensorMultiLevel report from node 2, instance 2, Direction: value=90.0
2016-11-27 15:39:53.871 Detail, Node002, Refreshed Value: old value=22.5, new value=90.0, type=decimal
2016-11-27 15:39:53.871 Detail, Node002, Changes to this value are not verified
2016-11-27 15:39:53.871 Detail, Node002, Notification: ValueChanged
2016-11-27 15:39:53.871 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 2 Index 7 Type decimal
node = 2 id = 1 value = 23.7 precision = 1 ###(this is ch 1 temp, degrees Celsius)
node = 2 id = 2 value = 22.3 precision = 1 ###(this is wind gauge temp, i.e. = outdoor temp, degrees Celsius)
node = 2 id = 3 value = 22.3 precision = 1 ###(this is wind chill temp, degrees Celsius)
node = 2 id = 4 value = 15.1 precision = 1 ###(this is ch 2 temp, degrees Celsius)
node = 2 id = 5 value = 28 precision = 0 ###(this is ch 1 humidity, %)
node = 2 id = 6 value = 42 precision = 0 ###(this is ch 2 humidity, %)
node = 2 id = 7 value = 0.13 precision = 2 ###(this is wind velocity, meter per second)
node = 2 id = 8 value = 0.80 precision = 2 ###(this is wind gust, meter per second)
node = 2 id = 9 value = 90.0 precision = 1 ###(this is wind direction, degrees)
node = 2 id = 10 value = 126.30 precision = 2 ###(this is rain rate, mm per hour)

Here are some log examples for each of the endpoints how they look like in the log when they receive updates:

Endpoint 1, id 1 above (temp ch 1 in degrees Celsius):
2016-11-27 17:08:58.923 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x01, 0x01, 0x31, 0x05, 0x01, 0x22, 0x00, 0xf0, 0x69
2016-11-27 17:08:58.923 Detail,
2016-11-27 17:08:58.923 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 1 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 17:08:58.924 Info, Node002, Received SensorMultiLevel report from node 2, instance 1, Temperature: value=24.0C
2016-11-27 17:08:58.924 Detail, Node002, Initial read of value
2016-11-27 17:08:58.924 Detail, Node002, Notification: ValueChanged
2016-11-27 17:08:58.924 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 1 Index 1 Type decimal



Endpoint 2, id 9 above (wind direction in degrees):
2016-11-27 16:46:57.384 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x02, 0x01, 0x31, 0x05, 0x07, 0x22, 0x07, 0x08, 0x93
2016-11-27 16:46:57.384 Detail,
2016-11-27 16:46:57.384 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 2 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 16:46:57.384 Info, Node002, Received SensorMultiLevel report from node 2, instance 2, Direction: value=180.0
2016-11-27 16:46:57.384 Detail, Node002, Refreshed Value: old value=157.5, new value=180.0, type=decimal
2016-11-27 16:46:57.384 Detail, Node002, Changes to this value are not verified
2016-11-27 16:46:57.384 Detail, Node002, Notification: ValueChanged
2016-11-27 16:46:57.384 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 2 Index 7 Type decimal


Endpoint 3, id 7 above (Wind gauge velocity in meters per second):
2016-11-27 16:50:55.844 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x03, 0x01, 0x31, 0x05, 0x06, 0x42, 0x00, 0x50, 0xac
2016-11-27 16:50:55.844 Detail,
2016-11-27 16:50:55.844 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 3 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 16:50:55.844 Info, Node002, Received SensorMultiLevel report from node 2, instance 3, Velocity: value=0.80m/s
2016-11-27 16:50:55.844 Detail, Node002, Refreshed Value: old value=0.89, new value=0.80, type=decimal
2016-11-27 16:50:55.844 Detail, Node002, Changes to this value are not verified
2016-11-27 16:50:55.845 Detail, Node002, Notification: ValueChanged
2016-11-27 16:50:55.845 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 3 Index 6 Type decimal


Endpoint 4, id 8 above (Wind gust in meters per second):
2016-11-27 17:06:46.677 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x04, 0x01, 0x31, 0x05, 0x06, 0x42, 0x01, 0x80, 0x7a
2016-11-27 17:06:46.677 Detail,
2016-11-27 17:06:46.677 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 4 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 17:06:46.677 Info, Node002, Received SensorMultiLevel report from node 2, instance 4, Velocity: value=3.84m/s
2016-11-27 17:06:46.677 Detail, Node002, Initial read of value
2016-11-27 17:06:46.678 Detail, Node002, Notification: ValueChanged
2016-11-27 17:06:46.678 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 4 Index 6 Type decimal


Endpoint 5, id 2 above (Wind gauge temp, i.e. outdoor temp, degrees Celsius):
2016-11-27 16:50:53.840 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x05, 0x01, 0x31, 0x05, 0x01, 0x22, 0x00, 0xee, 0x73
2016-11-27 16:50:53.841 Detail,
2016-11-27 16:50:53.841 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 5 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 16:50:53.841 Info, Node002, Received SensorMultiLevel report from node 2, instance 5, Temperature: value=23.8C
2016-11-27 16:50:53.841 Detail, Node002, Refreshed Value: old value=23.9, new value=23.8, type=decimal
2016-11-27 16:50:53.841 Detail, Node002, Changes to this value are not verified
2016-11-27 16:50:53.841 Detail, Node002, Notification: ValueChanged
2016-11-27 16:50:53.841 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 5 Index 1 Type decimal

Endpoint 6, id 3 above (wind chill in degrees Celsius)
2016-11-27 16:50:54.842 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x06, 0x01, 0x31, 0x05, 0x01, 0x22, 0x00, 0xee, 0x70
2016-11-27 16:50:54.842 Detail,
2016-11-27 16:50:54.842 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 6 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 16:50:54.842 Info, Node002, Received SensorMultiLevel report from node 2, instance 6, Temperature: value=23.8C
2016-11-27 16:50:54.842 Detail, Node002, Refreshed Value: old value=23.9, new value=23.8, type=decimal
2016-11-27 16:50:54.843 Detail, Node002, Changes to this value are not verified
2016-11-27 16:50:54.843 Detail, Node002, Notification: ValueChanged
2016-11-27 16:50:54.843 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 6 Index 1 Type decimal

Endpoint 7, id 10 above (Rain rate in millimeter per hour):
2016-11-27 16:48:01.507 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x07, 0x01, 0x31, 0x05, 0x0c, 0x42, 0x00, 0x00, 0xf2
2016-11-27 16:48:01.507 Detail,
2016-11-27 16:48:01.507 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 7 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 16:48:01.507 Info, Node002, Received SensorMultiLevel report from node 2, instance 7, Rain Rate: value=0.00mm/h
2016-11-27 16:48:01.507 Detail, Node002, Refreshed Value: old value=14.00, new value=0.00, type=decimal
2016-11-27 16:48:01.507 Detail, Node002, Changes to this value are not verified
2016-11-27 16:48:01.508 Detail, Node002, Notification: ValueChanged
2016-11-27 16:48:01.508 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 7 Index 12 Type decimal

Endpoint 8, id 5 above (ch 1 humidity in percent):
2016-11-27 17:04:33.426 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x08, 0x01, 0x31, 0x05, 0x05, 0x02, 0x00, 0x1d, 0xa9
2016-11-27 17:04:33.426 Detail,
2016-11-27 17:04:33.426 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 8 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 17:04:33.427 Info, Node002, Received SensorMultiLevel report from node 2, instance 8, Relative Humidity: value=29%
2016-11-27 17:04:33.427 Detail, Node002, Initial read of value
2016-11-27 17:04:33.427 Detail, Node002, Notification: ValueChanged
2016-11-27 17:04:33.427 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 8 Index 5 Type decimal


Endpoint 9, id 4 above (temp ch 2 in degrees Celsius):
2016-11-27 16:46:44.357 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x09, 0x01, 0x31, 0x05, 0x01, 0x22, 0x00, 0xd6, 0x47
2016-11-27 16:46:44.357 Detail,
2016-11-27 16:46:44.357 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 9 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 16:46:44.357 Info, Node002, Received SensorMultiLevel report from node 2, instance 9, Temperature: value=21.4C
2016-11-27 16:46:44.357 Detail, Node002, Refreshed Value: old value=21.3, new value=21.4, type=decimal
2016-11-27 16:46:44.357 Detail, Node002, Changes to this value are not verified
2016-11-27 16:46:44.357 Detail, Node002, Notification: ValueChanged
2016-11-27 16:46:44.357 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 9 Index 1 Type decimal


Endpoint 10, id 6 above (ch 2 humidity in percent):
2016-11-27 16:49:00.621 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x60, 0x0d, 0x0a, 0x01, 0x31, 0x05, 0x05, 0x02, 0x00, 0x23, 0x95
2016-11-27 16:49:00.621 Detail,
2016-11-27 16:49:00.621 Info, Node002, Received a MultiChannelEncap from node 2, endpoint 10 for Command Class COMMAND_CLASS_SENSOR_MULTILEVEL
2016-11-27 16:49:00.621 Info, Node002, Received SensorMultiLevel report from node 2, instance 10, Relative Humidity: value=35%
2016-11-27 16:49:00.621 Detail, Node002, Refreshed Value: old value=36, new value=35, type=decimal
2016-11-27 16:49:00.621 Detail, Node002, Changes to this value are not verified
2016-11-27 16:49:00.621 Detail, Node002, Notification: ValueChanged
2016-11-27 16:49:00.621 Info, Notification: Value Changed Home 0xc02f7c21 Node 2 Genre user Class SENSOR MULTILEVEL Instance 10 Index 5 Type decimal

[matt (support)]

Great info. When you were trying it with Indigo were you using the same Z.Wave.ME UZB1 controller?

If you now move the Z.Wave.ME UZB1 over to your Mac and create a new device for the already included ZMNHZDx, does Indigo then show the incoming sensor data (and work)? That is, is it something that OZW is doing during its initial sync that is causing it to now work? Note you might want to create a new empty Indigo database if you are moving the UZB1 over to your Mac and it doesn't have all of your normal Z-Wave devices included. Otherwise, Indigo will notice the mismatch between all your Indigo Devices and what is included in the UZB1 and disable communication with most of your devices.

Nope, on my Indigo DEV I was using Aeon Labs USB Gen5 stick.
On my Indigo PROD I am using the old generation S2 USB stick from Aeon Labs.

I moved the Z.Wave.ME UZB1 from my Ubuntu machine to my Indigo DEV machine (running 7.0.2) and created an empty database.

Synced in the ZMNHZD1 and you know whaaaat!!?? I get sensor values for ALL endpoints now!

Sensor value for Wind Direction seems correction but it should also say "degrees" or the ° symbol.
Sensor value for Rain Fall Rate is displayed as 126.30 Degrees Celsius when it should be 126.30 mm/hr (millimeter per hour)

I am attaching the sync log into Indigo from the Z.WaveME UZB1 stick as well as some log outputs from Indigo that shows sensor updates.

[matt (support)]

Okay, so there is some magic command the Qubino is expecting to receive that gets it into a mode where it actually sends out the values. I don't know what that is yet, but I'll look over the OZW logs and see if I can guess what it might be. Did I mention these Qubino modules are a bit of an integration nightmare?

And I'll get the Wind Direction and Rain Fall Rate buglets fixed.

[matt (support)]

Here is a new new version of Indigo's Z-Wave plugin that will attempt to send the magic multi-instance-association command that gets the ZMNHZD to broadcast out all changes correctly. I know you have this one working now after setting it up in OZW, but if you want to try excluding/re-including it to see if Indigo can get it working from scratch then let me know the results. Thanks!

Here is a new version of Indigo's Z-Wave plugin that will attempt to send the magic multi-instance-association command that gets the ZMNHZD to broadcast out all changes correctly.

Wohooo that is great! I will test directly when I am back home!

I know you have this one working now after setting it up in OZW, but if you want to try excluding/re-including it to see if Indigo can get it working from scratch then let me know the results. Thanks!

No problem! I used OZW only to test the device and I sometimes use OZW to test new devices that not yet has support in Indigo.
Looking forward to test the new Z-Wave plugin tonight and hopefully we can get the ZMNHZDx to work properly in Indigo soon so that I finally can climb up on the roof of my house and mount the wind sensor there..

@Matt:
Sorry but now with the latest version of the Z-Wave plugin (2.0.40) I can sync in the ZMNHZD1 without problems but I do not get ANY updates in the debug log.

The difference now compared to the testing earlier above is that when it worked on my Mac DEV environment with the ZWave.ME UZB1 stick I tested now with the Aeon Labs S2 (old men) USB stick in my PROD environment.

Hmmm could it be that it has to be the newer Wave Plus compatible sticks?

I´ll make another test in my DEV environment with the ZWave.ME UZB1 stick instead. Reporting back in few hours.

(I can provide you with the full inclusion as well as the sync to Indigo log in debug mode if you need it.)


EDIT: Tested now on my DEV machine with the new Z-Wave plugin 2.0.40 and with the Aeon Labs S5 Gen5 USB stick.
Now I am back at square one... I get updates for temp ch 1 but nothing else.

However, seems definitely be something different between a Z-Wave Plus / Gen 5 compatible USB stick compared to the older version (like the Aeon Labs S2 stick) since in this case I get at least updates for temp ch 1.
I notice similar experience with the Sensative Strip door/window sensor that does sync in to Indigo with Gen 5 stick but not with Gen 2 stick (I´ll report that in a separate thread though).

Ok I was able to compile OpenZWave and OpenZWave Control Panel om my DEV Mac Mini (took only whole Saturday to figure it out... )

When that was done and working I excluded the ZMNHZD1 weather station from my Aeon Labs S5 Gen5 stick using Indigo.

Then I stopped Indigo.

I started OZWCP and included the ZMNHZD1 into the stick using Add Node function in OZWCP.
When inclusion was done I started to move around both temp/humidity sensors to trigger temp and humidity changes.
Did the same with the wind sensor, spinned the wind speed sensor and turned around the wind direction sensor.
And finally wobbled the sensor in the rain sensor to simulate rain.

OZWCP displayed proper sensor updates.

I then stopped OZWCP and started up my Indigo DEV again.
Re-synced the existing ZMNHZD1 device in Indigo to the new Node ID and voilaaaaa!
Values are displaying and updates are displaying!

Wind direction and rain rate are now shown with proper units also. Cool!

Must be something in the inclusion process that goes wrong when doing the inclusion in Indigo?

[matt (support)]

Sorry for the slow reply on this, but do you have the Event Log result of the Indigo sync with Z-Wave library (2.0.40 or newer) after the module was reset (excluded/re-included)? I need to dig deeper into what is going wrong with this.