Qubino ZMNHAD1 problem

For Z-Wave related questions in Domoticz

Moderator: leecollings

Forum rules
Post Reply
alveman
Posts: 21
Joined: Wednesday 29 January 2014 22:42
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:
Contact alveman

Qubino ZMNHAD1 problem

Post by alveman »

Hello,

I'm new to Z-wave, and can't really say if this is a problem or not. In my log after starting up I get this.

Code: Select all

2015-11-23 17:17:02.980 OpenZWave: Starting... 
 2015-11-23 17:17:02.980 OpenZWave: Version: 1.3-550-g4a2b2e5 
 2015-11-23 17:17:02.980 OpenZWave: using config in: /home/pi/domoticz/Config/ 
 2015-11-23 17:17:03.263 OpenZWave: Driver Ready 
 2015-11-23 17:17:03.317 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SENSOR ALARM, Label: Heat, Instance: 1 
 2015-11-23 17:17:03.322 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1 
 2015-11-23 17:17:03.324 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SWITCH BINARY, Label: Switch, Instance: 2 
 2015-11-23 17:17:03.326 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0 
 2015-11-23 17:17:03.328 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 2 
 2015-11-23 17:17:03.330 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 3 
 2015-11-23 17:17:03.332 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 1 
 2015-11-23 17:17:03.333 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SENSOR MULTILEVEL, Label: Temperature, Instance: 2 
 2015-11-23 17:17:03.333 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: METER, Label: Energy, Instance: 1 
 2015-11-23 17:17:03.334 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: METER, Label: Energy, Instance: 2 
 2015-11-23 17:17:03.335 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: METER, Label: Power, Instance: 1 
 2015-11-23 17:17:03.336 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: METER, Label: Power, Instance: 2 
 2015-11-23 17:17:03.340 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Type, Instance: 1 
 2015-11-23 17:17:03.342 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Level, Instance: 1 
 2015-11-23 17:17:03.344 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Type, Instance: 2 
 2015-11-23 17:17:03.346 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Level, Instance: 2 
 2015-11-23 17:17:03.348 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Type, Instance: 3 
 2015-11-23 17:17:03.350 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Alarm Level, Instance: 3 
 2015-11-23 17:17:03.352 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: SourceNodeId, Instance: 1 
 2015-11-23 17:17:03.352 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Clock, Instance: 1 
 2015-11-23 17:17:03.354 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: SourceNodeId, Instance: 2 
 2015-11-23 17:17:03.355 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: System, Instance: 2 
 2015-11-23 17:17:03.357 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Emergency, Instance: 2 
 2015-11-23 17:17:03.358 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Clock, Instance: 2 
 2015-11-23 17:17:03.360 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: HomeHealth, Instance: 2 
 2015-11-23 17:17:03.362 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: SourceNodeId, Instance: 3 
 2015-11-23 17:17:03.363 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Power Management, Instance: 3 
 2015-11-23 17:17:03.365 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: System, Instance: 3 
 2015-11-23 17:17:03.367 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Emergency, Instance: 3 
 2015-11-23 17:17:03.368 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: Clock, Instance: 3 
 2015-11-23 17:17:03.370 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: ALARM, Label: HomeHealth, Instance: 3
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
2015-11-23 17:17:19.878 OpenZWave: Received timeout notification from HomeID: 3235865076, NodeID: 4 (0x04)
It looks like all the parameters comes several times. And in the OpenZwave control panel it look really strange. I have tried removing the nod and reconnecting it. But it’s coming back all the same. This started after a Domoticz update last week.

Anyone having the problem?

Martin
Attachments
Skarmklipp.PNG
Skarmklipp.PNG (43.06 KiB) Viewed 2671 times
Top
User avatar
gizmocuz
Posts: 2363
Joined: Thursday 11 July 2013 18:59
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Top of the world
Contact:
Contact gizmocuz

Re: Qubino ZMNHAD1 problem

Post by gizmocuz »

Did you try excluding/including this node again?
Quality outlives Quantity!
Top
zofiel
Posts: 30
Joined: Sunday 19 July 2015 10:03
Target OS: -
Domoticz version:
Contact:
Contact zofiel

Re: Qubino ZMNHAD1 problem

Post by zofiel »

same problem here.

EDIT: Sorry, my problem is with ZMNHDD1

I reinstalled domoticz today. All ok but the dimmer dead after a minute
Last edited by zofiel on Tuesday 24 November 2015 10:34, edited 1 time in total.
Top
alve
Posts: 2
Joined: Monday 29 December 2014 23:21
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:
Contact alve

Re: Qubino ZMNHAD1 problem

Post by alve »

Yes, I have tryed excluding/including but it is all the same.


Skickat från min iPhone med Tapatalk
Top
alveman
Posts: 21
Joined: Wednesday 29 January 2014 22:42
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:
Contact alveman

Re: Qubino ZMNHAD1 problem

Post by alveman »

Hey, I wonder how the amount of energy measurement work on these Qubino relays. I get two different meter that reports values. But both reports only instantaneous values, not accumulated. Must it be so? Do I have to solve the accumulated through script or dose this works for everyone else?
Attachments
This accumulated energy came in when I the same day I updated Domoticz
This accumulated energy came in when I the same day I updated Domoticz
Skärmklipp3.PNG (81.92 KiB) Viewed 2572 times
Skärmklipp2.PNG
Skärmklipp2.PNG (88.21 KiB) Viewed 2572 times
Skärmklipp1.PNG
Skärmklipp1.PNG (11.63 KiB) Viewed 2572 times
Top
User avatar
bbqkees
Posts: 407
Joined: Sunday 17 August 2014 21:01
Target OS: Linux
Domoticz version: 4.1x
Location: The Netherlands
Contact:
Contact bbqkees

Re: Qubino ZMNHAD1 problem

Post by bbqkees »

zofiel wrote:same problem here.

EDIT: Sorry, my problem is with ZMNHDD1

I reinstalled domoticz today. All ok but the dimmer dead after a minute
If you have a Aeotec S2 stick this dimmer will not work. Qubino themselves are going to create their own OpenZWave config files in Q1-2016 so I hope this will solve everything.
alveman wrote:Hey, I wonder how the amount of energy measurement work on these Qubino relays. I get two different meter that reports values. But both reports only instantaneous values, not accumulated. Must it be so? Do I have to solve the accumulated through script or dose this works for everyone else?
The accumulated energy stopped working correctly on my Qubino dimmers when the 'general kWh meter' was changed in Domoticz a few months ago.
Before it worked just fine.
Bosch / Nefit / Buderus / Junkers / Worcester / Sieger EMS bus Wi-Fi MQTT Gateway and interface boards: https://bbqkees-electronics.nl/
Top
User avatar
Egregius
Posts: 2582
Joined: Thursday 09 April 2015 12:19
Target OS: Linux
Domoticz version: v2024.7
Location: Beitem, BE
Contact:
Contact Egregius

Re: Qubino ZMNHAD1 problem

Post by Egregius »

bbqkees wrote:Qubino themselves are going to create their own OpenZWave config files in Q1-2016 so I hope this will solve everything.
That's good news :D
Keep us informed if you hear anything ;)
Top
alve
Posts: 2
Joined: Monday 29 December 2014 23:21
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:
Contact alve

Re: Qubino ZMNHAD1 problem

Post by alve »

Thanx for update, see you next year


Skickat från min iPhone med Tapatalk
Top
jeey
Posts: 3
Joined: Thursday 03 March 2016 22:20
Target OS: Linux
Domoticz version:
Contact:
Contact jeey

Re: Qubino ZMNHAD1 problem

Post by jeey »

Old thread, but noticed the OP has problems with timeouts here also.

I noticed that new ZMNHAD1 files where merged on 01.02.16 on github https://github.com/domoticz/domoticz/bl ... MNHAD1.xml

Anyone else experiences problems with timeouts on this hardware?
Kinda annoying sometimes as it takes domoticz a few secs to turn off the light

Domoticz log:

Code: Select all

2016-03-03 22:23:32.977 OpenZWave: Received timeout notification from HomeID: xxxxx, NodeID: 10 (0x0a)
)
OpenZwave log:

Code: Select all

2016-03-03 22:27:39.034 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2016-03-03 22:27:39.034 Always, 
2016-03-03 22:27:39.035 Always, Dumping queued log messages
2016-03-03 22:27:39.035 Always, 
2016-03-03 22:27:39.035 Always, 
2016-03-03 22:27:39.035 Always, End of queued log message dump
2016-03-03 22:27:39.035 Always,
Top
Gravityz
Posts: 583
Joined: Wednesday 16 December 2015 19:13
Target OS: NAS (Synology & others)
Domoticz version: 2022.2
Location: Netherlands
Contact:
Contact Gravityz

Re: Qubino ZMNHAD1 problem

Post by Gravityz »

i tried mine.

i have had timeouts from the start but i always figured this was because this module is far away.
the switch however goes instantly on and off.

i however experienced something strange lately.
i was trying to solve a problem and deleted the complete zwcfgxxxx file.
after that the zmnhad1 came online again but the temp sensors(i have 2 entries) were not working anymore.

i deleted them, did a reset and one came back, the other not.
after playing with it for a couple of hours i suddenly got temp sensor 2 back.

Now here's the thing.

before all this i noticed that if i gave the temp an offset the 2 temperatures were not always the same
somwetimes temp 1 was exactly the offset lower(eg 0.4 degrees lower)
after a couple of minutes they were the same

now if you look at the grapfic of temp1 you see all these spikes. These spikes are caused by the temp offset. it sometimes looses the ofset
temp2 however is very smooth and never looses the offset.

here is my thought.
at first when you include the zmnhad1 you only get 1 temp.
after changing the offset you get the second one(temp2) who represends the temp+offset.

really strange behavoir

i also inspected the xml files and some things have changed but not things who could have caused this.
temp2.jpg
temp2.jpg (92.34 KiB) Viewed 2295 times
temp1.jpg
temp1.jpg (99.76 KiB) Viewed 2295 times
Top
Post Reply

Return to “Z-Wave”

Who is online

Users browsing this forum: No registered users and 0 guests