Lost connection with Alexa and Google home

[cag014 731]

After an upgrade have lost connection to Alexa and Google home. All devices are unresponsive.

When trying to activate device from Alexa, HC3 is losing internet connection for a sec.

Interesting that devices connected to HC2 are working fine.

Edited January 28, 2025 by cag014

[Mestregg 0]

I have the same issue here. Everything works fine in Yubi but Alexa show all devices as unresponsive. Already tried to restart HC3 and Alexa, and rediscover devices but nothing works.

[Bob Winter 2]

I have the same problem with my HC3, it stopped responding to Alexa last night and is doing the same this morning

[Neo Andersson 230]

Same here. No connection to Google. @m.roszak Any fix for that?

[m.roszak 763]

We are on it

[cag014 731]

1 hour ago, m.roszak said:

We are on it

It could be related to your latest network infrastructure maintenance and not necessary the upgrade isuue.

[Florian_123 0]

Same topic. This morning Alexa not working at all all devices unresponsive ("sever unresponsive"). Yubii Works... I had not upgraded the software. After upgrade to next stable version same issue.

 

Also deactivated the Alexa Skill and reactivated it. Same problem. Removed device in Alexa and search for it -> No Device Found. Whole House no voice control -> Please Help

Edited January 28, 2025 by Florian_123

[Lacroix 0]

Very same here since yesterday night.

[Ronny Smits 0]

I have all devices unresponsive after the upgrade yesterday. Any solution in sight?

[Marco_Vas 0]

Same problem here; after (and during) the maintenance of yesterday...
Yubii Home 5.171.15 (beta) (updated months ago)
All Nice and Fibaro devices, connected to Yubii Home, are shown as unresponsive from Alexa and Google Home assistants, and stopped responding on voice commands last night starting from the maintenance of yesterday at 9 pm GMT+1. Before then everything was working fine.
 

[A.Socha 133]

Hello

 

we have located the cause, please check now.

1 godzinę temu, cag014 napisał:

It could be related to your latest network infrastructure maintenance and not necessary the upgrade isuue.

Unfortunately partly yes, the error is with the network configuration which did not allow some types of queries through.

If you notice anything else please let us know.

Of the good things, the entire environment as of now is on AWS in HA (high availability) configuration in the Frankfurt region in several zones

My apologies for the problems

[cag014 731]

4 minutes ago, A.Socha said:

Hello

 

we have located the cause, please check now.

Unfortunately partly yes, the error is with the network configuration which did not allow some types of queries through.

If you notice anything else please let us know.

Of the good things, the entire environment as of now is on AWS in HA (high availability) configuration in the Frankfurt region in several zones

My apologies for the problems

Thanks for a such a quick prompt to the problem.

Everything back to normal and works fine

[xmemphis2 0]

I have the same issue and fibaro support responses are "we are working on that, it has the highest status" 

[cag014 731]

1 hour ago, xmemphis2 said:

I have the same issue and fibaro support responses are "we are working on that, it has the highest status" 

The issue has fixed few hours ago... Check again.