-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No devices found #265
Comments
Does the log show that the HABmin JAR is starting correctly?
|
Hi Chris, yes it is started correctly. I can use all other features, except zwave binding :( |
Is the zwave binding listed in the list of bindings? If yes, when you click on it do you get the 3 or 4 tabs coming up on the right side? If yes, does the database explorer show anything? |
Hi Chris, |
tedcsi, Did you unzipped the zwave binding .jar file? I am actually getting a similar problem. I have openHAB2 and the log file show my z-wave Stick is recognized. However, I cannot see the z-wave device in HABmin2. |
Do check the product in zwave binding jar and see if your device is in there. I had to use zwave 1.8 binding jar instead of 1.7. The product database was updated in 1.8. |
The device list is not linked to the database. HABmin should show all devices linked to the controller even if they are not in the database (it won't of course give them a name if they aren't in the DB). |
I installed openHab with a Aeon Z-stick gen 5 (ZW090-C) and Aeon Multisensor 6 (ZW100-C), which is working properly. Created the items, and I see the sensor readings in the openHab log.
I'd like to use habmin to configure all, but it does not show any device when zwave binding is selected.
I realize I probably need to update the products database, but the Wiki states the following:
If the manufacturer and/or product aren't known, then the interface will list the manufacturer ID, device ID and device type. This will allow these devices to be added to the configuration database.
So i'd expect to at least see the devices in the list. Am I missing something here?
The text was updated successfully, but these errors were encountered: