One strange issue I've noticed: I've got a LightwaveRF dimmer set up in Domoticz, and if I slide all the way to the right in the Reacticz icon, the dimmer only goes to 46% (as shown in Domoticz). If I slide to 100% in Domoticz (actually, 96%), Reacticz shows 0 (i.e., all grey).

Could this be to do with the fact that there are 31 steps in Domoticz for a LightwaveRF dimmer?

NietGiftig wrote:I just want to say that I'm going to use Reacticz as my main day-to-day user interface on my tablets.

Woot, thanks for your support

MikeF wrote:I've got a LightwaveRF dimmer set up in Domoticz, and if I slide all the way to the right in the Reacticz icon, the dimmer only goes to 46% (as shown in Domoticz). If I slide to 100% in Domoticz (actually, 96%), Reacticz shows 0 (i.e., all grey).
Could this be to do with the fact that there are 31 steps in Domoticz for a LightwaveRF dimmer?

Yes exactly, it sounds like it's the same issue G3rard reported here. The max value varies depending on the device and Reacticz was developed for Hue light (because that's the only type I have). It's a bit tricky to support other dimmers because MQTT is very limited in terms of the information it provides, but I'll find a way around. If you could add the JSON data for your device to the issue in github that would be greatly appreciated.

ptitneo wrote: It's a bit tricky to support other dimmers because MQTT is very limited in terms of the information it provides, but I'll find a way around.

Yes, the same problem i have encountered when I use Node-red.
The MQTT output is far from complete.
I think that @gizmocuz for some reason has no real interest in the mqtt thing, or lacks the time
But, that is his legitimate choice, but not good for developing
If only there was a generic hex colour / hue / brightness dummy device with MQTT output.
I (we) could do the rest in our own solutions.

Just do a little search on google, try "start mqtt with websockets" or something like that
So much info on the WEB, I do not have to repeat it here.
It costs me more time time to type my own findings then it cost your time to search it yourself.

Hi everyone, I've tried something to fix dimmers that have different max levels (basically it now calls the JSON API once to figure it out, while still relying on MQTT for updates). Let me know if it works for you !

PS: @NietGiftig "Hide Off level" in selector switches also works now (it uses the same improvement)

ptitneo wrote:Hi everyone, I've tried something to fix dimmers that have different max levels (basically it now calls the JSON API once to figure it out, while still relying on MQTT for updates). Let me know if it works for you !

Hi ptitneo,

Working OK now for LightwaveRF dimmer - thanks!
One minor issue is that, when I change level in Domoticz, Reacticz leaves a bar at its (Reacticz's) previous level:

MikeF wrote:
One minor issue is that, when I change level in Domoticz, Reacticz leaves a bar at its (Reacticz's) previous level:

Wow, that's weird This white bar represents the target value, immediately reflecting user input, and sent to Domoticz. The yellow area behind represents the actual value as returned by Domoticz. So normally they should be aligned (with a slight delay for the yellow area). The bar should always be positioned exactly where you click, is it not the case ? In your example it looks like you set roughly 40% as a target but the value returned by Domoticz is about 75%. Where did you click? And what was the real value then? If you know how to use the developer console, please give me the JSON request (and response) that Reacticz sends when you click on the dimmer.

Here's a few more screenshots.
1. Drag slider in Reacticz, Domoticz shows 65%:
2. Reduce to 37% in Domoticz:
3. Increase to 84% in Domoticz:

I've also noticed (sorry!) that if I turn the light off in Domoticz (i.e., click on the icon, rather than drag the slider), it goes off in Reacticz; however, when I turn it on again in Domoticz, it stays off in Reacticz.

Ah ok thanks, I understand now That's the expected behavior - I just didn't think about changing values alternatively using Domoticz and Reacticz. As I explained, the white bar is just a visual feedback to show that Reacticz is sending the command, it only reflects the local value that you manually set on Reacticz and doesn't get affected by the actual state of the dimmer (which is represented by the yellow area). This is by design. What I can do to make it less confusing is make the white bar simply disappear after a while, showing it back only when Reacticz is being used to set a new value.

Patrick wrote:Is there a way I can request a widget type? E.g. meter readouts from the Dutch P1 smartmeter? Or a contact from a MySensor?

Please create an issue on the github repository, it helps keeping track of the bugs and requests. Try to put as much information as possible eg what the JSON API returns, that commands can be sent and copy the data below the "unsupported device type" widget that you should be getting when selecting these devices in Reacticz today.