effing: You need to update to the latest version of the plugin where this should be fixed

Fixed now.

- If I were to change the name within the Sonoff device, would this then ripple through via auto discovery and update the name of the device within Domoticz, Or would it create 'new' devices? No, a new device would only be created if you change the "topic" of your device. Also the name you set in ...

Domoticz auto discover the sonoff devices and I can control them with domoticz or Hardware button. But if I stop domoticz service, manually change relais status and then re-enable domoticz, the status of the relais are not updated anymore. This should definitely work.. If you're willing to give it ...

I've been fiddling around with this plugin this evening to try to get it to work.. A bit of a noob with MQTT and Tasmoda but it seems to work since the Domoticz logs show the status change of the sonoff But when I flip the switch (so to speak) in Domoticz, the switch goes off but the status doesn't ...

mvveelen wrote: ↑Saturday 11 August 2018 20:19 After using the MQTT discovery for a while, I suddenly have some of the Sonoff devices being discovered as a "Dimmer" instead of the usual ON/OFF Switches.

Just to confirm, this is now fully solved by https://github.com/emontnemery/domoticz ... y/issues/8 ?

Can you try with latest beta?
It has improved logging of these kind of hangs, which will make it easier to debug.
(Please make backup of your database so you can go back to stable version after testing)

Using Domoticz Beta 9317 on Synology NAS Fibaro FGRGBWM441 Zwave Modul RGBW (CW) Stripe When trying to adjust brightness with all three pickers, changes are done but jump back to maximum brightness very quickly. In other words - brightness adjustment is not working. Color picking seems to be ...

<Deleted>

I'm not a lua user myself, but can't you just do something like: os.execute([[curl 'http://127.0.0.1:30/json.htm?type=command&param=setcolbrightnessvalue&idx=123&color={"m":1,"t":0,"r":0,"g":0,"b":0,"cw":255,"ww":255}&brightness=50']])

This is not purpose of slave switch. Purpose of slave switch is to update state of main switch without sending a command to the switch . This is useful for simple RF switches (meaning they don't report state) with several remotes: If you press one of the remotes, Domoticz state will update to try to ...

If the hue light does not support changing color or changing color temperature but just on/off or dimming, it will be added as Lighting 2.
Why do you want it added as Lighting 2, is it to have the dimmer slider show?

Updated WW / RGB/ RGBW / RGBWW support, as discussed on github: https://github.com/domoticz/domoticz/issues/2078 https://github.com/domoticz/domoticz/pull/2229 Summary: Color picker for dimmer updated with adjustable color temperature Possible to set colors other than fully saturated from Web UI ...

Please help test the build linked from here: https://github.com/domoticz/domoticz/issues/2078.
With it, it should be possible to create a "Dummy" RGB/RGBW/RGBWW device, and picked color will be stored in database and accessible through JSON Web API and announced oevr MQTT.

Hi!

This will work with the updated support for color dimmers being discussed here:
https://github.com/domoticz/domoticz/issues/2078

With this change, you can create a scene including your yeelight with a defined color temperature.

If you have time, please test the version linked from github.

Hi Reconos, did you ever get it working?

This sounds very interesting, do you have a little more documentation on the MQTT formating, Topic, payload, etc? I am currently using a custom nodered flow for controlling my lightify lighting, I tried to implement auto creation of the lights but it proved problematic in matching using the names ...

A patch has been submitted which should solve this.
Please send a PM if you are willing to test.

My Domoticz is using my 3.6.4 Python installation: 2018-02-04 15:17:10.318 Domoticz V3.8875 (c)2012-2018 GizMoCuz I have some time to look at this now, and I prepared a debug build which should hopefully helps narrow down why the onConnect callback does not work. Is PM working for you now in the ...

Run Git Pull and disable and enable the plugin and now i get this error

Sorry, please update again, it should be fixed now!