I recently purchased another Bali (graber) zwave motorized blind. I have others I purchased a year ago. The initial blinds were recognized by Openhab as Somfy RSZ1 motorized shades, with 4 channels. The newest blind showed as unrecognized. The OpenSmartHouse Z-Wave database lists the RSZ1 type as 5253:5A31. The Bali rep told me that the motor had been updated, and the Openhab xml file shows the new types as 5252:5A42. Following Bob Eckhoff’s excellent tutorials, I extracted the rsz1 xml file from my existing zwave binding xml. My current zwave binding xml is version 4.1.0. I edited the manufacturerRef parameter and added 5252:5A42 to the manufacturerRef property. Then I added the rsz1 xml back into the binding jar and used bundle:update command from the openhab console. After restarting Openhab the new blind was recognized and works perfectly.
At this point, I know that the OpenSmartHouse database needs to be updated to include the new type, 5252:5A42. I don’t have a login access to update the database, and haven’t tried to get one for fear of goofing something up, but hopefully an experienced zwave database person could make the change.
It’s pretty fool proof to add a new DB entry when you have the XML file. IIRC you upload the file and most everything gets filled in for you. You just need to add some stuff like a link to the device manual PDF, description, and stuff like that. All the important stuff comes from the XML file.
And I believe changes get reviewed so if you do mess something up pretty bad at least a second pair of eyes will hopefully catch it. But given you have a working XML I think it’s going to be very low risk.
If the existing binding XML works with the new TYPE:ID to your satisfaction, I’ll add it for you. If there are missing parameters or other things, you’ll have to follow the above advice to upload the newer XML. Let me know.
By adding the new TYPE:ID, it generated the same channels as the other Bali blinds that I have. The channels it generates are Switch, Rollershutter, Dimmer[Deprecated], and Battery Level. I only use 2 of them, Rollershutter, and Battery Level. So everything works as I hoped. I’ve written rules to open and close the blinds based on astro sun data.
I spoke with the Bali help desk and they indicated that the motor had probably been updated, but which is probably what changed the TYPE:ID, but the manufacturer etc. is the same as before.
BTW, in your instructions for updating the jar file, you mentioned the issue with the Openhab image didn’t have the jar command. I was able to examine the file using 7zip on my windows computer, but I updated it using the jar command on another raspberrypi 4 that has the standard Raspbian OS.
I bet that would be your answer, so added it last night right before a DB update. It should be in the next 4.2 snapshot.
As to the jar update, there are other ways as noted in the post. The OH “issue” is just the Java JRE is typically installed and it is the Java JDK that has the “jar” command (IIRC). I have used BreeZIP like you have described also. As the XMLs are flat they can be modified without effecting the Java classes.
I was searching around for where to find the latest zwave jar file and started reading some of the documentation in the openHAB.org/addons/zwave/doc/things.html. For Graber, there are 3 model numbers listed, CSZ1, RSZ1, and VCZ1. My original blinds were discovered as RSZ1 items, so I figured the new one would be the same. But the categories listed in the documentation for the various model numbers are as follows, Blinds for CSZ1, Remote Control for RSZ1, and Remote Control for VCZ1. Shouldn’t the blinds be discovered as CSZ1 devices?
As for remote controllers, Bali offers 2 types, so it makes sense that there are 2 models for those. I have the fancier remote, but I haven’t tried to include it into Openhab. In fact, I have only paired the remote with one blind because I needed to reset the limits on one.
). The first part of this post has more detail.