Popp Z-rain

[TheHoff]

Greetings
After my Oregon Scientific 433mhz rain gauge broke I got me a Z-wave rain gauge instead. Seems much more robust than the Oregon one. I've got the Aeon Z-stick connected to my Pi3 running Domoticz beta 4.11590 with one other Z-wave node connected, a Fibaro switch.
Pairing the Z-rain was pretty easy and Domoticz sees it as a rain rate/Custom sensor and rain sensor. However when I test the gauge, a few hours after pairing, by tipping a cup of water into the bucket only the rain rate is updated. The rain amount is not.
Also the Domoticz logs gives the error message when I include the Z-rain gauge, don't know if it's related.
"2020-01-01 13:28:22.390 Error: OpenZWave: Value_Changed: Unhandled value type ZDTYPE_SWITCH_NORMAL (2). Node: 14 (0x0e), CommandClass: SENSOR MULTILEVEL, Label: General Purpose, Instance: 1, Index: 2 (OpenZWave.cpp:3188)"
Any idea what this is?

Regards
/Fredrik

[kevster]

Hi

Did you get any further with this. I'm looking for a new guage too...

[Snowtiger]

It looks like it's interpreting this device as a Switch, 1 value, opposed to it being a Sensor multi level device - 1 instance, 2 index.
The module OpenZwave.cpp can not detect it as a multi level device and therefor throws this error in the specified line number.

Is it Popp product code 700168? If it is, then it is in the Zwave product database.

[lander]

If it's in the Zwave product database it should work, no?

[Snowtiger]

Yes, it should work BTW to be precise - it is the OpenZwave 'database' which is incorporated into Domoticz.

[Abber]

Hi,
How did this end? Does the Popp Z-rain work as expected? Is the rain amount monitoren correctly in Domoticz?
I am considering to buy the Popp z-rain, but fot €80 I want to be sure that the amount of rain is monitored correctly!

Thanks for letting me know!

[mickmack82]

For what it's worth, i use this device for over a year without any problems. Rain rate and total amount of rain is updated as expected.

[Abber]

Thanks Mickmack! Now I dare to invest my €80
Since you are using it for more than a year now, how is the accuracy? Does it register little amounts of rain as well?

[mickmack82]

It reports the rainfall with 0.5mm accuracy. I never compared it to a official rain gauge though. But overall I am quite satisfied with this device.

For the problem above: try to refresh node info. Not only from the ozw panel but also from the domoticz hardware page. That did resolve some zwave errors with other zwave devices generating messages like this.

[Abber]

Ok thanks. I am going to order one.

[mickmack82]

After the update to the 2020 version I also receive the error mentioned in the first post:

Unhandled value type ZDTYPE_SWITCH_NORMAL (2). Node: 15 (0x0f), CommandClass: SENSOR MULTILEVEL, Label: General Purpose, Instance: 1, Index: 2 (OpenZWave.cpp:3189)

However, rainrate and rainfall is updated as it should.
Any progress with this?

[Kyrille]

After the update to the 2020 version I also receive the error mentioned in the first post:

Unhandled value type ZDTYPE_SWITCH_NORMAL (2). Node: 15 (0x0f), CommandClass: SENSOR MULTILEVEL, Label: General Purpose, Instance: 1, Index: 2 (OpenZWave.cpp:3189)

However, rainrate and rainfall is updated as it should.
Any progress with this?

I just discovered this topic and I have exactly the same issue as you. I created a new ticket yesterday (https://www.domoticz.com/forum/viewtopi ... 24&t=32312) and I am still investigating. Even if the device is still working fine, I now receive emails everyday (I want to be warned when Domoticz encounters an error, and it happens for each exchange between the controller and the z-rain).

Regards.

[mickmack82]

Did some more digging and found the following:

The section of code mentioned in the error (line 3188 in OpenZWave.cpp) handles the datatypes bool, byte, string and list.

Code: Select all

if (vType == OpenZWave::ValueID::ValueType_Bool)
			{
				if (bValue == true)
					intValue = 255;
				else
					intValue = 0;
			}
			else if (vType == OpenZWave::ValueID::ValueType_Byte)
			{
				if (byteValue == 0)
					intValue = 0;
				else
					intValue = 255;
			}
			else if (vType == OpenZWave::ValueID::ValueType_String)
			{
				if (commandclass == COMMAND_CLASS_COLOR_CONTROL)
				{
					//New color value received, not handled yet
					return;
				}
			}
			else if (vType == OpenZWave::ValueID::ValueType_List)
			{
				if (commandclass == COMMAND_CLASS_COLOR_CONTROL)
				{
					//Color Index changed, not used
					return;
				}
			}
			else
			{
				_log.Log(LOG_ERROR, "OpenZWave: Value_Changed: Unhandled value type ZDTYPE_SWITCH_NORMAL (%d). Node: %d (0x%02x), CommandClass: %s, Label: %s, Instance: %d, Index: %d (%s:%d)", vType, NodeID, NodeID, cclassStr(commandclass), vLabel.c_str(), vID.GetInstance(), vID.GetIndex(), std::string(__MYFUNCTION__).substr(std::string(__MYFUNCTION__).find_last_of("/\\") + 1).c_str(), __LINE__);
				return;
			}

However the datatype defined in Config/popp/700168.xml, for index 1 is "short". All other indexes have datatype "byte".

Code: Select all

<Value genre="config" index="1" instance="1" label="Rain Counter" max="32000" min="0" size="2" type="short" units="mm" value="0">
      <Help>
				Ths values shows the total count of rain from the moment of inclusion in mm water level. By writing this value this counter can be reset.
				Default Value: 0
			</Help>
    </Value>
    <Value genre="config" index="2" instance="1" label="Rain Start Command" max="99" min="0" size="1" type="byte" units="" value="99">
      <Help>
				This BASIC Set Command value is sent out into Association Group 2 when the device detects start of rain.
				Default Value: 99
			</Help>
    </Value>

Could it be that index 1, which has "short" as a datatype is causing this error?
The error message mentions index 2, but that index has "byte" as datatype, so that should be ok.

[mickmack]

This issue is fixed in the latest beta.

Verstuurd vanaf mijn Nokia 8.1 met Tapatalk

[commentator]

Greetings
After my Oregon Scientific 433mhz rain gauge broke I got me a Z-wave rain gauge instead. Seems much more robust than the Oregon one. I've got the Aeon Z-stick connected to my Pi3 running Domoticz beta 4.11590 with one other Z-wave node connected, a Fibaro switch.
Pairing the Z-rain was pretty easy and Domoticz sees it as a rain rate/Custom sensor and rain sensor. However when I test the gauge, a few hours after pairing, by tipping a cup of water into the bucket only the rain rate is updated. The rain amount is not.
Also the Domoticz logs gives the error message when I include the Z-rain gauge, don't know if it's related.
"2020-01-01 13:28:22.390 Error: OpenZWave: Value_Changed: Unhandled value type ZDTYPE_SWITCH_NORMAL (2). Node: 14 (0x0e), CommandClass: SENSOR MULTILEVEL, Label: General Purpose, Instance: 1, Index: 2 (OpenZWave.cpp:3188)"
Any idea what this is?

Regards
/Fredrik

had one for a year, then it stopped working when it was raining 55mm/hour. It was complete wet inside the device

[Solderbro]

Let's figure that out, i changes the term in the popp file to byte and will see what happens. Because this bug is the major annoying thing, you have to total disable the email alerts or it spam your inbox every 5 minutes with the popp error.

General question, can we download beta and extract only the bugged files for the stable?

Solderbro