remcok wrote: ↑Wednesday 06 July 2022 1:20 I created a plugin for Domoticz for local readout of a GoodWe inverter via modbus over UDP.

Could you add throtteling function? Similar to this

On Github I made a suggestion on how to

When my RPI is rebooted, Domo keeps crashing. It only restarts after I manually switch off the pinger and goodwe hardware (modifying the DB). I don't know how to read the crashlog, so I don't know which of those two causes the crash. Who could point me in the right direction? Logfile contents: [New ...

gizmocuz wrote: ↑Tuesday 18 March 2025 8:59 In your router forward a strange port like 3562 to port 443 of Domoticz,

Strange ports are just a security illusion: Shodan

gizmocuz wrote: ↑Monday 31 March 2025 12:50 In the past.

So, in the resent 3/4 years, can you mention a mayor change that was not backwards compatible?

Well Zigbee2MQTT has upgraded to V2.x.
The Domo beta has support for that, but the stable not yet, so it would be nice to seal that gap.

Better not expose your domo to the web.
If you need to access your domo instance from outdoors, use a VPN.
Most modem/routers support vpn server, if yours does not, get one that does.

Use adapter type: zstack.

Next: specify the right adapterport: here

MQTT not (correct) installed/configured:

https://randomnerdtutorials.com/how-to- ... pberry-pi/

JanJaap wrote: ↑Sunday 26 January 2025 19:36 So I just pushed a change to log only 1 line per update as the other 3 didn't make much sense....

That already saves 66%, thanks!

Is there a way to disable the logging for 'info' status?

I noticed that the log file grows very large, about 1 MB per day (in my case: goodwe Goodwe.log). domo V2024.7 plugin 4.0.1 Raspbian Bookworm (32 bit) RPI4 What is wrong? Here's a snippet of the file 2025-01-26 17:15:15,657 - INFO - GoodWe.py - PowerStation created: 'b1193c2f-ad19-419c-bb41-xxxx ...

If auto-backup is enabled, use a backup from an hour ago.

waltervl wrote: ↑Monday 12 August 2024 0:12 I never has seen

Code: Select all

do return end

In a dzvents script. What should it do?

It prevents the rest of the script from executing.
Normally used in httpresponses, not really needed in this case, but it does no harm.

I have multiple energy measuring devices, from different manufactureres, all zigbee (MQTT, autodiscovery). The purpose was to monitor the update frequency to determine the stability of the zigbee network. The results got me flabbercasted, the amount of updates/triggers is INSANE. What is happening ...

Perhaps the mobile dashboard works for you, this makes a list from your dashboard.

Goto:settings and change the user interface to Mobile.

nonolk wrote: ↑Thursday 11 April 2024 13:57 So you mean everythings, Domotics and Zigbee2mqtt.

Yes, everything.
But using the old installation(data) as a backup, it only took me a couple of hours, which is less time than spend on 'debugging'.

nonolk wrote: ↑Wednesday 10 April 2024 15:54 Could you please eleaborate on what you mean by i took a clean image ?

format drive, start from scratch.

I used Suncalc Next, use the Suncalc in an other python3 script (below) and call it from crontab. import socketserver import urllib.request import math from datetime import datetime, timedelta from suncalc import get_position, get_times date = datetime.utcnow() + timedelta(hours=2) lon=4 ...

The problem is 'solved'. I took a clean image, and reinstalled everything. Now MQTT is recovering after a restart. Battery operated devices also recover, but only after being actuated, first signal/command/data is lost. I'm running Bullseye now, because some plugins didn't work on Bookworm. (32 bit ...

As I wrote in the in the first post, i have 3 RPI's from who 2 make the connection and only one does not make a connection at boot, only manual with "sudo mount -a" The mount cmd also uses the same line as in fstab, so it is not permission and/or in .smbcredits Is the difference in network ...

Is the line "//172.16.10.120/Backup/Pi246 /mnt/WDCloud cifs credentials=/home/pi/.smbcredits 0 0" in /etc/fstab ?

It is probably in the permissions of ".smbcredits"

Found a workaround, this is working for most devices, except for battery operated devices that don't report often, like pushbuttons or motion sensors. While domoticz is running: stop zigbee2mqtt, clear mqtt broker, start zigbee2mqtt. This can also be done 'automatically': Im my case the Auto ...