I've got a couple of these: https://nl.aliexpress.com/item/1005002496243227.html?gatewayAdapt=glo2nld&spm=a2g0o.order_list.0.0.187579d2jfsJxs They work fine with the Tuya app, and are correctly handled by HomeAssistant's LocalTuya integration. They are not detected by the Domiticz Tuya cloud plugin ...

Well, column HUMIDITY in table TEMPERATURE is of type INTEGER, so that settles it...

While on the topic: The docs say that the humidty value is a "PERCENTAGE (may be > 100)" but it doesn't say whether it is an integer or a float value. It seems that float values are rounded (truncated?) to integers, so no decimal precision. Is this intentional?

Hi, I have a NodeMCU running Tasmota 11 with a AM2301 (DHT22) connected to it. The devices are correctly picked up by the Tasmota Autodiscovery plugin. Values are shown correctly, but Domoticz does not keep a history for the humidity readings. Do I need to change a setting? scrot20220218081233.png ...

Did you try the Domoticz feature of Tasmota.

Read the docs and then Configuration > Configure Domoticz.

https://github.com/domoticz/domoticz/issues/5106
I hope that's what you wanted?

I'll do my best ;). Topic `homeassistant/light/F4FAA9_LI_1/config` {"name":"Bulb01","stat_t":"tele/bulb01/STATE","avty_t":"tele/bulb01/LWT","pl_avail":"Online","pl_not_avail":"Offline","cmd_t":"cmnd/bulb01/POWER","pl_off":"OFF","pl_on":"ON","stat_val_tpl":"{{value_json.POWER}}","uniq_id":"F4FAA9_LI ...

I'm not sufficiently familiar with MQTT autodiscovery so my first question would be: Is the config message sent by the lamp allright? If so, the discovery must be fixed in domoticz, otherwise it must (first) be fixed in Tasmota.

That's what I did in viewtopic.php?p=284797#p284797

Maybe... I'm pretty sure I manually removed all config messages for this device from mqtt (using MQTT Explorer).

But the problem is more that using MQTT autodetect the type is not correctly detected (i.e., just a dimmable light and not an RGBWW light).

Autodeterct works too good. It even detects devices I no not have (anymore). And it keeps detecting (and adding) devices even when I remove them. For example, I have a Tasmoto light bulb (Color switch, RGBWW, Dimmer) that is configured using a virtual device. Now we have autodetect, Domoticz detects ...

Another one: {"~":"ems-esp","uniq_id":"boiler_curburnpow","stat_t":"~/boiler_data","name":"Boiler burner current power","val_tpl":"{{value_json.curburnpow}}","unit_of_meas":"%","ic":"mdi:percent-outline","device_class":"power_factor","dev":{"ids":["ems-esp-boiler"]}} Under MQTT autodiscovery it is ...

Okay, here is one. {"name":"Bulb01","stat_t":"tele/bulb01/STATE","avty_t":"tele/bulb01/LWT","pl_avail":"Online","pl_not_avail":"Offline","cmd_t":"cmnd/bulb01/POWER","pl_off":"OFF","pl_on":"ON","stat_val_tpl":"{{value_json.POWER}}","uniq_id":"F4FAA9_LI_1","dev":{"ids":["F4FAA9"]},"bri_cmd_t":"cmnd ...

How can I intercept the device CONFIG MQTT message?

Given that many devices are wrongly identified this would be more than welcome. Mandatory, even.

I monitor my heating with an EMS-ESP gateway. This works excellent. Until recently this required a custom plugin but now it can use the new Domoticz MQTT autodectect. Great. Unfortunately, many of the sensors that had an appropriate type (e.g. General/Percentage) are now General/Custom. As a ...

So be it.

As far as I can see the link between rooms and devices is in the DeviceToPlansMap table in the database. So I decided to play foul...

Yes, that works for enable/disable. But I don't want to disable them, just stash in e.g. a room.

MQTT auto discovery yielded new hardware with some 80 sensors/settings. I want to group these so that I can view/hide them all at once. Is moving the items to a room the best way to do this? When moving items to a room, is there a way to multi-select candidates? Moving them one by one is a bit ...

Expensive. I use a USB 3 cableadapter (7,50 euro Pihut) and a SSD 240 GB 20 euro and a Raspbery Pi 4 and printed my own case. I blew up several USB3 ports on RPi and other computers with a cheap adapter cable. (Blew up = the USB3 port stopped ultraspeed and only functioned in highspeed (USB2) mode ...