@akbooer
Since a couple of weeks/months, we are in the process to redo 5 rooms @ home (kids are moving from room to another room) and of course, I would need to redo a bunch of device name and room name in Zway..
Is there an easy way to tell openLuup to completely start over fresh without having to delete/rename them one by one in openLuup ?
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.
_John.
I have an odd issue which seems to be only for Fibaro wall plugs. They come in to Z-Way with two "electric meter" entrys, one "Power" meter and a couple of alarm entrys. In addition to the switch that is.
One of the "electric meters" is KWh and the other one is seemingly Watts, but it stays at 0/-1w. The "Power" meter shows the Watts used right now.
When these come into openluup, the wrong electric meter is selected for displaying the Watts, is there any way to manipulate which one openLuup uses? I see that the sub channel for power also is transferred, but it isn't in the data Veraflux is transmitting to my influxdb..
Haven't used the watts reading for anything before now, now i want to estimate when my dryer is done based on power usage. 🙂
Having some trouble getting the Fibaro TRV device working with the ZWay bridge. The device works in the ZWay (Zwave.Me) Smart Home GUI, and creates a number of devices in OpenLuup, some of which appear to have the right variables in it. Changing the XML and JSON files makes no difference.
I also tried creating a separate child device for Parameter 67 (using the gui for the ZWay bridge, see below), and setting the XML/JSON types for that device (like I've havd to do for a few other devices). This results in a device that correctly displays the TRV setpoint, but chaning the setpoint in the OpenLuup gui does not result in anything being transmitted to/by ZWay.
20490 49-0 D_ComboDevice1.xml zNode #49-0
49-0-113-8-12-A
49-0-113-8-13-A
49-0-113-8-14-A
49-0-113-8-15-A
49-0-113-9-3-A
49-0-64
49-0-67-1
20491 49-1 D_ComboDevice1.xml zNode #49-1
49-1-113-8-12-A
49-1-113-8-13-A
49-1-113-8-14-A
49-1-113-8-15-A
49-1-113-9-3-A
49-1-64
25031 49-1-67-1 D_Heater1.xml Radiator Bedroom
20492 49-2 D_ComboDevice1.xml multi #49-2
49-2-113-8-10-A
49-2-113-8-11-A
25030 49-2-49-1 D_TemperatureSensor1.xml Radiator Bedroom
I expect this document to be dynamic based on inputs from people who try but did not want to completely rewrite it here:
Z-Way/README.md at master · rafale77/Z-Way Z-Way/README.md at master · rafale77/Z-WayZway plugin for openLuup . Contribute to rafale77/Z-Way development by creating an account on GitHub.
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?)
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.
//ArcherS
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?
2f2566ba-1bb8-436e-a107-363bb66a7436-image.png
1a188194-faed-4d5c-8dc8-7a21914209fb-image.png
55a457fe-101e-4cb7-bced-3693d9f280c4-image.png
e9deae5c-79f1-407b-adb7-718663ab0149-image.png
Hi AK,
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.
С уважением,
Полторак Сергей
Z-Wave.Me
Why would that make you reluctant? It doesn’t seem to be any different from any other local startup supporting funds in other countries.
Fibaro TRV on ZWay/OpenLuup?
-
Having some trouble getting the Fibaro TRV device working with the ZWay bridge. The device works in the ZWay (Zwave.Me) Smart Home GUI, and creates a number of devices in OpenLuup, some of which appear to have the right variables in it. Changing the XML and JSON files makes no difference.
I also tried creating a separate child device for Parameter 67 (using the gui for the ZWay bridge, see below), and setting the XML/JSON types for that device (like I've havd to do for a few other devices). This results in a device that correctly displays the TRV setpoint, but chaning the setpoint in the OpenLuup gui does not result in anything being transmitted to/by ZWay.
20490 49-0 D_ComboDevice1.xml zNode #49-0
49-0-113-8-12-A
49-0-113-8-13-A
49-0-113-8-14-A
49-0-113-8-15-A
49-0-113-9-3-A
49-0-64
49-0-67-1
20491 49-1 D_ComboDevice1.xml zNode #49-1
49-1-113-8-12-A
49-1-113-8-13-A
49-1-113-8-14-A
49-1-113-8-15-A
49-1-113-9-3-A
49-1-64
25031 49-1-67-1 D_Heater1.xml Radiator Bedroom
20492 49-2 D_ComboDevice1.xml multi #49-2
49-2-113-8-10-A
49-2-113-8-11-A
25030 49-2-49-1 D_TemperatureSensor1.xml Radiator Bedroom -
They offer:
- On/Off control (In ZWay this is an On/Off button, in OpenLuup when using Vera it shows a single Heater1 device with Off/Heat operating modes)
- Current temperature
- Current Heating setpoint (read / write)
I'm not sure how these map to the variables in the above list, and some seem to be duplicated. BTW, device 25031 is a child device that I turned on manually in the plugin, in order to see if it could be controlled that way.
-
Update:
If I change Device 49-1 in the above list to a Heater1 device, it will not show the correct current setpoint, but when I change the setpoint on device 49-1, the thermostat will follow along.
If I go into the ZWay bridge config and tick Parameter 67 on Device 49-1 (49-1-67-1), I get an extra device that does show the correct current setpoint. Changing it on that new device will not result in the thermostat changing accordingly, however.
-
Alright, I just took a quick look at the bridge code and indeed... there are a lot of unsupported command classes:
49-1-113-8-12-A
49-1-113-8-13-A
49-1-113-8-14-A
49-1-113-8-15-A
49-1-113-9-3-ACould you tell me what each of the 113-8 and 113-9 correspond to? They should be some alarm sensor variables. Maybe we can automate the creation of a child device for each of them.
49-0-64
49-0-67-1This is where the bridge gets confused. The mix of command class this device has doesn't correspond to a known device type so it shows up as a combo device. I think if you manually change the device type to a D_HVAC_ZoneThermostat1, the setpoint should work though ideally, I would prefer to get the bridge to set it up as a heater device. Knowing what the CC113 correspond to would help.
Also do you know what the various instances correspond to? (The device creates instances 0, 1 and 2) This is the type of things which bug me about fibaro devices... Instances 0 and 1 appear identical while instance 2 is only a sensor. Do they correspond to a 2 zone control with the addition of an extra sensor?
Edit:
Ok I think I figured a couple of more things out:
Instance 2 is the temperature sensor. @Intveltr when you change temperature setpoint on z-way do both variables in both intance 0 and 1 change or only one of them? and which one is it? I am wondering if one of them is a dummy.
The reason why the bridge is not recognizing the device is because of the most bizarre implementation from fibaro to move the temperature sensor into a separate logic instance along with some non conflicting binary sensors (the command class 113). We have to customize the device recognition to correspond to this strange logic layout. Once I know what the instances 1 and 0 correspond to and what all these alarm sensors do, I should be able to provide support for it. -
I've no idea what those unsupported ones are. ZWay has a bunch of Fibaro Power Management Alarm and Fibaro System Alarm devices but I've no idea what they do.
I tried setting 49-0 and 49-1 to Heater1 and ZoneThermostat1 devices, but neither fully work. I can set the setpoint through them but they don't show the current setpoint, that only happens if I create a separate child device for 49-1-67-1 (and that child only displays the setpoint; it won't allow changing it).
By the way, yes, there are 2 very similar looking devices. This is mirrored in ZWay which has 2 devices to control the setpoint. Both will transmit new values to the TRV, but only one of them (49-1) will update the setpoint if I turn the radiator knob. It seems 49-0 is something of a dummy. Fibaro is known for bizarre ZWave implementations, which is also reflected in ZWay. Vera however will display this thing correctly (as a single Heater1 device). Personally, I can live with having the current temperature in a separate device though.
-
Can you do me a favor an try setting your 2 combo devices as if it was a thermostat instead of being a heater? D_HVAC_ZoneThermostat1.xml and D_HVAC_ZoneThermostat1.json?
I think your setpoint will work if you do it this way. All you would have to do would be to run a scene with a trigger on the temperature sensor CurrentTemperature variable to update the same variable in the thermostat. That would be the fastest workaround. Obviously Only the heat setpoint would work.
I am also attaching Z_Way2.lua.zip which you can test. Just delete all the devices associated with the fibaro and run a luup reload. It should create 2 thermostats and a temperature sensor. One of the two thermostat should have its setpoint functioning (The child one 20491).
-
@rafale77 I have tried before to change the device type manually and that didn't work for some reason. But after loading your new lua file and recreating the devices, this now works correctly, from the mobile app to Openluup to ZWay to the thermostat, and all the way back. The operating mode (off / heat) is also transmitted correctly.
Thanks!
