@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!
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.
These are great not just for sensors, but also to ZWave-ify existing equipment in cases where a simple dry relay ZWave switch won't cut it. I had a few motorized transom windows with IR remotes, that can also be controlled through some weird industrial serial protocol. I build controllers for them using ZUNO boards, so I can now control the windows through OpenLuup.
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.
It's in the app store now 
Please let me know if it installs correctly
I'll put it in this weekend
They offer:
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.
@perh So would I I've made a major (and very expensive) effort a few years ago using Xamarin, but the Android part never worked very well, it took ages to start up and just parsing JSON files required whole seconds. I'm hoping to revisit this at some point since they have made huge improvements to Xamarin since then, but don't hold your breath; it's a huge effort.
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
All,
Due to changes in the push notification system by Apple, the plugin to send push notifications to HomeWave will have to be updated. Please use the link below. This plugin works on both Vera and OpenLuup platforms.
Push messages will continue to work with the old and the new plugin. Once the server and the HomeWave app are updated, the old plugin will stop working
I didn't actually wire 3 Horstmann relays in parallel, it's one relay, plus 2 Fibaro dry contact relays (can't use a double unit, you can't associate the Horstman thermostat with the 2nd relay in the double unit). You can buy Horstman thermostats separately and save some cash that way. They associate just fine with regular switches (I have one associated with an additional switch for a floor heating pump)
It's a bit of an issue. You can of course do this programatically if you have temperature sensors in all the rooms. But you'd have to drive the Horstmann relay programatically, which isn't ideal. The thermostat has some clever logic to drive your boiler in an optimal way (I think you can even set the boiler type in the Horstmann).
What I did: I put thermostats in the rooms that I want to have good temperature control in (3 rooms). The relay units near the boiler are simply wired in parallel: this defeats the cleverness of the boiler control... but only when more than one thermostat demands heat while being near its setpoint. The TRVs in those rooms are programmatically slaved to the thermostat: every so often the home controller reads the setpoint and updates the TRVs.
The TRVs in the other rooms are usually set to 14 degrees. At the moment I have them set so they go to 20 degrees when I turn the lights on in that room, and I close one of the boiler relays for 5 minutes to draw heat into the radiator. These are small rooms and this works well enough.
By the way, I'm getting some serious savings by not heating the rooms that are not in use during the day.
