Z-Wave unresponsive and unreliable

When you sign in to https://support.homey.app/, you can view the ticket status by selecting ‘my activities’
It’s possible something went wrong with the email updates.

1 Like

Today I saw that I also have many TX errors and my z-wave have a lot of timeouts and it is unstable. I changed nothing. I did not installed newest updates.

I was using Homey 2019 pro for one year and I didn’t have such problem.

I am also using Homey 2023 pro Lan adapter - maybe this is the case.

@Stief are You also using LAN adapter?

I have a lot errors like this:

[2024-11-21T14:35:20.020Z] Transmit failed with TRANSMIT_COMPLETE_FAIL_PHY - txStatusReport: {“wTransmitTicks”:“0x0”,“bRepeaters”:“0x0”,“rssi_values_incoming_0”:“0x0”,“rssi_values_incoming_1”:“0x0”,“rssi_values_incoming_2”:“0x0”,“rssi_values_incoming_3”:“0x0”,“rssi_values_incoming_4”:“0x0”,“bACKChannelNo”:“0x0”,“bLastTxChannelNo”:“0x0”,“bRouteSchemeState”:“0x0”,“pLastUsedRoute_0”:“0x0”,“pLastUsedRoute_1”:“0x0”,“pLastUsedRoute_2”:“0x0”,“pLastUsedRoute_3”:“0x0”,“pLastUsedRoute_4”:“0x0”,“bRouteTries”:“0x0”,“bLastFailedLinkFrom”:“0x0”,“bLastFailedLinkTo”:“0x0”,“bUsedTxPower”:“0x0”,“bMeasuredNoiseFloor”:“0x0”,“bDestinationAckUsedTxPower”:“0x0”,“bDestinationAckMeasuredRssi”:“0x0”,“bDestinationAckMeasuredNoiseFloor”:“0x0”}

Anyone know how to read this error?

I sended request to Athom.

1 Like

Thanks for the suggestion, I’ve doubled checked and Wi-Fi is disconnected.

Thank you!
I just logged in and my issue is still open after 18 days. No reply from Athom yet, even though the mail stated:

Our estimated response time is 3 business days.

I’m glad to hear that I’m not alone.

I’m also using the LAN-adapter and I can see TRANSMIT_COMPLETE_FAIL_PHY as well as TRANSMIT_COMPLETE_NO_ACK in my log.

But in your ZWAVE list, the node 36 is broken. Seems it"s orphaned entry, in that case select REMOVE UNKNOWN NODEs.

hi,

Remove unknow nodes doesn’t work for me at all.

You must press it and wait…then press again and wait… repeat it even 2-3-4 times depending when the status changed and it will get removed.

Hi,

It worked but doesn’t helped with z-wave timeouts. Maybe the problem is Secure S2 connection with half of my devices.

When I first added all my Fibaro ZWave devices to my Homey (at the time I had a 2016 Pro), they were added securely.

I had problems with the Homey being sluggish sometimes.

At the time Athom (luckily) shared their source code for apps on GitHub. So I downloaded the Fibaro-app and updated the driver.compose.json for each device:

"zwave": {
        "includeSecure": false,
        ...
}

Following this guide I could install my updated Fibaro-app and re-add my devices. After that, my Homey felt like a different beast. :wink: Everything felt noticeably smoother compared to before.

Anyway, maybe this isn’t the case with the new Homey Pro 2023.

Hello,

Can You be more specific how did You do that? I know how to install aps with CLI method but can You send me link what Fibaro app You installed and how You change this inclideSecure to false?

When You install app from github You need to readd all devices from beginning?

There is more simple method, to enter pairing pin 00000 - or there was even app before in case there was no pairing pin (DSK key?) required [APP][Pro] UnZ-Cure (add z-wave devices unsecure) But you shall be okay with 00000.

Yet, I really wonder if this is the issue or solution you are looking for.

My z-wave died almost completly. Every second I have error. I cant even remove device and do anything. 2 hours ago everything was working fine. I updated system to new version meantime. I really don’t know what is going on.

All energy devices stopped to measure energy.

Share your ZWAVE dev. view again also check what you see in the field “Current command” and after try Homey restart / PTP.

I can’t see anything on current command. I restore backup from today morning but the same situation :frowning:

Thank You everyone for help but everything is ok for now. I turn off current in my whole house for 10s. After that everything is working ok and I don’t have any errors. Weird

2 Likes

@Lukasz_Kostek I’m not sure how to do it anymore, since Athom decided to stop sharing the source code for their apps.

But I guess it doesn’t matter since @Sharkys method is much easier. :slight_smile: :+1:

1 Like

Glad it helped your problem. In my case it didn’t. I still get a lot of duplicate commands being sent if I check my ZWave log in Homey Developer Tools.

Hi,

I think in my situation problem was caused by Qubino 3 phase metter. I changed settings (atachement) and now everything is working ok.

I am also using this flow to wake up qubino every 5 minuts (you have to change 155 to your Qubino node (171 or something)

I’m also sending the “Test”-command (0x20,0x02) to my Qubino Smart Meters every 15 minutes to keep them alive.

I’ve been doing it for a long time and It’s working very well.

1 Like