Nearly there with the migration ..
Is it ok to use older device files or do they get updated from time to time?
Now that a fresh openLuup is up and running and connected to Zway where's the best place to source device files without vera? I probably have them on another openLuup install but not 100% which ones to copy over.
I've finally gotten the stuff to work together. Now - before I migrate all the vera devices, how do i use this?
How does the variables NameDevices and CloneRooms work? (is there a manual or description of the plugin?)Set up rooms and names in Z-way? No rooms in z-way, and distribute them in openluup?
CloneRooms seems obvious, but is that the best way to go when I have more bridges?
I have an old Z-wave.me wall controller that I still use for turning the espresso machine on and off. The controller controls an Aeotec Micro Switch that for the moment is still on my Vera.
The wall controller has always been a bit tricky to work with on Vera. On my old UI5 VeraLite I managed to get it associated to the switch.
On the UI7 Vera I never got that to work, instead I could use it as a trigger in Reactor to detect when sl_SceneActivated was 1 or 0.
I have moved the wall controller to Z-way and there it is included as it should.
a30b06dd-1f3c-4ca6-9966-b0a6f183de04-image.png Compared to when it was connected to the Vera it has proper on/off buttons so that it can be controlled from the Z-way GUI.
The command classes are the following:
68a54e6b-b240-40b2-95bb-9696bf7789cf-image.png In OpenLuup it still shows up as it did in the Vera, i.e. only showing battery.
985acfb7-6af9-4cf0-a426-79d4358baf6e-image.png Is it possible to change device type so that it get the right properties in OpenLuup?
At the moment it does not have any useful properties except for battery level. It e.g. lacks the sl_SceneActivated variable.
Another step would then be to move the Aeotec switch to Z-way and to then associate the wall controller to the switch in Z-way. It seems as if this can be done in the ExpertUI.
I hope this is the correct forum – apologies if not!
I have a Raspberry Pi3 with a Razberry Z-Wave card installed. I have installed the Z-Way software and have successfully included a Fibaro Z-Wave switch on the Z-Wave network. I can toggle the switch on and off successfully from my laptop through port 8083 of the Raspberry Pi3.
On the same Raspberry Pi3 I have installed openLuup on which I have installed the Z-Way plugin. I can access this through port 3480 on the Raspberry Pi3 from my laptop.
Here is where I have come to a dead stop. How do I get access to the Fibaro Z-Wave switch from the openLuup application? I can find no documentation that tells me specifically how to do this.
Any help would be greatly appreciated.
Just finished migrating to Zway, Although there are some devices that are being detected as a dimmer when in fact are Shutters.
What would be the best route to properly change how this devices are being detected by the ZWay plugin on openluup?
I must be missing something but I am having now some devices fail on the bridge due to them running out of battery. Upon battery replacement, they function properly on z-way-server but the failure remains over the bridge. The failure shows up on the parent device and it says that a specific command class has failed. Looking at the return API json, it should not return any command class level failure however so I am not sure where the bridge gets its failed state from...
edit: Nevermind, I figured it out. It is a gap in data alignment between the different z-way APIs. The zwave and JS API got the update that the device recovered but not the smarthome API. Pausing and restarting the zwave app on z-way fixed it.
I noticed the change when I switched from the RaZberry to UZB (During the switch all devices moved to the Room 101 briefly, maybe that had something to do with it). Any idea why this would have happened? Can I easily change them all back to enabled? Also, what exactly does this attribute do? I only noticed because none of my z-wave devices were showing up in Imperihome and when I set the "disabled" attribute back to 0, the device shows up. Thanks.
So I started experimenting by moving some of my wallplugs and power switch zwave devices over from VeraPlus to Z-Way.
In Z-Way this results in different elements for switching, Watts and kWh. Some even have Volts which I never saw on Vera.
But using the Z-Way plugin in openLuup only the Switch element is visible and all other elements of the zwave node are not.
I don't really know to much about Z-Way or the plugin, but am trying to learn on the run.
Maybe someone can give me some pointers what and where to look for to solve this?
Just wanted to point out and start the topic of the following:
We are working on a project that will allow to use Z-Way library as the core of Z-Wave in Home Assistant. First releases will be around June/July I believe
Additionally there are ways to support Z-Way from HAss via HTTP requests. This is a community project and we have no deep knowledge about it.
С уважением,Apr 19, 2020 Official Z-way integration request Official Z-way integration request
Why would that make you reluctant? It doesn’t seem to be any different from any other local startup supporting funds in other countries.
Changing Device type from dimmer to Shutter
Have you tried just changing the device type?
It's while since I've looked at that code, and I certainly don't have any of that device type. What device filesedoes it use? There may be a command classes that I need to add to support this.
rafale77 last edited by rafale77
Change the device_file to "D_WindowCovering1.xml" making sure that this file exist in your openLuup installation (I think it came from the vera as I don't remember fiddling with it. category_num = 8
Changing the device type worked,
Currently ALTUI is unable to categorize any of the devices correctly. it sets all the device coming form the zway plugin to category_num: 0 It's kinda painful to go through every device and manually edit them, What would be the proper way to get the ZWay plugin to properly configure this devices, would adding the manufacturer's id to L_ZWay2.lua help?
It's kinda painful to go through every device and manually edit them,
...but pretty easy to write a short Lua script to do it?
IIRC, category is not an attribute currently encoded in the plugin. The whole idea is to make this far more flexible than Vera, and more able to support different Zwave devices without special coding.
therealdb last edited by
@akbooer can’t you just set it the first time and then make it user configurable?
This is the old database problem...
- identify the device
- look up characteristics in the database
- set the attributes.
The first two items are the problem, but particularly the second. I do not want to build and maintain a database of all possible devices. Vera never got this bit right.
A bit of manual configuration pain at the start for the user, or a lifetime of pain for me. That’s the trade off.
Couldn't it be optional with a cloud based database that is maintained by the community ?
Configuration really isn't something that you need to do very often... unless, of course, you are using this for lots of commercial installations.
therealdb last edited by
I feel your pain. But I was referring to the ability to read it from zway. Maybe they’re exposing this into as well.