Why are some my Z-Wave nodes not recognized in HABmin ?

[GertKonemann]

Chris,

Habmin fits each update better in openhab and starts getting really useful. To be able to use the configuration parameters of my Z-Wave devices in HABmin, recognition of the manufacturer and devicetype is essential. I have 5 Fibaro FGS221 devices of different versions, of which the newer ones are not recognized. Also my GreenWave Reality Powernodes are not recognized, nor is my AEON ZStick-2 (Node 1). Below you see my current devices in Homeseer 2 and in Habmin. I hope this helps getting habmin even more useful.

Gert Könemann

[cdjackson]

Hi Gert,

Yes, the device database needs all the different device IDs to be added - Fibaro especially have a habit of changing IDs for every new software version.

  I'll take a look at this and see if I can add the new devices.

  Cheers

Chris    

[GertKonemann]

Thanks Chris.

[cdjackson]

A couple of notes -: 1) I don't know (yet) why the S2 stick doesn't show up. The manufacturer is set to 0 which isn't correct - this is something in the binding and I haven't looked into it. I also have this stick and will take a look at it at some stage, but for now it's not too important since there's nothing to configure. 2) The type/id for your new Fibaro switches should have worked - I made a small change to the database (changes a lower case to upper case hex) so we'll see if that helps (I'd be a bit surprised, but we'll see). 3) I've added the other units. Unfortunately I'm in Germany at the moment and won't be home until Friday so can't test it until then. As soon as I've tested this I'll post an update. None of them have config, but at least they should be named correctly.

Cheers Chris

[GertKonemann]

1) You are right this is only cosmetic. 2) We will see if that helps. Can i see what the switches send back in a logfile ? I did not see it in the consolelog. 3) Thats nice. But most devices have something to configure. a. The GreenWave powerstrips have parameter 1 to configure, which is called the blinking timeout in minutes (max. 255). If the device is not polled within this time, a green ring around its mains switch start blinking to show the user that it has lost the connection with the controller (in this case openHAB). I did not find official documentation of this, but since I set this parameter, my devices stopped the irritant blinking. I will try to find links to the user documentation of the others tomorrow. Have a nice trip back home.

Gert

[cdjackson]

2) We will see if that helps. Can i see what the switches send back in a logfile ? I did not see it in the console log.

What do you mean? You can see the type/id in the XML, or in the device list in HABmin. This is about all that is displayed until you try and do something else. However, without the product database for the device, then you can’t really do much so that needs to be working so that HABmin knows what it can do... 3) Thats nice. But most devices have something to configure.

Hmmm - ok. I just looked in the pepper database and it didn’t have any config. So, either I found the wrong devices (which I don’t think so since the type/id were ok), or pepper doesn’t have all the info. If you can find some documentation I can implement the settings.

Cheers Chris

[cdjackson]

Ok - so I've found some information on the configuration - I'll try and add this tonight.

[GertKonemann]

Now the new Fibaro FGS221 are also recognized. The Everspring SF812 Smoke detector is probably also a device which is frequently used. The manual can be downloaded here http://zwave-products.co.uk/online/templatemedia/all_lang/resources/Everspring+SF812+Smoke+Detector.pdf I realised how much work you already did and how much there is still to do. Other software enables the user to configure unknown devices with supported commandclasses in a general way, like set parameter x to value y. Homeseer does that and warns to use that only if you know what you are doing. There will always be new devices, that are not yet known in openhab and this could help to start using them. Is that an idea for HABmin ? Thanks for your great work.

Gert

[cdjackson]

Hi Gert, Thanks - I’ll take a look at the smoke detector tomorrow or Saturday (I’m in Friedrechshafen at the moment and head home tomorrow afternoon0.

I added the Greenwave config today - I think the file should have been merged into the main repo today, so you might be able to compile the zwave binding with these files yourself. I’ll generate a new JAR when I get home anyway…

I agree having to have the XML files is a bit of a pain, but it does ensure that the devices are configured correctly. It may be possible to do something along the lines of what you’ve said - I’ll have a think about this. The files aren’t hard to make, and I hope that others can also generate them - the problem has been that the config database has not been in the main repo until today, so it’s been difficult for others to contribute…

Cheers Chris

On 17 Jan 2014, at 00:05, GertKonemann notifications@github.com wrote:

Now the new Fibaro FGS221 are also recognized. The Everspring SF812 Smoke detector is probably also a device which is frequently used. The manual can be downloaded here http://zwave-products.co.uk/online/templatemedia/all_lang/resources/Everspring+SF812+Smoke+Detector.pdf I realised how much work you already did and how much there is still to do. Other software enables the user to configure unknown devices with supported commandclasses in a general way, like set parameter x to value y. Homeseer does that and warns to use that only if you know what you are doing. There will always be new devices, that are not yet known in openhab and this could help to start using them. Is that an idea for HABmin ? Thanks for your great work.

Gert

— Reply to this email directly or view it on GitHub.

[cdjackson]

The latest files now include the greenwave devices. I'll take a look at the smoke detector tomorrow.

[cdjackson]

Actually, the smoke detector has no configuration, so the version in the binding now should be fine. It includes associations already.

[GertKonemann]

Now all my devices are recognized. Great ! A minor problem: The Everspring temperature and humidity sensor and the smoke detector have in habmin both productnumber ST814. The smoke detector should be SF812.

Gert

[cdjackson]

Yes, you’re right - I’ll fix the model numbers.

Thanks for testing.

Cheers Chris

On 18 Jan 2014, at 11:39, GertKonemann notifications@github.com wrote:

Now all my devices are recognized. Great ! A minor problem: The Everspring temperature and humidity sensor and the smoke detector have in habmin both productnumber ST814. The smoke detector should be SF812.

Gert

— Reply to this email directly or view it on GitHub.

[cdjackson]

I've pushed a new zwave binding which I hope fixes this and closes the issue. I'll push the update to openhab later.

[GertKonemann]

OK

Van: Chris Jackson [mailto:notifications@github.com] Verzonden: zaterdag 18 januari 2014 13:23 Aan: cdjackson/HABmin CC: GertKonemann Onderwerp: Re: [HABmin] Why are some my Z-Wave nodes not recognized in HABmin ? (#70)

I've pushed a new zwave binding which I hope fixes this and closes the issue. I'll push the update to openhab later.

— Reply to this email directly or view it on GitHub https://github.com/cdjackson/HABmin/issues/70#issuecomment-32680795 .Beschrijving: Afbeelding verwijderd door afzender.

[mkarnek]

Dear Chris,

First of all, great work with HABmin! The product looks very promising and nicely fills a gap for Zwave OpenHab users.

Secondly I would like to request to update the "products.xml" with some additional information, please see screenshot below.

The devices are as follows: Fibaro Universal Dimmer 500W (Firmware EU 2.2) = ID:100a,Type:100 Fibaro Relay Switch 1x3kW = ID:100a,Type:400 Aeon Labs Micros Smart Switch (2nd Edition) = Shows up as "4-IN-1 MULTISENSOR 4-IN-1 MULTISENSOR", not sure how to get you the ID and Type for this one.

If there is another preferred way to update the device database, please let me know.

Regards Martin

[cdjackson]

Hi Martin, I can easily update the Fibaro sensors with the extra type - I’ll do this shortly. Another user has submitted a pull request to openHAB for the 4 in 1 sensor - I’ll merge that into my development branch and we can see if that fixes the issues and take it from there…

The “preferred” way to update devices is to branch the openhab repository and modify the files, but it’s simple for me to do this so it’s easier for me to make the mods.

Cheers Chris

[mkarnek]

Hi Chris,

Thank you for your prompt response! I am still very new to GitHub and are currently finding by way around so not quite ready to branch just anything yet.

Regards Martin

On Sun, Jan 19, 2014 at 7:51 PM, Chris Jackson notifications@github.comwrote:

Hi Martin, I can easily update the Fibaro sensors with the extra type - I’ll do this shortly. Another user has submitted a pull request to openHAB for the 4 in 1 sensor - I’ll merge that into my development branch and we can see if that fixes the issues and take it from there…

The “preferred” way to update devices is to branch the openhab repository and modify the files, but it’s simple for me to do this so it’s easier for me to make the mods.

Cheers Chris

— Reply to this email directly or view it on GitHubhttps://github.com/cdjackson/HABmin/issues/70#issuecomment-32716183 .

[cdjackson]

No probs.

I’ve pulled the new updates and they already include at least the Fibaro updates for your device. I’ll compile it up and put it on Github and you can see how it looks…

Cheers Chris