Wave shutter relay becoming unresponsive in HA

[Janek]

Hello,

i have finally bought about 10 of the shelly qubino wave shutter relays to control my house blinds.
i installed them, included them in the Zwave network through my Aeotec Zwave USB stick in home assistant, have calibrated them and started to use them.

however, recently they have become unresponsive in random. one room has 4 blinds and sometimes blind #1 becomes unresponsive eventhough in HA it shows as online and alive.
I have to power cycle the relay to get it back to work again, but then it fails again. also relay #4 which is in the same room has this random dropping issue. Day before it was relay #2 and even relay #3.

i have made an automation in HA to group 4 shutter relays to be able to control the tilting, and when i tried it once or twice it worked, and then some blinds started dropping out and did not tilt as was requested by the tilt function in HA.
then i tried to control the tilt individually but no response, but in HA it showed the device as online and available, but unresponsive. then i tried to control it with the manual switch, in some case it worked, but in others it was not responding at all.

The RSI strength is around -64, RTT 875ms,  it has a direct connection to the zwave stick, no bounce through other nodes.

i have tried to reinclude the devices, rebuild route for the device and for the whole wave network but without success.

i have also updated the firmware to 12.23.0,  but no luck.

can you tell me what the issue might be? is it range? is RSI -64 not strong enough? 

the statistics show 0 dropped commands on the TX, but about 36 dropped on the RX side. total of 5866 commands were sent/received.

please let me know what i can do to resolve this problem.

thank you for any help and advice.

 

[Levin]

Hi

Sounds very similar to my topic, at least the unresponsive part.

In my case its not about the tilt but normal operation. It seems only to happen while using an associated device.
Could be related, but no fix so far.

 

[Shelly Wave help]

Can you let us know if there's any routing involved the unresponsive devices? Meaning if there's any device that have a route trough the devices with issues?
You may check that in the Z-Wave JS UI Network graph


Can anyone provide us the logs from the time that happen in order to investigate better what is happening?

[Janek]

unfortunately i dont have such network map available in my homeassistant instance.

i have done the update of the Zwave JS in homeassitant, and also updated the latest firmware to the Shelly zwave shutter 

QNSH-001P10, but today one became again unavailable and cannot get it to work. maybe have to again power cycle the unit. which im not so happy about.

i dont  know if another unit is being routed through this one, but all the rest seem to be working. actually another shutter controller is in the same room as this one and its working.

i hope you guys can figure out whats causing this random failure.

i want to add 8 more windows but now im a bit hesitant to do so due to the reliability 😞

[Janek]

So i tried to get the lost device back to working status by using the wall shutter switches but that also did not work. had to power cycle the unit and then it came back on.

i tried some other shutters as well, and in another shutter i noticed some delays and eventually got an error message from HA.

this shutter is in another room on the other side of the house, so i doubt this one somehow hops through the 1st shutter in another room that went bad.

i have tried to rebuild the routes several times now, so we'll see if that helps any, but i did this in the past too and it eventually failed.

not sure what more can be done in this regard.
I want to set up some automation for tilting and closing blinds through some scripts but i wonder whether it will be reliable at all. we'll see.

if there are any new firmwares to solve this, please let me know.

thanks

 

[Janek]

this is the latest device statistics from the device that was unavailable and had to power cycle it to get it working again.

the second picture is device statistics of another wave shutter that became unavailable today but luckily i was able to re-interview the device and after the 2nd time it was sucesfull and became live again.

so im not sure whats causing this random fallout of random wave shutter devices.

once it goes offline i cannot get any device info and since they drop out randomly over random period of time, not sure how i could even monitor it and try to get the data before it happens.

im open to any suggestions you may have.
Thanks for any help you can provide.

[Emmanuel P.]

Hi,

I have the same issue with 3 out of 6 Shelly qubino shutter. I’m not sure it’s linked to node or zwave. In fact :

- physical toggles do not work

- remote is not working with app ( eedomus zwave system)

- modules can be pinged, parameters changed  

So I have to reboot power supply several times a day to get appropriate behaviour  

I found some details of web regarding previous qubino module and explaining that modules can go in “security” mode “thinking” motor is out of serve. Solution should be changing parameters 76 and 85  I couldn’t find the right ones…

I’ve checked parameters of the 3 other modules. It’s the same but may be motor has not the same behaviour. 

I hope Shelly will give a solution…

 

Emmanuel

[Janek]

hey guys, well just to let you know, i have added a powered usb hub in front of the Aeotec usb stick and also moved it over to a more open location to improve the signal strength.

it seems that the amount of dropped packets has reduced and the shelly devices are reachable and do not go offline - or at least haven't gone offline to my knowledge.

so maybe you could try this too, to improve the signal reception and see if that helps you any.

not sure how the zwave network exactly works, if the transmitter transmits the signal until it gets some kind of return notification from the device and then it it stops transmitting the command, or if it just shoots it out there in hope that the device receives it and executes the comand. so not sure if a firmware is the issue or rather signal strength here. 🤷‍♂️
im sure its complicated protocol, so at this point just have to hope that the powered usb doesn't drag down the standard usb port on the Rpi and doesnt cause issues with HA. 

we'll see how it goes.

[Emmanuel P.]

Look, i’ve checked firmware version with  « COMMAND_CLASS_VERSION » command. 
The 3 modules without issue have the following result : …appversion[0c] appsubversion [11]. Which should be in hexa, so version 12.17

The 3 others with the disconnect issue give the following result : appversion [0c] appsubversion [0d]. so version 12.13

i will upgrade and give you feedback. Can you check version ?

[Shelly Wave help]

The version 12.13 have a known issue that was later fixed in the version 12.17, we advice to update the 12.13 versions at least to the 12.17, you may update them to the later versions too, but keep in mind that this will swap the orientation as it should be (by default the orientation was inverted)

Instead for the issues related to the Shutters when a scene is triggered the workaround for now is to use the automation instead of the scene. In most of the cases the issue occur when the Shutters are all triggered together, so if you do an automation that send the shutters in the position with a delay instead of using a scene that sends all the commands to the shutters at the same time the issue should be minimised if not completely avoided. Also a good practise is to disable the power reports, this will minimise the Z-Wave traffic which also help maintain the shutters working properly.