Atrim 800 USB Controller Stuck at 7.17.2 #6816
Replies: 3 comments 5 replies
-
|
👋 Hey @ioguy! Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log on loglevel debug is required to diagnose most issues. Please consider uploading a logfile that captures your problem. As a reminder, here's how to create one: |
Beta Was this translation helpful? Give feedback.
-
|
File error 0x50 means the bootloader considers the update incompatible. How does the Atrim stick show up in Z-Wave JS UI? If they have their own IDS, you probably need their firmware and not the pre-built ones from Silabs. Have you asked Atrim support? |
Beta Was this translation helpful? Give feedback.
-
|
Shows up as: I've emailed Atrim 3 times - radio silence. Also can't find anything online about it. I'd just pickup a ZST39 but I don't want to be locked at Zooz's firmware levels. |
Beta Was this translation helpful? Give feedback.
-
Based on that, the default firmwares should work. No idea why they don't. |
Beta Was this translation helpful? Give feedback.
-
|
I just received a reply from Atrim (maybe they read these forums). Apparently it's an SiLabs bug where the memory allocation/partitioning is different 7.17 and it cannot be upgraded. 7.21.X may eventually have a fix for this. They pointed me to this discussion but there's not a lot of info, nor does an SiLabs employee confirm anything: Guess I'll just sit and wait. |
Beta Was this translation helpful? Give feedback.
-
|
I've seen that issue, but AFAIK it was specifically for upgrading to 7.20.0/1 and has been fixed since. Sit and wait it is then. |
Beta Was this translation helpful? Give feedback.
-
|
FYI, while I understand that it that should be no problem flashing the Silicon Labs Z-Wave 700 series or 800 series controller hardware, be warned that there is currently also an unrelated serious bug in all 7.19.x to 7.21.2 versions of Z-Wave Controller firmware (i.e. all firmware released after 7.18.8) that causes the Z-Wave Controller to randomly hang during transmission until it is restarted. It is currently unclear if this bug is fixed in a later firmware version." though Silabs have said they that they are aware and plan to fix it. So for now do not upgrade to anything higher than 7.18.8 firmware. As such it is currently not recommended to upgrade to anything higher than v7.18.8 is recommended today. See: "During the validation of the fix attempt we identified that the solution is not complete and with the refactoring efforts needed, it was not possible to integrate it into the 7.21.2 release. The team is well aware of the impact of this issue and is actively working on it with the highest priority. We will provide an update with the new ETA when confirmed by our R&D." You should also be aware there are additional known issues or bugs that can sometimes cause both TX Power Level + Measured Power Levels and/or RF Region settings to reset themselves when flashing Z-Wave Controller firmware upgrade, meaning that you sometimes manually have to re-configure those to correct settings after upgrade firmware, (the general recommendation there seems to be to upgrade one version at a time and not jump over a version). There are more related discussions here:
PS: Regardless of which Z-Wave Controller you are using, because Z-Wave radios use use low-power and UHF (Ultra High Frequency) to only send short packets which generally means relativly poor radio propagation though many types of building materials, the general best practice recommendation is to take preventive actions to avoid keeping sources of EMI/RMI/EMF-interference too close to the Z-Wave Controller adapter, and the easiest way to do so if you have a USB radio adapter/dongle is to connect it via long shielded USB extension cable to a USB 2.0 port or USB 2.0 hub to be able to get it a bit away on its own (as well as especially making sure to keep it away from USB 3.x/4.x ports/devices/peripherals/cables as such are infamous for causing EMI/RMI/EMF-interference that affect RF IoT devices. Of course, since Z-Wave network's range/coverage depends heavily on mesh networking by design you also want to make sure to add many always-on/always-connected/always-powered mains-powered Z-Wave devices at strategic locations in your home that act as Z-Wave Repeater devices (sometimes also referred to as Z-Wave Range Extenders or Z-Wave Routers). |
Beta Was this translation helpful? Give feedback.
-
|
I'm not concerned about the failed to transmit bug. My current system is on 7.21.3 and I get it locking up all the time - it hiccups and starts up again (I've never had to restart it myself). I want to switch to the 800 for the additional speed/range but unfortunately I can't NVM restore onto 7.17.2. |
Beta Was this translation helpful? Give feedback.
-
Just received a new Atrim 800 USB Controller and it came with firmware 7.17.2.
Using Z-Wave JS 12.5.6 to flash on a separate computer under docker.
I'm trying to update but having no success (in PC Controller or Z-Wave JS). I tried 7.18.0, 7.18.2, 7.18.8 and 7.21.2. I'm using BRD4204D which is what Atrim specifies on their website:
https://atrim.co/help/stick/atrim-stick-update-firmware-home-assistant-800-series.html
All give the following failure:
The SiLabs release notes does mention some info on upgrading from 7.17 but I'm not sure what to do (or if it relates):
Any ideas on how to get started or if I should just return it?
Software versions
No response
Device information
No response
Checklist
I made sure to provide a driver log on level debug.
The log includes a re-interview of the problematic device (if applicable).
The log includes the problematic interaction with the device (if applicable).
I provided the node ID of the problematic device (if applicable).
Upload Logfile
No response
Beta Was this translation helpful? Give feedback.
All reactions