Jan Bouwhuis

This is interesting. I'm not having issues with `snmp` on python 3.12. What installation type are you using?

> Raspberry Pi OS Lite - Debian 12 (bookworm) Home Assistant Core in a Python venv Okay, I can confirm it works okay with HASS OS 11.5, with `pysnmp-lextudio==5.0.31`

MQTT device triggers be unique on the keys `device_id`, `type` and `subtype`. Duplicate triggers will not be set up.

@KoenKK can it be that device triggers that are supplied from Zigbee2Mqtt are not unique in all cases?

Related to https://github.com/Koenkk/zigbee2mqtt/issues/21158 Probably fixed with Zigbee2Mqtt 1.35.3. Closing as this is not an issue with Home Assistant Core

How did you add the MQTT entity? Is there any config payload or yaml config you can share for the entity? Is there anything in the logs? > When using...

If the device class is `date`, then your code does not respect that. What about: ```python ... try: if (payload_datetime := dt_util.parse_datetime(new_value)) is None and ( payload_datetime := datetime.fromtimestamp(float(payload)) )...

> > We have templates to parse timestamps. E.g. See https://www.home-assistant.io/docs/configuration/templating/#time > > Example: > > ``` > > {{ as_datetime(value) }} > > ``` > > > > >...

@emontnemery As we can use templates to parse UNIX EPOCH timestamps, do you still think it makes sense to add native support for this on MQTT sensors?

This PR will add an example for this case to the MQTT sensors documentation: https://github.com/home-assistant/home-assistant.io/pull/31287