Was there made a fix for this problem, because i notice the following problem by me.
I have a quibino roller shutter. If i tell the openhab to set the shutter to 90% then it opens them so that they are 90% open, so just 10 % from the rollershutters are visible.
By the same setting if i tell the Google to set the blinds to 90% than are 10% open and 90% are visible.
If i use the invert percentage for the channel in openhab, than if i tell the openhab to set the shutter to 90% then it opens them so that they are 10% open, so just 90 % from the rollershutters are visible.
By the same setting if i tell the Google to set the blinds to 90% than are 90% open and 10% are visible.
@Rintano, Iâve closed the long Google Assistant thread to new posts and yourâs is the last post and it doesnât have a response yet so I moved it to itâs own thread. Tagging @MARZIMA in case you donât see this, the post was originally a reply to one of yours.
Hallo, Any news or any idea?
@MARZIMA
Hi, any update in Google Assistant integration and NOT WORKING:
[âhomekit:TargetHeatingCoolingModeâ] vs [âhomekit:HeatingCoolingModeâ] ?
We can set target temperature, read target temperature, read humidity but we cannot set heatingCooling mode⊠so we donât know what is current mode in specific room âŠ
Does GA integration support âopen shutter to 10%â and âclose shutter to 10%â - the last should be the opposite of the first, not the same.
âŠor should get rid of the words âopenâ and âcloseâ and only refer to something like âmove shutter to 10%â?
(Iâm not a native speaker, hopefully you understand me)
As i know it does not support. the 10% is the same, not important how the words are formuled.
You need to use the word âcloseâ or âopenâ, at least when talking German. âmove toâ or similar donât work.
Yes, you need to use the words âOpenâ and âCloseâ, but not important which you use, the shutter would move to the same position. The Open the blinds to 10% would do the same as Close the blinds to 10%.
How do you configure a rollershutter if you have both the Goodle assistant active and the Homekit AddOn?
For homekit the tag to be used is âWindowCoveringâ and for Google it needs to be âCurtainâ or âShutterâ. How do I get my rollershutteritems to appear in homekit and Google assistant so I can use both. I.e. what would a configuration line look like.
Does anybody have other items than swithced and lights active in both. For switches and lights it works fine as there are TAGs that work for both (Switchable and LIghting)
Hi,
I donât have Homekit, but i would Implement 2 âDummyâ items, one for the Google and one for the Homekit. Both would update the real shutter and each other by change in a rule. Or u can the real shutter item use for Homekit and make a dummy just for the Google.
Have you tried just adding both tags? I believe both HomeKit and GA will ignore tags it doesnât understand.
Even though it may be totally obvious to most of you at least it took me quite some time to find out the right syntax to be able to tag a rollershutter item.
The documentation says it should be âtaggedâ with { ga=âshutterâ } but of course usually you would have the { channel=ââŠâ } already in your item, so I defined it as follows
Rollershutter myShutter âRolliâ { ga=âshutterâ channel=ââŠâ }
which fails because the syntax is wrong.
I wasnât aware until after some while that the right syntax is that you have to use a COMMA between both.
Rollershutter myShutter "Rolli" { ga="Shutter",channel="zwave:device:8ce122f5:node12:blinds_control" }
and yes, if you look thoroughly in Items | openHAB you will find examples with comma-separations in the curly brackets but even though I am working with OH for quite some time this never stroke me. So forgive me my ignorance but others may donât know this as well, so I thought Iâd share this.
Hi there,
playing around with rollershutters and google assistant, and stumbled on a possible problem.
Openhab assumes that 0 means open (shutter is up) and 100 means closed (shutter down).
Google assistant thinks the same (without inversion), however a command like âopen/close the shutter to 20 percentâ sends a command of 80 to Openhab.
If I invert the roll, 20 gets sent as 20, but now open means down and close means up.
According to the documentation, one of the two modes should word correctly:
Blinds and similar devices
Blinds should always use the
Rollershutter
item type. Since Google and openHAB use the oposite percentage value for âopenedâ or âclosedâ, the action will tranlate this automatically. If the values are still inverted in your case, you can state the[ inverted=true ]
option for allRollershutter
items.#
What am I missing?
Does this explanation help you?
To recapâŠ
Google world says: xx% is the percentage of how much a blind is opened
â âcloseâ translates to 0%
â âopenâ translates to 100%openHAB world says: xx% is the percentage of how much a blind is closed
â âdownâ translates to 100%
â âupâ translates to 0%Therefore, by default the percentage is always inverted, so that âcloseâ becomes âdownâ.
If a user does not want this inversion, the inverted=true option can be set.
But this also causes âcloseâ being inverted to âupâ and âopenâ becoming âdownâ.Since Google only tells the open percentage (and not the verb âcloseâ or âdownâ), we can not differentiate between saying âset blind to 100%â or âopen blindâ.
Therefore, we are not able to ânot invertâ the verbs, if the users chooses to invert the numbers.
Hello,
Thanks for the link. It confirms the problem. Iâm happy to see it as an open issue.
When I add my rollershutters to GA they show up in the Google home up as blicds with a gear icon at the top but they donât do anything.
The blinds do respond to voice command OPEN and close but within the Google home app the ico isnât working at all.
Have I done something wrong ?
This is the same for all of us. There seems just to be no support for manual control yet.
Hey @michikrug!
Actually, Iâm not sure you have a Google hub, but in fact there are blinds/shutters/rollershutters controls on it!! (Attached a picture below)
Iâve tried to understand the controls, or checking what they send back to OH but Iâm not quite sure how to go about that.
Any hints? Iâve only just begun adopting a motor for my blinds into OpenHAB (in fact the motor is on the floor and I donât know up from down yetâŠ) so any pointers or relevant info is highly appreciated!
Hah knowing how to access the console is pretty handy!
So the âplayâ icon sends the âMOVEâ command back to openHAB. The stop, well that one is pretty explanatory. My issue is now with the ones above, which I suppose controls the direction. Clicking those sends nothing back to openHABâŠ
Where to go from here, I wonder?
Nice to see some controls here. I do not own a Google Nest Hub, so will also not be able to test this.
Sending a direction together with âMoveâ is not implemented in the integration. Would probably need some conversion to âUp/Downâ.
The issue Iâm facing now is that even openhab ârollers utterâ item has three buttons at the item level, which appear to be âupâ âdownâ âstopâ, but, when clicking on them, the tasmotta controller receives â100â â0â or another â0â for stop.
Meaning that I cannot automate this properly.
Any hints?