Just FYI: Burst of voice notifications crashes the box

[Horia]

Hi,

I use voice notifications by upnp for many events including secure access into the home. I faced a household crisis during holidays because the box crash under these circumstances.

My tag reader rule settings did not include delays, hence naturally burst attempts to disable security. After a while the outcome from the box is: red LED, no local or remote eedomus connection even that HTTP, SSH, HTTPS ports remain open, no local rule/radio control, but ICMP to box still works.

I tested and retested this with the new SW release by issuing by web ui test commands for the voice generator...multiple times. Hence, I did open a case and I did disable or delayed the rules generating bursts of voice notifications.

I hope the CO team will fix with the next SW release. If you have comments please share.

Thanks and regards, Horia

[Horia]

No fix yet.

I tried a fast sequence of 5x Time reports via the test function in the voice generation device.

The box crashed after the 2nd attempt to relay on upnp. Once I re-powered the box, it crashed again while it seems the cloud injected the remaining requests.

Regards, Horia

[fullpower]

Hi Horia,

What kind of crash does your box ?
Strange...I use Upnp (with Eedomus' TTS) at the opening of my portal on 2 devices : android tablet asus TF300 & Nvidia shield android TV + Bubble Upnp (paid) , i have never seen any crash ...

[Horia]

Hi,

Like I said this happens only with a burst of multiple, closely time spaced upnp voice notifications. As result I see the cloud connection lost, the local web server not responding (even that both HTTP and HTPS ports on the box are still open), the LED red, but ICMP pings to box working still, all Z-wave/433MHZ control stops.

A power reboot recovers.

I discovered it while the upnp voice notifications have some time lags and somebody tried to disable multiple times through the tag reader the surveillance hence generated multiple upnp requests next to each others in time. Now I introduced time delays on the rules, so the issue will be avoided most of the times.

If you want to test, go on the voice generation device (Synthèse vocale), and trigger the test for one of the messages multiple times. If click test 5 times fast for "Il est [TIME]" the crash happens.

Regards, Horia

[Horia]

Actually, could somebody please try to reconfirm the behavior?

I wonder if is an issue with the SW on my box, in which case I could do a forced mise a jour ...Otherwise, it would confirm the bug and motivate the CO team to take a look.

To test: just click test multiple times on "Il est [TIME]" dans le dispositif de "Synthèse vocale" dans la section de Valeurs.

Thanks, Horia

[fullpower]

Hi Horia !

I 'll try this evenning ...

EDIT : Horia, sorry but no crash 4 me ...
i tried all values and clicked several times on each value or clicked 10 times on "il est [time]"
...but apart from the fact that the box has a little difficulties to talk so many times, no worries !

[Horia]

Thanks a lot for confirming. I'll do a local software restoration.

Regards, Horia

[Horia]

Hi,

I did the software refresh.

The box handled a longer burst but finally the result was the same.

Hence, I have to say: There is a BUG out There and to continue on the pseudo lyrics from Pink Floyd, I would ask: Hey you, CO can you feel it?

Regards, Horia

[fullpower]

Have you tried a factory reset ?

[Horia]

It took me a year to stabilise my large Z-wave network.

So not point, this is most probably unrelated issue, there are workarounds in place. Hopefully CO will do something about. They have done the same for more serious issues I raised on Z-wave aspects.

Regards, Horia