Issue solved!!!!

By adding these six lines in the mqtt_templates_gen2.txt as the last part of the section valid for the used base Shelly ("ShellyPlus1" in my case) I can finally see all devices from the Shelly AddOn in Domoticz!
topic=%discovery_prefix%/sensor/%shelly_id%-ext-3/temperature/config ...

I guess the MQTT Autodiscovery topic entries might also be a clue to why Domoticz are not picking up all the sensors, adding the parts related to this device here:

switch
shellyplus1-08b61fd95d44-0
config = {"name": "shellyplus1-08b61fd95d44 Relay 0", "cmd_t": "~rpc", "pl_off": "{\"id\":1,\"src ...

I can add for other users with problems using the Shelly Sensor Add-on that the Firmware in the "base-Shelly" might need to be updated, in my case I updated to the latest Firmware 20240223-141953/1.2.2-g7c39781 to get the menu's needed to manually activate all the sensor inputs. Without this manual ...

ShellyTeacher has been working great so far but now I'm facing an issue where I'm a bit stuck troubleshooting due to lack of knowledge of how "MQTT Autodiscovery" and ShellyTeacher works internally:

I added a ShellyPlus1 that worked all the way to and from Domoticz, BUT when I added a Shelly ...

Of course, stupid me!! :oops:
I took a photo of the settings that would be removed during the backup-restore and was so sure the name was Device_check but that was of course the name I had given this ”hardware” device myself and even though I went through the complete dropdown list several times I ...

Would you based on own experience with Domoticz recommend Aeotec Zi-Stick ZGA008 with Zigbee2MQTT and Domoticz Autodiscovery?

When deploying a new system I would prefer to buy a new/late design where I can buy replacement if needed for as long time as possible.

The SiLabs EFR32MG21 chip inside is ...

I`ve recently been evaluating all options for presence detection of mobile phones and found the ”Domoticz internal” Device_check found under Settings-Hardware-Type and then selecting ”Device_check” from the dropdown list as the only one still working on 2024 domoticz releases.

BUT, when I`m now ...

I've now tried, but cleaning the MQTT broker did not solve the complete problem as the broker stayed completely empty after reactivating zwavejs. (except $SYS and zwavejsAD/status=online after reboot of the complete system)

After enabling and analyzing logs and reading and learning more about MQTT ...

Thanks Gizmocuz!
Sounds reasonable. Will try that but it will take me a few days before I get a chance to try.

I can add that these are the Domoticz settings:
Domoticz Hardware.JPG
And this is how the MQTT looks from MQTT-Explorer where I expected the red marked data to change when either the Zwavejs-UI or Domoticz device switch position or physical sensor data is changed:
MQTT Explorer.JPG

I'm using ...

Following the Wiki: https://www.domoticz.com/wiki/Zwave-JS-UI I can now see (MQTT autodiscover) zwave devices in Domoticz and I can successfully change (physical) switch status directly through Zwavejs-UI control-panel, BUT changes in switch status and sensor measurements are not propagated to ...

Even though I`m a Noob I truly think we are on the right way to make Zwave-JS-UI easy to use and migrate to when using Domoticz. We might still have a few things to optimize but we can do and maintain this together!

I managed to get the mosquitto service to auto-restart on reboot but have a few ...