Hi @chris, thanks for replying. I am so happy to be wrong!
So I don’t think any of us on this thread own this new Homeseer switch yet but since you say it’s possible to control the params I will likely be purchasing one.
I would however love to learn how to add channels for parameters as I have other devices I would like to control in this way. May I suggest the following for you to update so we can learn how to do it on others:
I’m very excited about this feature for other deivces but do want to ask why you are concerned about keeping the number to a minimum? Why is it not a good idea to expose most/all configuration properties as channels?
I understand that some properties are unlikely to need to be changed after initial setup but I still think there will be devices with quite a few properties that make sense to expose as channels.
Simply because adding “hundreds” of channels into the system isn’t very nice. They appear in everyones PaperUI, and many people use automatic linking, so that means “hundreds” of extra items. If parameters are needed, then I have no issue adding them of course, but I don’t want to simply add a channel for every parameters if that’s what you are getting at?
Apologies in advance for my newbie question… I just installed the latest daily build of OH2.3 last night on my Pi. I have a Zwave+ USB stick connected and currently just one HS-WD200+ switch. I added the Zwave binding and searched for devices. While searching, I tapped the paddle up on the switch and OH found the switch but it reports it as an unknown device. I see it in the DB via a browser but it isn’t shown as a supported device. Originally I installed 2.2 stable and then upgraded to latest daily. I had to reinstall the Zwave binding afterward which I thought would give me the latest DB, yet the HS-WD200+ doesn’t show as a supported device within PaperUI. Am I doing something wrong (entirely possible since I’ve never touched OH before yesterday)? If not, do you have any idea when this switch will be supported?
I think that is what I am getting at, and understood.
For the WD200+ it of course makes sense to add channels for the config params that control the LEDs so it’s just a case of adding them to the DB entry.
I hope you would agree that the same could be said for the nightlight feature of the GE-45605 I mentioned.
Could you point me towards any information for adding a channel to the device DB for a config param? I am eager to add the ones I think would be useful but I haven’t found a simple guide to doing so.
Thanks
As I mentioned in my comment to Chris, I am not sure how to expose zwave config params as channels and as far as I can see the DB entry for the WD200+ does not have any of the config params exposed as channels as we would need. (I may be wrong as I don’t think I have ever seen a DB entry for a device with config params exposed ad channels so not sure what I am looking for)
Hopefully someone can explain to us how to do this and we can update the DB entry for this and other devices.
I didn’t look too hard to be honest, but if it’s needed, then let’s add it. I’m not trying to stop channels being added if they are really needed for normal use - I just ask that we don’t blindly add everything “just in case”
Below is an example of a device that has a parameter added - hopefully it explains what to do.
Fill in the exact same channel name (ie with config_decimal) and add the parameter=XX where XX is the parameter number.
That’s it… If there are options in the parameter configuration, the database will create a channel with these options when the database is exported. You can see this if you go and click on the export button at the top of the page -:
Fantastic! Thanks @chris this is exactly what I needed.
I have updated the GE 45605 and ‘requested review’.
Please remind me on the next steps - when the DB is exported what do I need to do to see the updates?
I use .things files and .items files to mange my devices and am running OH2.x
Thanks to the info from Chris above I think we have what we need in order to update the WD200+ DB entry to expose the config params as channels.
Looking at the DB entry however it shows a red warning and a yellow warning so this may be a reason why the device is not being recognised for you.
I am not sure how to fix this unfortunately.
If I click on Configuration->Bindings->Z-wave Binding, the HS-WD200+ is not in the “Supported Things” list. So, I don’t believe the version of the database containing the entry is in this version of the binding and waiting will not solve the problem in this case. I assume we need to wait for Chris to export the DB to the binding and it’s not something I can do myself locally. Maybe I’ll try to peruse the source for the binding and try to determine what version of the DB is contained within it.
Update: Looking at the source for the z-wave binding in GitHub, I can see that homeseer_hswd200 is not in the ESH-INF/things directory and the last commit to the master branch was 5 days ago. Looking in the DB, the device does exist was created 4 days ago, but it contains 2 errors. I’m going to register on the DB site and ask for permission to update as the errors seem trivial to fix.
@nealg Looks like Chris has updated the WD200+ entry in the DB. I am not sure of the steps to import the latest device changes - possibly just delete the thing and re-add it but I may be wrong. Anyway, you may have more luck adding it to now the errors are fixed.
Yes, I got a notification as I’m watching the repo in GitHub :-). I’ve already upgraded to the latest snapshot and it immediately recognized the device! I’ve created rules to turn the switch on/off at specific times and it’s working great! I even changed the LED to green (just playing around). Now I just need to figure out how to use the astro binding in the rule engine within PaperUI (is this possible in the current version?)
Hi @idean, I’m a newbie to OH2 and, so far, I don’t have any code examples. I created the device and rules entirely within PaperUI. Currently, I have the switch turning on/off at a specific time of day. I’d like to base the trigger for these rules on sunrise/sunset, but I haven’t determined if I can use the astro binding in the experimental rule engine in PaperUI. If not, I’m ok with editing flat files too and I’ve seen plenty of example on the use of astro for this purpose.
Anyone else have an example of using astro in the Rule Engine or is this not currently possible?
Update: I figured out how to do sunrise/sunset in PaperUI with the Astro binding. I had to do a scan with the Astro binding in inbox. It then added two new things: Local Moon & Local Sun. Editing the Local Sun thing, I clicked on Sunrise Start time channel and linked it to a new item. Then, I did the same for Sunset Start time. Then, I was able to trigger on “a trigger channel fires” and select the channel I had just linked: “Local Sun (set#event)” with event name “START” for the sunset rule and “Local Sun (rise#event)” and event name “END” for the sunrise rule. This is working for me.
I also notice that the nighltight change I made to the GE 45605 device is not showing up. i.e. There is not new channel available on the device. Even after removing and re-adding.
Are the latest database updates included in the 4th March version of the SECURITY binding?
I think the latest binding should include these channels. I guess the common issue is an old version is still running so I’d suggest to double check that the correct version is really running in the Karaf console.
If it is, then please provide the exact information provided by the binding about the device product codes as yours may be slightly different than the device in the database.
I have this switch working for the most part now in OH.
I have made quite a few updates to the device in the DB that are pending review. I added some comments to that page also as I am not sure how to surface the blink status of the LEDs since they all relate to a single bitmasked parameter. Plus the blink frequency setting is not working at all for me via OpenHAB. @chris - not sure if comments made in the DB device page go direct to your inbox or if they are just on the page itself -in either case, I would really appreciate your help with the two issues I mentioned to get this device fully integrated and controllable in OH.
Thanks!
. Probably I’ll do this tomorrow.
).