Qubino input always reads as OFF, is this normal?

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.

Moderators: leecollings, remb0

Post Reply
Geuvert
Posts: 6
Joined: Tuesday 07 May 2019 20:11
Target OS: Linux
Domoticz version: 4.10717
Location: Netherlands
Contact:
Contact Geuvert

Qubino input always reads as OFF, is this normal?

Post by Geuvert »

Hi everybody,

In follow-up on a different question on the forum I have a question about the status of a switch.
I'm trying to read out the status of the I3 input of a Qubino dimmer. I've been tinkering with this for some while now. However it shows some odd behaviour and i'm not sure whether this is a bug, a driver problem, completely normal or something else.

So, the Qubino dimmer has three physical inputs, I1, I2 and I3.
I1 is an input that controls the lamp. I2 and I3 are inputs to do whatever. In the time between the other topic and now I have removed all group associations except for the lifeline, so only the lifeline is associated to the z-wave stick.

I1 and I2 work normally as far as I can tell. When I operate the (bi-stable) switch attached to I3, Domoticz shows behaviour I don't understand:

First scenario; Flip the switch (I3) to on:
The log shows an alarm, I3 and, after almost 2 seconds, I2:
Spoiler: show
2019-06-03 20:17:29.997 (Controller) Light/Switch (Alarm Type)
2019-06-03 20:17:29.998 (Controller) Light/Switch (Qubino Dimmer I3)
2019-06-03 20:17:31.794 (Controller) Light/Switch (Qubino I2)
Second scenario; Flip the switch (I3) to off:
The log shows an alarm, I3 and, after almost 2 seconds, I2:
Spoiler: show
2019-06-03 20:22:02.578 (Controller) Light/Switch (Alarm Type)
2019-06-03 20:22:02.579 (Controller) Light/Switch (Qubino Dimmer I3)
2019-06-03 20:22:04.212 (Controller) Light/Switch (Qubino I2)
Third scenario; Flip the switch (I3) to on and quickly back to off (like a monostable switch):
The log shows an alarm and I3:
Spoiler: show
2019-06-03 20:24:50.678 (Controller) Light/Switch (Alarm Type)
2019-06-03 20:24:50.679 (Controller) Light/Switch (Qubino Dimmer I3)
Please notice that, in scenario three, I2 did not show up in the log.

Because the log does not show the status of the physical switch I wrote a very simple piece of code to help me with that:
Spoiler: show

Code: Select all

return {
	on = {
		devices = {
			'Qubino Dimmer I3'
		}
	},
	execute = function(domoticz, switch)
	    if (switch.state == 'On') then
	        domoticz.log('Message: Qubino I3 is ON')
	    else if (switch.state == 'Off') then
	        domoticz.log('Message: Qubino I3 is OFF')
	    else
	        domoticz.log('Message: Qubino I3 is...???')
	    end
	end
end
}
In all the previous mentioned scenarios after the log shows I3 activity I get the message that I3 is OFF:
Spoiler: show
2019-06-03 20:30:52.259 (Controller) Light/Switch (Qubino Dimmer I3)
2019-06-03 20:30:52.273 Status: dzVents: Info: Handling events for: "Qubino Dimmer I3", value: "Off"
2019-06-03 20:30:52.273 Status: dzVents: Info: ------ Start internal script: Test: Device: "Qubino Dimmer I3 (Controller)", Index: 120
2019-06-03 20:30:52.273 Status: dzVents: Info: Message: Qubino I3 is OFF
2019-06-03 20:30:52.273 Status: dzVents: Info: ------ Finished Test
Now, Is this normal behaviour? Is there a bug in the software? Do I have bad luck with my hardware?

Your replies would be greatly appreciated.


Geuvert
Top
Trigun
Posts: 390
Joined: Wednesday 30 November 2016 11:58
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10717
Contact:
Contact Trigun

Re: Qubino input always reads as OFF, is this normal?

Post by Trigun »

Geuvert wrote:Hi everybody,

In follow-up on a different question on the forum I have a question about the status of a switch.
I'm trying to read out the status of the I3 input of a Qubino dimmer. I've been tinkering with this for some while now. However it shows some odd behaviour and i'm not sure whether this is a bug, a driver problem, completely normal or something else.

So, the Qubino dimmer has three physical inputs, I1, I2 and I3.
I1 is an input that controls the lamp. I2 and I3 are inputs to do whatever. In the time between the other topic and now I have removed all group associations except for the lifeline, so only the lifeline is associated to the z-wave stick.

I1 and I2 work normally as far as I can tell. When I operate the (bi-stable) switch attached to I3, Domoticz shows behaviour I don't understand:

First scenario; Flip the switch (I3) to on:
The log shows an alarm, I3 and, after almost 2 seconds, I2:
Spoiler: show
2019-06-03 20:17:29.997 (Controller) Light/Switch (Alarm Type)
2019-06-03 20:17:29.998 (Controller) Light/Switch (Qubino Dimmer I3)
2019-06-03 20:17:31.794 (Controller) Light/Switch (Qubino I2)
Second scenario; Flip the switch (I3) to off:
The log shows an alarm, I3 and, after almost 2 seconds, I2:
Spoiler: show
2019-06-03 20:22:02.578 (Controller) Light/Switch (Alarm Type)
2019-06-03 20:22:02.579 (Controller) Light/Switch (Qubino Dimmer I3)
2019-06-03 20:22:04.212 (Controller) Light/Switch (Qubino I2)
Third scenario; Flip the switch (I3) to on and quickly back to off (like a monostable switch):
The log shows an alarm and I3:
Spoiler: show
2019-06-03 20:24:50.678 (Controller) Light/Switch (Alarm Type)
2019-06-03 20:24:50.679 (Controller) Light/Switch (Qubino Dimmer I3)
Please notice that, in scenario three, I2 did not show up in the log.

Because the log does not show the status of the physical switch I wrote a very simple piece of code to help me with that:
Spoiler: show

Code: Select all

return {
	on = {
		devices = {
			'Qubino Dimmer I3'
		}
	},
	execute = function(domoticz, switch)
	    if (switch.state == 'On') then
	        domoticz.log('Message: Qubino I3 is ON')
	    else if (switch.state == 'Off') then
	        domoticz.log('Message: Qubino I3 is OFF')
	    else
	        domoticz.log('Message: Qubino I3 is...???')
	    end
	end
end
}
In all the previous mentioned scenarios after the log shows I3 activity I get the message that I3 is OFF:
Spoiler: show
2019-06-03 20:30:52.259 (Controller) Light/Switch (Qubino Dimmer I3)
2019-06-03 20:30:52.273 Status: dzVents: Info: Handling events for: "Qubino Dimmer I3", value: "Off"
2019-06-03 20:30:52.273 Status: dzVents: Info: ------ Start internal script: Test: Device: "Qubino Dimmer I3 (Controller)", Index: 120
2019-06-03 20:30:52.273 Status: dzVents: Info: Message: Qubino I3 is OFF
2019-06-03 20:30:52.273 Status: dzVents: Info: ------ Finished Test
Now, Is this normal behaviour? Is there a bug in the software? Do I have bad luck with my hardware?

Your replies would be greatly appreciated.


Geuvert
My experienxe is that the qubino dimmers don’t work well with bi-stable. Push button switches on the other hand, work fanantastic. I have approx 10 dimmers and all work well with push buttons. With The qubino switches it doesn’t matter, both work good!


Sent from my iPhone using Tapatalk
Top
Geuvert
Posts: 6
Joined: Tuesday 07 May 2019 20:11
Target OS: Linux
Domoticz version: 4.10717
Location: Netherlands
Contact:
Contact Geuvert

Re: Qubino input always reads as OFF, is this normal?

Post by Geuvert »

Hi Trigun,

Thanks for your reply.

Do you use the I3 input with a momentary switch as well?
If so, how have you configured it? I have it set to binary sensor.

Awaiting your reply,


Geuvert
Top
Trigun
Posts: 390
Joined: Wednesday 30 November 2016 11:58
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.10717
Contact:
Contact Trigun

Re: Qubino input always reads as OFF, is this normal?

Post by Trigun »

Geuvert wrote:Hi Trigun,

Thanks for your reply.

Do you use the I3 input with a momentary switch as well?
If so, how have you configured it? I have it set to binary sensor.

Awaiting your reply,


Geuvert
Nope, I use the I1 only as both i2and i3 at for sensors only(on a dimmer) that said, I3 is either a normally open or normally closed output.


Sent from my iPhone using Tapatalk
Top
Post Reply

Return to “Other questions and discussions”

Who is online

Users browsing this forum: Google [Bot] and 1 guest