Page 2 of 2

Re: Qubine ZMNHBD1 not working well

Posted: Wednesday 18 May 2016 18:49
by SchattenMann
OK so I worked my way around this but it's still a no go unfortunately..

Instant Status reports are being sent to the same device (lets call it parent) so it's no use.

I suppose if it's working for you and not for me it must be cuz i have an S3 version

Re: Qubine ZMNHBD1 not working well

Posted: Thursday 19 May 2016 8:57
by Egregius
Use the refresh script that's here somewhere.
Works already about a year here.

Re: Qubine ZMNHBD1 not working well

Posted: Thursday 19 May 2016 10:22
by SchattenMann
Yeah but that will need a PHP server :-(

Re: Qubine ZMNHBD1 not working well

Posted: Thursday 19 May 2016 11:07
by Egregius
Not really, you can install php5 for cli only.
Or analyze the called functions and translate it to bash/lua/...

Re: Qubine ZMNHBD1 not working well

Posted: Thursday 19 May 2016 11:31
by juankar
Try to associate groups 2-8 with node 1.1 (yes 1 point 1), that's use multiInstace association of this device.
I know S3 firmware had issue with power reports. You can ask for update if you have this kind of issue.
Bye.

Re: Qubine ZMNHBD1 not working well

Posted: Saturday 21 May 2016 12:09
by hamish
juankar wrote:Try to associate groups 2-8 with node 1.1 (yes 1 point 1), that's use multiInstace association of this device.
I know S3 firmware had issue with power reports. You can ask for update if you have this kind of issue.
Bye.
Specifically groups 4 and 7 of the root device are the important ones for power reports... I'm not sure if Domoticz knows how to set the individual endpoint groups... (They seem to be a reflection of the root device groups anyway)

Root device:
Group 1: Lifeline group (reserved for communication with the main controller), 1 node allowed.
Group 2: basic on/off (triggered at change of the output Q1 state and reflecting its state) up to 16 nodes.
Group 3: switch binary report (triggered at change of the output Q1 state and reflecting its state) up to 16 nodes.
Group 4: power meter report (triggered at change of the output Q1 state) up to 16 nodes.
Group 5: basic on/off (triggered at change of the output Q2 state and reflecting its state) up to 16 nodes.
Group 6: switch binary report (triggered at change of the output Q2 state and reflecting its state) up to 16 nodes.
Group 7: power meter report (triggered at change of the output Q2 state) up to 16 nodes.
Group 8: multilevel sensor report (triggered at change of temperature sensor) up to 16 nodes.

End point 1:
Group 1: Lifeline group, 0 nodes allowed.
Group 2: basic on/off (triggered at change of the output Q1 state and reflecting its state) up to 16 nodes.
Group 3: switch binary report (triggered at change of the output Q1 state and reflecting its state) up to 16 nodes.
Group 4: power meter report (triggered at change of the output Q1 state and reflecting its state) up to 16 nodes.

End point 2:
Group 1: Lifeline group, 0 nodes allowed.
Group 2: basic on/off (triggered at change of the output Q2 state and reflecting its state) up to 16 nodes.
Group 3: switch binary report (triggered at change of the output Q2 state and reflecting its state) up to 16 nodes.
Group 4: power meter report (triggered at change of the output Q2 state and reflecting its state) up to 16 nodes.

End point 3:
Group 1: Lifeline group, 0 nodes allowed.
Group 2: multilevel sensor report (triggered at change of temperature sensor) up to 16 nodes.

New With This But Have Problems

Posted: Friday 14 July 2017 9:30
by CalistaAlbert
I Am Also New At ZMNHBD1 But It's Not Guiding Me Well Or May Be It's Not Working Well...!

http://www.celebstyleoutfits.com/mens-j ... collection