Domoticz

azeph wrote: ↑Thursday 21 December 2023 0:08 Would it be possible to show the graphs from ShellyTeacher for Domoticz in the way that it is displayed with the Eraser3/HomeWizard-Wifi-Energy-Socket plugin? If that would be possible, it would be great!

Not sure if it solves your problem, but as i see your Shelly sensor is a Custom sensor. It may be better if you use an Energy type. Whats your Domoticz version?
As you must have seen in the ShellyTeacher README:
"Energy reporting needs at least Domoticz 2023 beta 15530 (watt-minute and watt-hour now supported)"

Thank you for your reply! I have the latest stable version of Domoticz, which is version 2023 2, build 15453. I am not sure how safe it is to use a beta version... Maybe it is the best to wait for the next stable version? The Shelly sensor is indeed a Custom sensor. After installation with the ShellyTeacher 6 Shelly devices appear in the Devices list and Shelly Energy has automatically obtained the Custom sensor type. I do not see how I can change the type.

azeph wrote: ↑Friday 22 December 2023 21:49 Thank you for your reply! I have the latest stable version of Domoticz, which is version 2023 2, build 15453. I am not sure how safe it is to use a beta version... Maybe it is the best to wait for the next stable version? The Shelly sensor is indeed a Custom sensor. After installation with the ShellyTeacher 6 Shelly devices appear in the Devices list and Shelly Energy has automatically obtained the Custom sensor type. I do not see how I can change the type.

2023.2 released July 21 2023, but "Wh" sensor (as Energy) support added at 08 Sep 2023. See: https://github.com/domoticz/domoticz/issues/5812
You cannot change the sensor type directly, first you have to upgrade to a Domoticz version which has this fix, than you have to delete Custom sensor and run ShellyTeacher again which will trigger the creation of the new Shelly Energy sensor.

Beta versions always have a chance to break things, so if you can live without this function until Domoticz 2024 first stable arrives, i recommend it.

I will wait for the next stable release. In the mean time I also tried the ShellyMQTT - Domoticz Python Plugin. When I follow the installation instructions, I see config/ status information in the MQTT Explorer, but no data. This is most likely because "Use custom prefix" is enabled. I do however not see where I can disable this. I do not see a possibility in the settings of Domoticz and also not in the MQTT settings when I use contact the Shelly Plus Plug S directly via the webinterface. How can I disable "Use custom prefix"?

azeph wrote: ↑Sunday 24 December 2023 14:52 In the mean time I also tried the ShellyMQTT - Domoticz Python Plugin. When I follow the installation instructions, I see config/ status information in the MQTT Explorer, but no data. This is most likely because "Use custom prefix" is enabled. I do however not see where I can disable this. I do not see a possibility in the settings of Domoticz and also not in the MQTT settings when I use contact the Shelly Plus Plug S directly via the webinterface. How can I disable "Use custom prefix"?

Sorry i do not understand your question. Shelly Plus Plug S is a Gen2 device which is not supported by the old ShellyMQTT plugin, as you can see it in the readme - by the way ShellyMQTT python plugin is not supported anymore, as its a dead end.

I read in the readme that the Shelly Plug S is supported by the old Shelly MQTT plugin. I thought it might also work for the Shell Plus Prug S, but that is not correct. Thank you for making that clear and for your quick replies. Very helpful for me.

Hi all,

I'm being forwarded to this topic from this topic viewtopic.php?t=41368.
Anyone else here experiencing the same issue?

I'am experience the same problems since update 2024-2 yesterday. I'am back to 2024-1 because my zigbee devices did not work anymore and in 2024-1 everything works fine.

supoos wrote: ↑Wednesday 17 January 2024 13:54 I'am experience the same problems since update 2024-2 yesterday. I'am back to 2024-1 because my zigbee devices did not work anymore and in 2024-1 everything works fine.

DO I understand correctly that u use Zigbee devices with the same issue with MQTT Autodiscovery?
This would namely mean the issue is more generic and not specific to Shelly.....

Yes, exact the same as you described but I'am a new one and not able to do so much research so I decided to go back to 2024-1 and waiting.

I have just upgrade my Domoticz to V2024.2
And MQTT Shelly devices working fine for me, after the upgrade. Although i had upgraded the system from a beta version, not from 2024.1.

mmzzz strange wondering with the issue could be and why for example also user supoos encounters the same issue....

@Supoos If Zigbee2MQTT is not working with MQTT Auto discover gateway there would be a lot of more issues. So it seems something specific on your system (make a new topic to discuss it separately).

I also would advise not to discuss Zigbee2MQTT in this forum topic and keep it on ShellyTeacher.

When I rerun the shellyteacher4domo python the devices are found now.

I am using Domoticz Version: 2024.2 (build 15864) with Shelly MQTT Autodiscovery plugin and shellyteacher.

I have successfully added a Shelly TRV, can control it, and status updates via MQTT.

I have now noticed, I have to re-run shellyteacher when I restart Domoticz, because Domoticz can no longer communicate with the TRV.

MQTT settings in TRV are:
- No custom prefix
- Clean Session: checked
- Retain: checked

Any hints?

Quax1507 wrote: ↑Friday 19 January 2024 11:43 MQTT settings in TRV are:
- Retain: checked

Any hints?

Your mosquitto MQTT broker has to be configured to handle retain.
https://pagefault.blog/2020/02/05/how-t ... tt-broker/

Hint: if you reboot your system, open an MQTT client, such as "MQTT Explorer" and you see that homeassistant/ (or whatever you autodiscovery topic) is empty, than your mqtt broker's retain function does not work.

Thank You for Your answer.

I tried restarting mosquitto servive, whicj is my MQTT broker and all messages come back immediately. So this does not seem to be the problem.
I also have other Shelly devices for testing... for example, my 2PM works flawlessly after restarting Domoticz.

Any other idea?

Quax1507 wrote: ↑Saturday 20 January 2024 9:13 Thank You for Your answer.

I tried restarting mosquitto servive, whicj is my MQTT broker and all messages come back immediately. So this does not seem to be the problem.
I also have other Shelly devices for testing... for example, my 2PM works flawlessly after restarting Domoticz.

Any other idea?

OK, I fixed it. "Retain" was not enabled in teacher

Quax1507 wrote: ↑Sunday 21 January 2024 11:44

Quax1507 wrote: ↑Saturday 20 January 2024 9:13 Thank You for Your answer.

I tried restarting mosquitto servive, whicj is my MQTT broker and all messages come back immediately. So this does not seem to be the problem.
I also have other Shelly devices for testing... for example, my 2PM works flawlessly after restarting Domoticz.

Any other idea?

OK, I fixed it. "Retain" was not enabled in teacher

I just ran into the next problem

I have included a "Shelly Motion 2" with teacher.

The following devices were created:

The problem is, that only Lux and Temp are updated when a motion or tamper is triggered.
Any help is appreciated