I also have a large number (>60) of Z wave devices and Z wave also accounts for the majority of my setup. I would definitely say go for it for the following reasons:
migration works very slickly in both directions (just read up in the forums and the support pages on how to do it) and it is widely reported on the forms to be slick
once you’ve migrated if you don’t see this issue immediately (I and many others have had no problems, not in any way diminishing the plight of those who have had serious ongoing issues) then you can take a full system local backup of HP2023 once you’ve got it set up well - that way you can always revert to that if you start seeing the issues with a later update
if you turn off automatic system updates on the HP2023 then each time you do a system upgrade you can take a local backup first, to make sure you are always able to revert
This action will create a full-system backup of Homey Pro, including settings, apps, experiments and the system software. A file that ends with .homeyprobackup will be created.
Restore Backup
This action will restore a full-system backup of Homey Pro, including settings, apps, experiments and the system software. Select the file that ends with .homeyprobackup you have created before.
You can not revert to previous firmware version, as I understood from Athom. So if you experience the issue, you are ****
Backup will not help, and trust me, I tried.
I’m astonished if that’s true since it directly contradicts literally the entire point of the local backup feature. I’m going to try it myself over the weekend now.
I mean if you migrate and it doesn’t work, you just turn off your HP2023 and Turn your HP2019 back on and carry on. A bit of zigbee repairing to do each way but that wasn’t too much bother.
Where did you read that? As far as I understood, when one z-wave controller takes over pairing of your devices, you can’t just turn on an old controller and have them re-pair with that again.
My understanding of how this works is that the migration from 2019 → 2023 means that the z-wave network on 2023 is an exact carbon copy of the z-wave network on 2019. So the 2023 doesn’t “take over pairing of your devices”; as far as the devices are concerned, it is your old z-wave controller. This is also why you cannot have both the 2019 and 2023 powered on at the same time after migration without serious issues - you would essentially have two identical controllers trying to run at the same time.
You can not revert to previous firmware version, as I understood from Athom. So if you experience the issue, you are ****
Backup will not help, and trust me, I tried.
This is incorrect. I have just reverted from 10.0.3 to 10.0.0 and back again using local backups. Of course, for backups to work you have to have taken a backup before you hit the problem. So if you suffer from the too much traffic issue as soon as you migrate to 2023 then this won’t help (and at that point you should revert to previous Homey Pro until this issue is fixed by Athom).
But if the problem is only triggered by an update to firmware, then as long as you remembered to take a local backup before upgrading the firmware then you can always revert to it if needed. So as I suggested above, turning off automatic system updates and making a local backup before each system upgrade is a safe way to proceed.
@Youri_Pasternak I think what Athom may have (correctly) told you is that there is no way to revert to a previous version of the firmware in place - i.e. without having to revert to a previous local backup. But reverting to a local backup makes it exactly is if nothing at all since that backup point ever happened, including firmware updates and (as I also verified in my experiment) adding new devices.
Since Athom has said they are working with Silabs on this, which is the manufacturer of the Z-Wave chip inside the new Homey, it’s can be a hardware issue (although more like a firmware issue), but it can also be an issue with the software talking with the chip. Hard to say.
I’m getting very worried about this.
This thread is growing quieter and it’s been weeks if not months now since my homey became pretty much useless.
There seems to be a few people in the know that claim that this is on a fix list but I haven’t read anything official from athom.
This is what frustrates me about athom. Why can’t they have an easily accessible list of known problems that they are working on. Instead of us just getting snippets of Information from moderators on here.
It’s all a bit amateur.
And I’m a bit fed up of getting my head bitten off on here because I’m sharing my frustration.
I agree 100%. The lack of communication is frustrating. Athom only reponses with “it’s on our list” with all the issues I reported. Very frustrating. I upgraded from HP2016 to HP2023 and sold my old Homey, so I cant go back. I fully regret buying this product, since I have no idea if the issues will ever be fixed.
I’d like to give you an update about the TRANSMIT_COMPLETE_FAIL error message.
You should know that of all known issues, this issue is the #1 issue we are working on to fix. We understand the frustration, so please know we’re doing everything we can. We’re even visiting customers’ homes with our analysers to get a better grasp on why this is happening.
We’re also working extremely close with Silicon Labs to solve this issue. It does seem to have happen only in the newer Z-Wave chip. Most likely it’s in their firmware, because ours didn’t change between HP19 and HP23, but we cannot say for sure until the issue is solved.
What’s so far been proven to be a workaround, is to exclude or power-off Z-Wave devices that have a very high TX or RX count in the Developer Tools. Some may be misconfigured, others may simply have a bug, but they do ‘flood’ the Z-Wave network, so no one else can come through. It may be that the Z-Wave chip used in HP19 did not care about this, and the newer does, but that’s speculation at this point.
We’re confident we will solve this issue in time, but please be patient with us, and if you have found a reproduction scenario with a possible fix, please shoot me a message directly!
— Emile
P.S. When restoring a USB Backup, the Z-Wave chip will be flashed with the same software in the backup. There’s no such thing as ‘not being able to go back’.
Thank you for the official answer from Athom and good that you’re working it.
The thing I’d like to add about the workaround is that every time it’s different Z-Wave nodes that are ‘too chatty’. It’s roller shutters, simple light switches, RGBW modules, sensors, thermostats and roof windows. Excluding them all would leave me without a smart home. I know, it’s just a work around, but I wanted to add my 2 cents.
Also, could you tell us why the log shows the same message from the same node 30-40x within one second, which could cause Z-Wave to crash? According to manufacturers the nodes themselves are not capable of this. And, the HP2019 does not show this problem in the log. At least in my situation (diagnostics and logs send multiple times) this seems to be a problem.
p.s. you’re still welcome here with you analysers.
Really good to hear Athom has this issue marked as high priority. Living with a Homey that is not functioning 30% of the time (even with all workarounds) is bearable, but only if I know Athom is working on it and it will be fixed. I still support a company like Athom, but to keep the enthousiasm up, I think something needs to change at Athom.
In my opinion Athom should inform his users better. At least provide a known issue list. With status updates. Don’t just close open tickets “when it is a known issue”, but keep the users updated (via a ticketing system). Show the amounts of users with a certain problem so priorities can be set and made visible. Same for the improvements / nice to haves. Let the users decide priority (vote) over new functions like dark mode, Energy, guest accounts or a customisable dashboard for example. I think that will make the community much more involved and understanding in a positive way.
Back to this topic: thanks again for you message. I really needed that. I can stop watching Home Assistant how-to video’s for now.
Thanks for your reply to this thread. On a global scale this is a banal problem for me, but at home it is causing alot of frustration. Much easier to wait out knowing that you are on the case. I do love the homey and there is no tempting alternative for me.
Hoping for swift resolution, Robin
