@Thorgal789, You would need to publish your actual code for me to comment but from the looks of it you are writing a webserver and handling client connections. When a client connects the plugin's onConnect is called followed by the onMessage, if the plugin does not add a reference to the client ...

@Thorgal789, The extended framework is not a workaround but but a better implementation for certain types of plugins, specifically those where multiple 'device's (physical or virtual) that have more than one attribute that can be exposed to Domoticz. It is much easier to code the plugin for these ...

I suspect this is not solvable because it is an issue with the library and not Python (or the framework). There is no 'un-import' function in Python to force a complete cleanup, I believe Python holds libraries in an internal cache even if nothing is referencing them anymore. Importing them a second ...

I'm not aware of any issues with 3.10.

I've done some initial testing with 3.11 on Windows and it looks like that will be okay as well.

@JanJaap, Both frameworks work off the same Domoticz database tables so I assume by migrate to the extended framework you are talking about changing the DeviceID and Unit numbers of existing devices? You could do it in the plugin by connecting to the database yourself using the Python SQLite3 module ...

I use a plugin to control output GPIO pins and don't have an issue, you could try that if the built in functionality isn't working for you.

Its here: https://github.com/dnpwwo/Domoticz-GPIO-Plugin

Hi,

This seems to have been a Linux only issue, I've pushed a fix that should fix at least some of the issues (maybe all).

Thanks @heggink, given I already had a copy of your test plugin I was able to reproduce the crash.

I've had a look at the deConz plugin and it does use WebSockets so it could be impacted. If anyone has a test machine that can use this plugin it would be helpful to see the output from running with the plugin debug level set to include 'Messages'. There is also a WebSocket Client example plugin ...

Unlikely that the WebSocket fix impacted this because it was contained to that protocol but there was a more general change in the last week around returning data to plgins that may have an issue.

If you are impacted please post the domoticz_crash.log file (from you Domoticz folder) and I can look.

@JanJaap,

I have responded in the other thread, but for clarity: The dictionary containing a device's units is 'Units' not 'Unit'.

That is why Domoticz is correctly reporting:

@JanJaap,

You need to refer to 'Units', not 'Unit'.

@heggink,

Nothing, I reproduced your code and it didn't work for me either.

I've pushed a fix.

I've pushed a change to check (and log) for running threads during stop and wait for around 10 seconds to give them time to stop before continuing.

Sadly the 'threading' library doesn't have a 'kill' or 'stop' API so I can't do much about that.

The 2 stack dumps show that the 'zigpy-deconz' have 3 or 4 threads running during the plugin shutdown.

Python threads need to all be stopped before leaving onStop otherwise there will be a crash. The Python C API doesn't have a way of detecting or handling this (can I've seen).

@pipiche, Couple of things: I see you are using Python 3.10. I didn't know (for sure) that this worked so thanks for testing it :lol: Your Python threads look fine btw although its good to see that they are being dumped The actual crash of course, is caused by an incoming HTTP message: Error: > #8 ...

@ajarzyn,

You can change the Options just not the dictionary itself.

If you add, update or remove the Options dictionary entires then invoke Update() the Options for the Unit will be updated.

Yes, it should be in the next beta build.

Hi keros, You can't in the current Domoticz stable but I liked this idea so I just pushed an update into the beta channel that allows it: <plugin key="Timeout" name="Timeout Tester" author="Dnpwwo" version="2.2.7" externallink="https://www.google.com"> <description> <h2>Timeout Tester</h2><br ...

This: 2021-11-02 23:03:07.811 Error: (Homebridge Tuya Plug) Device creation failed, Domoticz settings prevent accepting new devices. is probably the issue. You have new device creation disabled in the 'Settings' tab so the plugin can't create new devices (and doesn't handle it very elegantly). If ...

You could try using the example HTTP Listener plugin that comes with Domoticz. Look under domoticz/plugins/examples for HTTP Listener.py. Create a new folder under plugins (name not important) copy HTTP Listener.py into it and rename it plugin.py. Restart Domoticz and add it as a piece of hardware ...