Most of our domotics events are automated, such as lamps, heating and aircos based on presence, time and temperature. However some events I was unable to automate, such as security camera verification, alerts and doorbell events. To handle these, I developed an android app called DomoticzApp. The ...

That is great information Walter. Thank you! I have added the Enever integration and will request a access token. At second thought I indeed also do not have partial shade. What type of inverters do you have since you imply multiple, but not mini. Indeed I want to use Zigbee enabled power monitors ...

After completing my domoticz adventure https://forum.domoticz.com/viewtopic.php?t=42719 I'm now venturing into solar energy. My requirements for this next step are as follows: * Solar panels combined with microinverters: maximizing energy efficiency at the panel level. * Integrating with a home ...

Hi, I just wanted to share the results of my domotics adventure over the last 15 months for fun and insight. I implemented a rather extensive Domoticz setup, and here are some key characteristics and lessons learned from the project: Zigbee: I set up 3 Zigbee networks, each with its own Zigbee2MQTT ...

The update in september.... I pinpointed the problem to the zigbee dimmers and zigbee setpoint devices. Autodiscovery often failed when restarting the rpi. Probably three zigbee networks with approx 80 zigbee devices (500 zigbee entities) is too much for auto discovery when restarting. Guess it's a ...

Light/Switches = 30 days Short logs: 1 day Check box not checked @Walter, does that answer your question? Memory issue over here is still solved. However all history is gone. It's a real bummer as my plan is to use OpenAI to see if I can optimize the energy usage, based on sun position, sunpower ...

I see the same error occurs with mysensor devices. What is your advice?

Ok, I'll ignore the setup list. Yes, it's another hardware/interface type. Do you imply that the autodiscovery feature in Domoticz for each interface type has been developed with different (source) code? Sorry haven't digged too deep into the code base (yet). Anyway, let's focus on MQTT. By ...

Again, am I the only one experiencing this with autodiscovery?

After some testing, another example. In this case with a Mysensors gateway.

On the hardware/setup page nothing is shown, in other tests most devices are shown, with or without mixed up texts.

Hi Walter, can you help me explain this on the page of the first link. 'After creation of the MQTT Autodiscover hardware in menu Setup - Hardware you can click on the setup button to configure the discovered devices if they have that option using Autodiscovery Number devices..' What I read is: If I ...

Lately I'm experiencing a troubling MQTT autodiscovery feature in Domoticz. Only 147 devices are recognized at once, which is far from the 1089 published in MQTT (99% are Zigbee devices). The consequence is that most MQTT connected devices are not accessible by Domoticz. The 147 devices (= entities ...

With a clean install and importing the data created memory leaks, while the present install with an older version of the database got rid of the memory leak.

Have you tried to export the database, mv domoticz domoticz.bak, reinstall with curl and then imported an older version of your database?

An update that hopefully shines some light on the matter: I have extracted the Domoticz dir from the backup (dd -> disk image) of july 2023 (2023.2) and installed that version on the RPI and manually copy pasted all scripts. Result: no memory leak. Then updated Domoticz to the latest version (2024.4 ...

I ran various tests last week. In my case, the more sensors I enable, the more memory leaks occur. Disabling all scripts does not make a difference. Additionally, the type of hardware (MQTT, Gateway USB, Gateway LAN) does not affect the issue. Disabling MQTT slows down the memory leak the most since ...

This is my setup: Raspberry Pi reference 2023-05-03 Raspbian GNU/Linux 11 (bullseye) Linux pi 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux Raspberry Pi 4 Model B Rev 1.5 Domoticz: Version: 2024.4 (build 15910) Build Hash: 0f2fcff99 Compile Date: 2024-02-10 12:56:24 dzVents ...

Today I installed the latest beta. Same issue persists.

Is it really that my instance is the only one that has memory leaks? If I start with a brand new install the same issue occurs. Cannot believe that I'm the only one having this issue.

I did some testing last weeks. The leak correlates with enabled hardware, not with any script. More enabled hardware = more memory leaking away. Herewith a image. memory leaks.png Yesterday evening I disabled most of the hardware. At 3:30 the daily restart occurs. At 9:00 I disabled all hardware ...

Yes I will start with that part.

@Kedi, I am afraid that I have to rebuild the system from scratch and step by step add configuration.