Probably a strange question...

I used to own Daikin airco's myself... And have build native support for it in Domoticz

Does this not work anymore?

No this is not an issue with Domoticz and has to be fixed by the one creating these config objects.
You, on the other hand, can edit/replace your own config object, and consider this a 'fix'
But it has to be fixed upstream.

Yes, that's why it's good to switch something independent like Zigbee2MQTT. Working great!

Hmmm I see, it is using the short format of all variables.... there is a "uniq_id" Ambientweather-F007TH-2-154-temperature_C Ambientweather-F007TH-2-154-humidity Ahh pfff now I see The configs are a bit of a mess... If you use short-format, stick to short format! :mrgreen: "device" should be "dev ...

No, inside the config object payload

Also strange that the stat payload start with +/+/ ... but that's not related

It indeed supports modbus. So you could create a python Domoticz plugin for this. Or a python application that runs in the background of your system and uses the Domoticz JSON API to publish it's values to Domoticz Advertisement is a bit tricky... No it does not support 100A, as it is just plugged ...

These are mine unique-id's

0x00158d0004a98668_temperature_zigbee2mqtt
0x00158d0004a98668_humidity_zigbee2mqtt
0x00158d0004a98668_pressure_zigbee2mqtt

There are no unique id's in the above config. That's a first issue... there is no way telling if they belong to each other

Yes it is the Unique ID you have to look at

Is it possible to describe more in detail what you would like to see, maybe with a illustrative picture as well?
Above which bubbles? Power Users?

It also works great with Zigbee2MQTT
(As well as the SNZB-02LD)

Yes it does
As mentioned, don't specify devices for the admin users (by default)

It is the way the config objects are created. For example, my zigbee temp+hum+baro is combined into one For example when using the below config payloads, it creates one combined sensor. Maybe you could ask openMQTTGateway to do the same (have a look at the unique_id) homeassistant/sensor ...

You don't need to clear your cache
F5 works fine, but should be solved

Could you create a github issue, and post the MQTT config topic+payload, as well as the status topic/payload?

I'm afraid not... this has been discussed before on the forum. I am by no means a CSS guru... and there are much better devs that could probably fix this. One fix would be to replace this text when creating a new widget and remote it from CSS If you give them all the same idea, you could probably ...

Thanks for the feedback. Maybe you could let the author of this tool know that it sometimes generates icons with 0 byte length

So it is now solved by a new P1 cable? The latest P1 Smart Meters have a different baud rate. I remember I had to buy a new cable as well.
These days I use a P1 reader from "Zuidwijk", the Ethernet version

You are more then welcome to fix this 'last-seen', it's a CSS limitation (or my limitation)

It is defined in legacy.css

You did not show the log of your last text output text=text.."Daily Average = "..trend.." Prognose: "..prognose But I will assume there are no error I created a dummy text sensor (idx = 10379) and the below dzVents script return { on = { timer = { 'every minute', -- causes the script to be called ...

You still did not answer the question if the widget looks good now after a day use