This object is in archive! 

How to use a input 2 of a Qubino dimmer in the rule creator

Albin Sunnanbo shared this question 7 years ago
Need Answer

Hi

I have a zipamini (Firmware 0.9.999.4) with a few Qubino ZMNHDD1 Flush Dimmer Module

I want to use Input 2 of the Qubino dimmer to trigger a rule in the Zipamini rule creator, but I can't find the device in the rule creator.


In the device manager I have found my dimmer. It has found a "Group 5: Basic On/Off Input2..." that looks exactly like the input I want to bind to my rule.


3b515c8368d9b027fbd308dc6ffbbbc6


But in the rule creator I only have an actuator for the main dimmer function


960742af9ee7b882cf8642d922091c25


What should I do to be able to use the Input 2 on my dimmer in the rule creator?


// Albin

Replies (9)

photo
1

Albin,

Qubino module's input need to be manualy configured to be "shown as a device" and therefore appear on rule creator. On your group 5 settings look for the Binary Input end point, hit configuration, check on "show as device", save, sync and refresh the web browser.


See attached.

photo
1

Albin,

Did you get it to work?


Will be happy if you can post screen captures your settings :)


/Magnus

photo
1

Hi

Thanks for your replies.

Still nothing in the rule creator. I have checked both the "Actuator" and the "Control" sections under "Device".

I have saved, synced devices, synced rule creator and restarted my browser.

This is how it looks in device manager when I unfold:

This "No clusters" looks suspicious.

6475d92d64225e6994cbfd46d32d96ee

And this is the device settings for the Group 7 - binary I2.

The "Type = Undefined" here also looks suspicious. There is only "Undefined" to select from in the drop down.

bb14d6b3b7e9d3a61bc4415b731773a4

And this is the configuration for the top node of the device ("Albins taklampa")

3c3dde995e13678bacb3827d6c196f53

photo
1

Change the type from undefined to Binary sensor, save, sync and reload.

photo
1

There is only "Undefined" in the list.

photo
photo
1

I can not not change undefined to Binary sensor, there is no option to change to, the list is empty,abaf24e926e791b491937066c4575842

photo
1

In your configuration window for root device you have "enable/disable input 2" check this. This might likely need to be changed. Read the manual. After this is changed to allow input, the device will need to be excluded and reincluded in zipato.

Then you should have input 2 listed (as I have)

photo
1

If I can interpret the manual correctly the value 9 should configure I2 as binary sensor.

As seen in my screen shot above, the Enable/Disable I2 was already set to 9.

23e138bd9684ab7e2b571c6fb2c815cf

photo
1

-- double post --

photo
photo
1

Look above in the picture. It says default value is 0. So perhaps you had it included with 0 and zipato saved then as 9 due to their descriptor setup. Query the parameter and if you receive 9 i advise you to exclude and reinclude the device (do not reset). It should work. But you must do it before continue troubleshooting.

photo
1

I forgot about that setting for Qubinos, as Attila describes, you should be able to see the endpoint correctly after you change its configuration and exclude/include again. If you read the right configuration from the device, and exclude/include and you still have the issue I would recommend you to open a ticket on zipato support. I don't have qubino dimmers (only flush relays and shutters) and I never had issues to see their inputs as bynary sensors.

photo
1

Albin, have you got it working?

photo
1

Haven't got the time to try yet.

photo
1

Any progress yet?

I'm curious since I've probably got a similar issue.

photo
1

I've the same issue and have open a ticket with support.

photo
1

I have the same issues. Any news?

photo
photo
1

I got the same problem then I found this topic.


You can read about I solved it here

https://community.zipato.com/topic/how-can-i-use-input-2-on-a-qubino-flush-1-relay-zmnhad1

Leave a Comment
 
Attach a file