Hi @Mariano_Colmenarejo : In this version, it registered the first initial temperature, but no other since. Your previous version worked a lot better for me, as temp settings seemed responsive (was able to get temperature readings at shorter intervals).
In this version, I don’t see that option anymore, and so far, I don’t know if it will record another reading?
Can we bring back the last version?
The preferences that you had in the old profile were not valid for this firmware 2.5.
By default values should be sent with changes every 0.5ºc
I have added the preferences of this firmware 2.5:
Parameter 12 -Sensitivity to temperature changes according to fibaro manual:
The maximum acceptable difference between the last reported temperature and the current temperature read from the sensor. If the temperatures differ by the set value or more, a report with the current temperature value is sent to the device assigned to association group no. 3.
Available settings: 0 – 255 (0°C to 16°C) (32°F to 60.8°F)
Default setting: 8 (0.5°C)
Parameter size: 1 [byte]
To set an appropriate parameter value use the following formula:
x = delta T x 16 – for Celsius
x = delta T x 80 / 9 – for Fahrenheit
x = parameter value
delta T – maximum acceptable temperature gradient in Celsius or Fahrenheit
If the value is set to 0:
– if the wake-up interval is set to 255 seconds, temperature report will be sent according to the interval,
– if the wake-up interval is set to over 255, temperature report will be sent each ca. 4 minutes.
I have varied the limits from 0 to 255 (0º to 16º) by 0 to 127 0º to 8º), which are the ones that can be sent with 1 byte. And I have left the default at 0 so that it sends the temperature every 4 minutes.
You can calculate the value of the parameter with the temperature increase that you need to report, with the formula in the manual.
When you change the value you should wake up the sensor with the TMP button, according to the manual
Yes, the valves were directly connected to the RGBW outputs of the Fibaro 441 and I just had to switch pure R, G, B or W (in Vera and the old ST app) which was simple and cheap 8 years ago.
Thanks again for your help, Mariano! It´s very much appreciated!
@Mariano_Colmenarejo I am having trouble with your Z-wave Switch Mc driver with my qubino 2-relay device. Or maybe it’s just a problem with my configuration. I added the 2-relay device to ST using your driver. Then I created two virtual contact sensors to control the individual relays with Alexa. I made four routines in ST:
1-if either the Main or virtual switch 1 turn on, turn them both on
2-if either the Main or virtual switch 1 turn off, turn them both off
3-if either the Switch2 or virtual switch 2 turn on, turn them both on
4-if either the Switch2 or virtual switch 2 turn off, turn them both off
Unfortunately, when I turn on switch 2, within 5 minutes the main turns on. It seems like when switch 2 goes on, the device reports the main as on so then my routine turns on the main? Not sure what is going on. Any ideas for troubleshooting? Thanks!
@Mariano_Colmenarejo, hello again. So I used the settings to create child devices for both relays. Switch2 and the associated child device track well with each other and with the physical switch. The Main switch tracks with the physical switch but not the child Switch 1 device. The child device controls the light fine but if I switch the power in the parent device or with the physical switch, the child device does not track.