This object is in archive!
How to use a input 2 of a Qubino dimmer in the rule creator
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.
But in the rule creator I only have an actuator for the main dimmer function
What should I do to be able to use the Input 2 on my dimmer in the rule creator?
// Albin
The same question
No connection
Real-time notifications may not work
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.
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.
Albin,
Did you get it to work?
Will be happy if you can post screen captures your settings :)
/Magnus
Albin,
Did you get it to work?
Will be happy if you can post screen captures your settings :)
/Magnus
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.
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.
And this is the configuration for the top node of the device ("Albins taklampa")
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.
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.
And this is the configuration for the top node of the device ("Albins taklampa")
I can not not change undefined to Binary sensor, there is no option to change to, the list is empty,
I can not not change undefined to Binary sensor, there is no option to change to, the list is empty,
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)
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)
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.
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.
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.
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.
Albin, have you got it working?
Albin, have you got it working?
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
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
Replies have been locked on this page!