Pimoroni Enviro Grow board MQTT showing up but not device discovery

G’Day,

My Pimoroni Grow board (fully updated firmware) drops correctly (95% sure) MQTT messages into my H.A. (Core 2024.10.1) OS 13.01 , platform Generic x86-64 16Gb

MQTT listen to specific topic enviro/greenhouse-trays1 shows

Message 0 received on enviro/greenhouse-trays1 at 10:06:

{
“readings”: {
“pressure”: 1014.09,
“temperature”: 20.55,
“moisture_c”: 28.5,
“humidity”: 37.3,
“moisture_a”: 95.67,
“moisture_b”: 0,
“luminance”: 28.62
},
“nickname”: “greenhouse-trays1”,
“model”: “grow”,
“uid”: “e6614103e75c4937”,
“timestamp”: “2025-01-03T10:05:08Z”
}

QoS: 0 - Retain: true

In the device listing it does not show up , not with nickname greenhouse-trays1, nor model and in entities none of the soil readings (or any other show up either)

The log file of the Mosquitto broker (which does have discovery: tue btw) lists it connects (mentions Client name e6614103e75c4937 but not listed in devices under that name either). 192.168.1.12 is indeed the address for the grow board. user is tasmota since this is what I started with eons ago when adding tasmota to MQTT

2025-01-03 10:05:12: New client connected from 192.168.1.12:62977 as e6614103e75c4937 (p2, c1, k60, u’tasmota’).

2025-01-03 10:05:12: Client e6614103e75c4937 disconnected.

2025-01-03 10:05:25: Client 2tof1cel2cZGzTsUcUnInm closed its connection.

2025-01-03 10:05:43: New connection from 172.30.32.1:55509 on port 1883.

2025-01-03 10:05:43: New client connected from 172.30.32.1:55509 as 3P2kWjl9Hlwxl9xNwo9lM8 (p2, c1, k60, u’tasmota’).

2025-01-03 10:06:43: New connection from 172.30.32.2:35392 on port 1883.

*202-01-03 10:10:13: New connection from 192.168.1.12:54409 on port 1883.
2025-01-03 10:10:13: New client connected from 192.168.1.12:54409 as e6614103e75c4937 (p2, c1, k60, u’tasmota’).
2025-01-03 10:10:13: Client e6614103e75c4937 disconnected.

Not sure if I should start using differect MQTT protocol versions (currently on 3.1.1) since other MQTT topics seem to work fine.

Is there something in the json payload that is missing to make HA discover this ?