2020-02-28 14:15:37.545 Error: roborock hardware (19) thread seems to have ended unexpectedly but the vaccum seems to be connected anyway, is there a way to disable these error masseges? it fill my log all the time. try to set lower "Update interval" - in my case - 15s if I remember correctly there ...

for it to work again i need to remove the plugin and restart domoticz, then ad the plugin again for it to work. Do you really need to REMOVE the plugin? In my case this is "usual" way THIS plugin works - any changes can be applied only by restarting Domotics after re-configuring/restarting plugin ...

I want to add a second vacuum cleaner from same generation, what is de best solution for this? Because the added hardware does not contain parameters like IP adres, ID and token. Make copy of file miio_server.sh e.g. miio_server2.sh Update IP and TOKEN for new robot and change PORT (--port 22223 ...

I got the same problem with "import uuid".

@Dnpwwo
Great, thank you.

Why on chipset FTDI is problem ? May be not too late. Solution: https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=59420#p455407 In short: it's a hardware bug on the nano V3 boards (may be some other...). Pin 26 of FTDI should be connected to ground, but it's not. Solution is solder blob ...

Would of course be a bit much to ask if you could add color wheel support as well but will certainly look forward to that if you do decide to :) Currently Domoticz's RGB and RGBW switches sends to plugin only Color(Hue) and Brightness, but no Saturation. So it's very limited support to set Lifx ...

I got in some kind of problems, when using non-latin (cyrillic in my case) names for devices: myName="Тест" Domoticz.Log("myName = " + myName) Domoticz.Device(Name=myName, Unit=1, Type=244, Subtype=73, Switchtype=7).Create() Domoticz.Log("Device Created") Log: 2017-03-11 16:45:13.893 PluginSystem: St ...

@Dnpwwo, thank you.

With Domoticz 6905 and switch Type 244 everything work ok.

BTW, seems it's a typo in wiki example "E.g: Domoticz.Log(Device[2].Name)" should be "E.g: Domoticz.Log(Devices[2].Name)"

Hi @Dnpwwo, Domoticz V3.6905 accepted pull request #1308 I created device with Domoticz.Device(Name="Test", Unit=1, Type=244, Subtype=73, Switchtype=7, Used=1, DeviceID="aabbccddee").Create() Device with an ID(IDX) of "29" and DeviceID (ID) of "aabbccddee" is created and listed in "Devices" page ...

My first attempt to write Lifx control, using new Python plugin: Requires: • Latest Domoticz with Python plugins enabled (now beta V3.6675 and higher) • lightsd daemon by lopter https://github.com/lopter/lightsd Tested on raspberry pi. Plugin itself should work on windows, but daemon only on nixs sys ...

I can find "Plugin for UniPI" at the end of the dropdown list on the Hardware tab. That indicates the file is found by the plugin system, but it does not load. @ubee, I got in the same situation several times, without changing version of Domotics. Moreover – already added plugin continues work n ...

If you really need numbers that big I would suggest setting the heartbeat to 17 or 18 and doing what you want to do on every 4 call. Dnpwwo, thank you! Is it possible in any way to set DeviceID while creating device? It’s look like that now it is automatically generated. Can be useful for storing d ...

@Dnpwwo: if I set Heartbeat interval to 70 and more, and debugging in plugin is On, I start getting messages in log: 2017-01-30 14:16:00.539 Error: A1 hardware (9) thread seems to have ended unexpectedly message is logged every 30 seconds, except times when onHeartbeat called Plugin itself continues ...