I've tried to do some debugging in det code. I've modified the function ProcessInbound in class CPluginProtocolLine (PluginProtocols.cpp, line 101), so I got som debug information: void CPluginProtocolLine::ProcessInbound(const ReadEvent* Message) { CConnection* pConnection = Message->m_pConnection ...

I have now tried to turn on debug info in the Yamaha Plug-in and there are a lot of info, but no extra info about the error, only the text "Python exception set prior to callback 'onMessage'". Before I upgraded my server to Fedora 35 (and Python 3.10) everything was working.

I would like to give more information, but the text "Python exception set prior to callback 'onMessage'" is the only message I get. Can you maybe tell me how I can enable more logging.

Hi Right now I'm running Domoticz version 2022.1 (build 14268) on Fedora 35 and Phyton 3.10.2. I have installed some plug-ins in my Domoticz environment and the most of them are working without problems. But two of them says " Python exception set prior to callback 'onMessage' ", which results in no ...

According to issue 4487 (github) Domoticz still crashes on exit with Python 3.9.1 Domoticz crashes when there are some configuration changes to a Python Plugin. Can anyone say when this issue will be solved?

Thanks for the answer. I will try downgrading Python

I have now installed the package "gdb" on my Fedora 33, so I could get som more debug info. I have attached the log and all I've did was selecting the plugin and clicked the update button I've also did a fresh install of Fedora and a fresh compile of Domoticz on the newly create machine with the ...

I have a strange problem. I'm trying to develop af Python Plugin and every time i change ant parameters the plugin creates a segmentation fault. Even the base plugin template create a seg. fault when stopping the plugin. The log shows this: 2021-01-26 18:55:05.541 (Test) Processing 'onStopCallback ...

Sounds good. Are there any examples on how to use asyncio?

a thought: is it possible to use the asyncio module, ie async and await syntax in a plugin?

Many thanks, I will look at the examples to night

I'm developing a plugin and I need to be able to make about 20-30 simultaneous connections to a website.

I don't know how to make all these connections by using the connection object. Can anyone give me a hint?

I have a PHP script that updates some Dummy Switches in Domoticz. I have now chosen to use System Pinger instead and therefore need to see where I have used some of my Dummy Switches. Is it possible to get an overview of where a switch is used?

after running setcap, you need to restart your domoticz service. It took me a while to get it to work, and all I should do was to restart. @waaren, I'm stille looking into the problem I have with the script.I have create a complete test enviroment, so I think is should be possible for me to finde ...

I will give it a try tomorrow

I dont have a updatebeta in my domoticz folder. I have compiled domoticz today from github, so I think I'm on the latest build :-) Could it be something with dz.data or maybe cameraState? Are those datatypes saved ind the database or in th filesystem? I remember that I have some problems with the ...

I'm logging to a OS file in /var/log and the logfile does not contain any errors. I think there are som errors in my installation of Domoticz, but I can't find id.

I think the reset script dies at the line where "secondsAgo >= 20: true" should be printed without any error messages.

Just some extra info. All my existing dzVents scripts are working as expected

Yes, you are right, I misunderstood you, sorry. I have now tried the new script, but it only gave this in the log filen: 2020-07-24 21:34:54.185 (System Alive - Camera04) Lighting 2 (Ping - Camera04) 2020-07-24 21:34:54.215 Status: dzVents: Info: Handling events for: "Ping - Camera04", value: "Off ...

I have checked and double checked the script and it is just as you wrote it, the only change I have made is the idx. The camera has idx 370 and the plug has idx 369 scriptVar = 'cameraReset' return { on = { devices = { 370, }, customEvents = { scriptVar, } }, data = { cameraState = { history = true ...