When updating Zooz device firmware that includes either new parameters or new values for existing parameters, the Zbox hub generally doesn’t have an updated template to expose those new parameters. It would be useful if the firmware page for a device had links to associated parameter templates for each firmware version that changes the parameters.
As an example, the ZEN04 firmware was updated recently to add parameters 14 and 15, and also changes the values for parameters 5, 7, and 8. When I updated my ZEN04 to this latest firmware today, my template was reverted (from my custom one that had up to parameter 13) to an older template that only has up to parameter 9 and none of the new values. My Zbox hub is on the latest firmware (5.170.17).
I know I can make my own template to add the new values, but I’m sure Zooz already has the updated templates internally since they would need them for testing. It would be a big time savings if Zooz would publish those templates on the firmware page for us all. Or if they are already somewhere and I just missed them, could someone point me at them?
This would definitely be a time savings, @zoozer! I’ve also modified existing parameter files, creating custom .json files with updated parameters and very much appreciate what you mean.
As a side note, I have usually shared the updated parameter files with the Zooz/Z-Box Support team and they appreciate the input. It may also help them verify current support and, possibly, share the updated parameter files with other customers.
Im in the same boat. I have all zoos hardware; zboz and zen 30 switches. It’s crazy that the zbox is not aware of the new parameters. Zooz what is the fix for this, hacking together my own json file is a piss poor solution?
Have you contacted Z-Box / Zooz Support? I’ve found them very responsive and, for a particular device (you mention ZEN30 switches), they may have updated .json files already “in the can” that they may share with you prior to their release in a Z-Box update.
You could also ask others here on the forum, who may be willing to help you out with specific devices or issues.
Hey @Barkis and @silverf1re , we’re currently working on this! We will have a file accessible to our Z-Box users that will contain an updated json file for each device, so they can be loaded as needed. Thanks for your patience, as it takes some time to gather all files and prepare them for publication
@silverf1re thank you for the follow up! It is currently in progress, and we should have the files ready for publication in a few weeks. At this time, we have not confirmed the location of the publication, but likely in our Knowledge Base, similar to the firmware files. We’ll definitely be sure to announce and link it here as well.
We’re currently updating the JSON files for the Z-Box hub and plan to upload them to our GitHub repository, with direct links provided in our KB article.
Could you let us know which specific Zooz devices you’d like us to prioritize for the JSON file updates? With over 35 Zooz devices in our portfolio, we can tailor the updates based on community needs.
The short answer is yes You already might have a newer firmware version of your Zooz device, which Z-Box does not list the full parameter list in the current template.
Hey all, great news! The JSON Template article is ready with some of the links for the products. We currently have 8 JSON files completed and are working on more, but as we complete them they will be added to this document.
All new products released after March of 2025 will not need templates to show new parameters. We have updated the Configuration Command Class in the device firmware itself for these devices, so they will automatically provide the parameter name, descriptions and values without the need for the templates.
@zoozer Thank you for catching the issue with Parameter 14 — and apologies for the oversight! We’ll get that corrected right away.
As for Parameter 27, you’re absolutely right — it’s only available on 800 series devices running a specific firmware version. Since we create these templates manually, we chose to include all possible parameters to ensure full coverage. At the moment, we’re unable to assign specific profiles based on the device’s firmware version.
At this stage, we don’t see it as a major issue and prefer to have extra parameters listed rather than risk leaving out an important one.
