Hello again,

I have redirected the log to the syslog facility. Now I have more info.

I have set the plugin in debug mode.
The heartbeat is set to 9 seconds and the action to 10 seconds. As a result the next action would fire 18 seconds after the previous one.

Feb 19 12:18:13 rpi3b domoticz ...

I have directed the log file to syslog facility.
Now I have to wait until the problem happens again.

We will see.

Thanks @willemd for your interventions here

The plugin was set with the heartbeat to a fixed 10 seconds and I did ask for a refresh every 10 seconds (this item is configurable in steps of 10).
I will shorten a bit the heartbeat to 9 seconds, and double the refresh.
I don't really understand how this works (my fault, I should have read the ...

As the error message originates from Domoticz itself and not from the plugin, I wonder whether I could receive a recommendation from the Domoticz community.
What can happen when Domoticz forks a thread ?
What can cause "Error: xxx hardware (x) thread seems to have ended unexpectedly " ?

Thanks @willemd for your answer :)

This is the first thing I have made in the beginning.
The dongle is working perfectly, I can query it both in API v1 and v2.

When it happens, some data structure or thread is probably in a stale state. I have found no other way to recover than restarting Domoticz ...

Hello,

UPDATE at the bottom of the conversation



I am currently running Domoticz 2024.7 on Debian 11.11, Python 3.9.2.
Using HomeWizard P1 Meter and the plugin from 'Eraser3'. ( https://github.com/Eraser3/HomeWizard-Wifi-p1-plugin/blob/main/plugin.py )
I have set the plugin to run every 10 ...

Hello,

I have a plugin (hardware item) supported by a Python script, that stops working after several days, and reports every 10 to 15 seconds in the log:
Error: <name> hardware (<idx>) thread seems to have ended unexpectedly
2025-12-16 14_30_53-Domoticz — Mozilla Firefox.png
The script polls a ...

Hello,
I am also using the abovementioned fork that fixes the values multiplied by 10.
Anyway, all the rest of the logic is the same then the original Eraser3 version.

I am experiencing random crashes that occur more or less after one week of activity. I don't know if an external factor causes ...

jvdz wrote: Sunday 30 November 2025 11:23 You mean the *1000

The telegram shows: The JSON shows Thanks to the firmware in the HoweWizard dongle, the conversion occurs there.

waltervl wrote: Saturday 29 November 2025 23:42 Seems the eraser3 plugin has an issue ...

Thank you ! The fork from Gettevan works just right ! my problem is solved !

I am a bit puzzled about the multiplication by 10 when the data is imported from the JSON in float() instead of int()...

for the plugin, also check topic https://forum.domoticz.com/viewtopic.php?p=293717#p293717


Thanks @waltervl ;) Unfortunately there is no useful info for me in this thread.

The Homewizard dongle reports correct values for instant watt consumption, but Domoticz shows values multiplied by 10 ...

Hello,

I am from Belgium. In our country we get the same model of smart meters as in Netherlands and other European countries, with the P1 port being a non-standard unidirectional reversed-polarity serial port, and a 5V power supply, fed via an RJ12.

I quickly purchased this device: https ...

Dear Walter,

I have typed the following commands on the Tasmota console: (as suggested here https://forum.domoticz.com/viewtopic.php?t=40656)

SwitchMode1 1
SwitchTopic1 0
Rule1 on Switch1#state=1 do Publish domoticz/in {"command": "switchlight", "idx": 203, "switchcmd": "On" } endon on Switch1 ...

Hello @waltervl

The message sent by the Tasmota device (door sensor) is:
(door opened)
domoticz/in = {"idx":203,"nvalue":1,"svalue":"","Battery":100,"RSSI":7}
(door closed)
domoticz/in = {"idx":203,"nvalue":0,"svalue":"","Battery":100,"RSSI":7}


What I did (and I may be wrong)

This is the ...

Hello, dear Community,

Version: Version 2024.7 (July 13th 2024)
Platform: RPi3B+, Debian 11.11
Plugin/Hardware: MQTT Client Gateway with LAN interface, other unrelated
Description:
I have set up a door sensor, based on a esp8266 Wemos, running the most recent version of Tasmota.

A Domoticz switch ...

Thanks, it is exactly what I wanted to achieve, have a nice day. Erem and you put me on the right way.

Frédéric

Hello Rob,

I have brought some debug commands in order to log more:

return {

on = { devices = { 98 }}, -- idx of button

execute = function(dz, item )
dz.log("state of " .. item.name .. " is " .. item.state)
if item.state == "1 Click" then
dz.log("switching 74 off")
dz.devices(74 ...

Hello dear Community,

I have acquired new shades and got them delivered with standard motors, one up and one down.
I have interfaced them with two standard 2-way NO/NC relays which work fine. (like Sonoff 4ch-Pro)
I have used Zigbee push-buttons configured as selectors : single push= open or close ...

SSL can be tricky.
Old protocols are e.g. SSLv3, TLS1.0
Newer include TLS1.2, 1.3.

There must be a matching protocol between the client and the server, and then a matching cipher.


The user manual https://manuals.sma.de/SBxx-1VL-40/en-US/3389030027.html seems to indicate that http is supported ...

If your SMA can be reached without SSL, please give it a try. (e.g. http on port 80)

If your Syno is really too old, it is possible that its openssl libraries do not support the underlying more recent TLS versions.