Yubii home - is there some users here that could help me check if this products fits my needs ?

[ka2er 0]

Hi,

 

First some presentation : I'm new here I'm an IT professional and have a home in France that's already fitted with nice shutter and garden door automation. that's the "now" situation.

I just found your community and I hopes I will find here some folks with yubii home device that could help me answer some question I have before push the buy button.

the goal is to do some simple scenario but also handle MQTT Tasmota driven devices, yubii could be in master mode or maybe slave mode of other system like HASS.

Ideally I would interfaces all of this with MQTT or some REST API

 

I would like to have a gateway to control shutters (TT1N TT2N), door (Nice robes 400) and maybe some nice ligne controlled (TT1L). I just found Yubii home product could do it but not very sure after reading specs and documentation if it does it like I understand.

So here are a lot of questions (I apologize) :

 

- does this gateway handle all nice protocols ?

- does this gateway have an REST API documented in order to interface it with other automation solution like HASS

- same question for MQTT API

- does HCL line handle Nice protocol (I don't believe)

- does it outperform the precedent core gateway with seem to be limited to 6 groups

- does the integration of already existing remote or group is easy ?

- does it exist a demo interface somewhere to check the pro and con of this gateway ?

 

If anyone have experience or could help answer this question I would greatly appreciate it !

 

have a nice day.

[10der 825]

Quote

- does this gateway handle all nice protocols ?

if nice is NICE not nice protocols like zigbee / mqtt  etc - YES

 

Quote

- does this gateway have an REST API documented in order to interface it with other automation solution like HASS

yep. HC3 has swagger (id you developer you should know what is) and yes you can call API function from any others integrations

 

Quote

- same question for MQTT API

yes. but one disclaimer HC3 doesn't have own MQTT server   

 

Quote

- does HCL line handle Nice protocol (I don't believe)

IMHO yes. HCL AFAIK only restricted by MEM and CPU. Sorry too lazy reading RTFMs. also HCL can't be as master in ZWAVE net work

 

Quote

- does it outperform the precedent core gateway with seem to be limited to 6 groups

no comments. at the left hand yes, at the right with the current situation by proto(s) what it has... just modern UI / modern ZW3 proto / etc

but rPI4 with ZW USB stick + HASS + NODE-RED can cover all your requirements without HC3
IMHO 

Quote

- does the integration of already existing remote or group is easy ?

sorry can't catch you question

what remote or group you are talk about

 

Quote

- does it exist a demo interface somewhere to check the pro and con of this gateway ?

 

IMHO no. but also IMHO you can cinch with @tinman . he is a best seller / fibaro partner / etc / so on here  

 

[A.Socha 75]

2 godziny temu, ka2er napisał:

So here are a lot of questions (I apologize) :

 

- does this gateway handle all nice protocols ?

NOT ALL BUT MOST, FOR EXAMPLE FLOR, OPERA PLN2 OR PLN2+- YOU CAN CHECK ON REMOTE WHAT PROTOCOL ARE USING, BY YOUR DEVICE TT1 I THINK IT WILL BE OPERA

- does this gateway have an REST API documented in order to interface it with other automation solution like HASS

Yes

- same question for MQTT API

we don't give access to it for user

- does HCL line handle Nice protocol (I don't believe)

Search Yubii it is HCL for Nice products

Please login or register to see this link.

- does it outperform the precedent core gateway with seem to be limited to 6 groups

Yubii should be better, but all depends on what you want to receive.

- does the integration of already existing remote or group is easy ?

Yes you can use copy remote like copying nice remote to another remote

- does it exist a demo interface somewhere to check the pro and con of this gateway ?

You are from France? Maybe check Nice France, maybe they got showroom and can answer on all your questions

If anyone have experience or could help answer this question, I would greatly appreciate it !

 

have a nice day.

 

[ka2er 0]

1 hour ago, 10der said:

Quote

if nice is NICE not nice protocols like zigbee / mqtt  etc - YES

 

as NICE I refer to NICE S.A. product line which use several protocol

 

- NICE Flor-s (433 rolling code)

- NICE Smile (433 rolling code)

 

1 hour ago, 10der said:

Quote

yep. HC3 has swagger (id you developer you should know what is) and yes you can call API function from any others integrations

 

- you talk about HC3 but I didn't get if Yubbii Home include all HC3 features. if so the swagger part will be present in Yubii Home ?

 

1 hour ago, 10der said:

Quote

yes. but one disclaimer HC3 doesn't have own MQTT server  

 

- MQTT client will be fine. yubii home also has MQTT client ? 

 

1 hour ago, 10der said:

Quote

IMHO yes. HCL AFAIK only restricted by MEM and CPU. Sorry too lazy reading RTFMs. also HCL can't be as master in ZWAVE net work

 

As fas as I understand you the HC3 Manual apply to yubii home ?

 

1 hour ago, 10der said:

Quote

 

no comments. at the left hand yes, at the right with the current situation by proto(s) what it has... just modern UI / modern ZW3 proto / etc

but rPI4 with ZW USB stick + HASS + NODE-RED can cover all your requirements without HC3

 

 

Maybe some misunderstood , I don't plan to use ZWAVE as the shutter/garage door are 433 RF nice flo-R protocol (rolling code).

All the OSS solution I have looked at doesn't implement the FLO-R RF protocol (maybe I miss something).
If there is an OSS solution that handle NICE FLOR-R protocol I would be happy to hear about it.

 

1 hour ago, 10der said:

IMHO 

Quote

 

sorry can't catch you question

what remote or group you are talk about

 

 

NICE remote. I key remote could toggle several NICE receptor (motor, TT1N, TT1L, TT2N etc...).

 

1 hour ago, 10der said:

 

IMHO no. but also IMHO you can cinch with @tinman . he is a best seller / fibaro partner / etc / so on here  

 

 

thanks you for taking time to answer to each of my points 

[ka2er 0]

18 minutes ago, A.Socha said:

- does HCL line handle Nice protocol (I don't believe)

Search Yubii it is HCL for Nice products

ok I understand Yubii handle FLOR while HCL will not. is it right ?

 

19 minutes ago, A.Socha said:

- does it exist a demo interface somewhere to check the pro and con of this gateway ?

You are from France? Maybe check Nice France, maybe they got showroom and can answer on all your questions

tried to contact them via web contact form but no feedback so far

 

20 minutes ago, A.Socha said:

- same question for MQTT API

we don't give access to it for user

but can the Yubii gw could forward events and listen them to/from a remote MQTT server ? if access is not allowed for the moment is it in a roadmap ?

 

You seems to work closely on the product line Yubii is there some public roadmap or feature request list ?

[A.Socha 75]

2 godziny temu, ka2er napisał:

ok I understand Yubii handle FLOR while HCL will not. is it right ?

yes, Yubii=HC3L + extra radio for Nice and Elero

 

2 godziny temu, ka2er napisał:

tried to contact them via web contact form but no feedback so far

if there will be no answer send me PM i will wrote to them

 

2 godziny temu, ka2er napisał:

but can the Yubii gw could forward events and listen them to/from a remote MQTT server ?

I don't quite understand the functionality you want to achieve. The gateway shows the status of the devices (except for Nice with one-way protocol like FLOR (devices do not respond))

In the gateway you have the possibility to build automation based on events, e.g. at sunrise open the blinds

[ka2er 0]

29 minutes ago, A.Socha said:

I don't quite understand the functionality you want to achieve. The gateway shows the status of the devices (except for Nice with one-way protocol like FLOR (devices do not respond))

in fact I already have some event scenario in hass. some detection presence toogle based on who is at home, or some scenario based on light conditions "direct sun detection/summer". I could use them to close shutters home which are facing sun.

 

I could manage hybrid scenario HASS and YH-001 (yubii home) but I believe it would be simpler to do all scenario in one system. 

For example I also have velux shutter and got a velux gateway. The gateway is registered via apple home into hass. hass could ask velux gateway to close or open velux shutter.

 

web|android|iOS -> hass -> vendor gw (velux/nice/custom) -> shutter/garage door.

 

Benefits for me are multiple. I could aggregate many vendors without needs of standard and I don't believe they will be one day (security concerns, secret engineering, etc...).

if I can't weak couple system it's harder to manage and I can't use all signal inputs to build scenarios.

If another system could talk to gw via REST or ideally via MQTT it's easily pluggable and the coupling is loose.

 

example : 

Please login or register to see this code.

Please login or register to see this code.

 

as you can see you can act bi directionnally between automation system.

vendor don't have to rely on common protocol dedicated to automation but only on communication protocol already widely used in IOT

 

another scenario I would like to achieve : "close all shutter and velux".

not sure YH-001 can natively handle velux RF command, neither velux gw can handle NICE FLOR (each vendor keep secret their rolling code).

 

but if I can tell each gw "hey close the shutter" from a common automation system, goal is achieved and vendor don't have to release their rolling code (vendor locked in color).

 

temp sensor+light sensor+calendar -> "sun is hard" -> automation system -> gw velux -> velux shutter

temp sensor+light sensor+calendar -> "sun is hard" -> automation system -> gw nice -> nice shutter

 

Maybe I miss something and it exist more elegant way to achieve this, I will be happy to learn about it.

 

[A.Socha 75]

ok, Now I understand what you're trying to achieve.

 

Yes, Yubii has a REST API, so you can write integrations in HASS to enlist devices and long pooling, which we currently use to notify system changes.
For mono devices even this may not be necessary because as I mentioned earlier mono devices do not report their status.

As for Robus you probably have another remote that communicates with the module placed in Robus (OXI) depending on the protocol it can be one or two way.

As for velux we have no official integration with them.

 

[ka2er 0]

may the swagger contract be shared in order to have a look ?

[M.Mróz 12]

 Hello ka2er, not the exact swagger but maybe API reference will work here?...

You can check here:

Please login or register to see this link.

?

[tinman 1,002]

1 hour ago, M.Mróz said:

Please login or register to see this link.

 

 

ohh missed that, on Fibaro ID is still not yet available...

 

Please login or register to see this image.

/monthly_2021_12/image.png.a2e1262d675cccc7f95936eb04bcafb9.png" />

[M.Mróz 12]

Uhm..clearly...it should be! will try to ask my colleagues to provide relevant linkeage. ?

[ka2er 0]

On 12/1/2021 at 6:50 PM, M.Mróz said:

 Hello ka2er, not the exact swagger but maybe API reference will work here?...

You can check here:

Please login or register to see this link.

?

? you rocks !

so I believe what I am looking for to trigger Nice event is 

Please login or register to see this link.

I just discovered FIBARO community, I already found it pleasant and open

 

Edited December 3, 2021 by ka2er

[M.Mróz 12]

???

[ka2er 0]

gateway received. first nice shutter (TT1N receiver) appaired.

when I test button nothing move. 1st user experience very deceptive so far.

 

Where to get support ? is there some official support ? does the support is official done on this board ?

[A.Socha 75]

[email protected]

 

witch option you used to add? try add by remote access

[ka2er 0]

Please login or register to see this attachment.

 

ok thanks ticket opened.
tried all.

I believed the most suitable was the one selected on the screenshot.
The last one will only record my remote but won't trigger RF events to TT1N, TT2N paired devices as far as I understand.

[A.Socha 75]

Yes that option (marked) is recommended, when you're doing auto-detection which protocol it discovers?

[ka2er 0]

mono.

 

I could provide Har payload of a device (TT1N) enrollment if you like to have a look at REST calls.

I'm willing to spend some time on debugging this issue if someone could confirm that this nice product is supported.

also as I initially tried in stable release and it won't work, I had a look to beta changelog and saw multiple fix and improvements regarding Nice line products so I upgraded to beta.

unfortunately, enrollment under beta fw behaves the same.

 

Do you know if I can have access to a verbose debug log somewhere ? saw the ssh access is locked.

may I remote syslog or something like that ?

[ka2er 0]

no answer from the support since 24H ticket open. I hope I will have some feedback soon, if I need to ask for a refund I only have little time to troubleshoot.

if someone has the password to access this KB 

Please login or register to see this link.

 maybe I'll discover that my nice line product isn't supported and I bought something that can't fit my need.

[A.Socha 75]

sent me please ticket number on PM