You can set the Parameter
8. Measured Temperature Offset:
I think to -1.5 or -2 (not sure negative is right or not )

Michael

Additional idea:

What happen if you in the morning set the Setpoint for two minutes to 24 degree - and then to 21 degree?
Is it the same delay?

I do not have any problems here with my 5 Spirit since a long time, but all of them have Version 0.15.
And I'm working only in Heat mode.

Michael

Just updated to 3.8799 - at Stretch with Python 3.5.3

Removed the running Python plugin - and created a new integrated Python event - have taken the sample event - not with "All" but in this time with "Device"

Changed a dummy device level - and got again this:
2018-01-06 16:37:40.461 EventSystem ...

@Dnpwwo:
In 3.8798 I have still same problem - not sure, your patch is inside?

Thanks!

Hi

inserted a debug line here: def onCommand(self, Unit, Command, ifValue, dDetails = None):
Domoticz.Debug("onCommand1 called for unit " + str(Unit) + ": Command: '" + str(Command) + "', ifValue: " + str(ifValue) + ", dDetails: " + str(dDetails))

Got this result:
2017-12-31 12:55:29.645 (eBus ...

Found an issue with Hc1SFMode.

Here will be added a Switch/selector with right pulldown options. eBus_plugin.JPG
But the values are wrong (by Domoticz design it is "level" 0...90) but should be:
"values": { "0": "none", "1": "party", "2": "onedaybankholiday", "3": "onedayholiday", "4": "holiday ...

Dnpwwo wrote: Friday 29 December 2017 9:00 @micha_pr ,

Can you post the event source that used and if you stored it in a file or the database.

I will try and reproduce it if you do.

I have used for testing the sample code (with setting "All") only-

Thanks!

At Setup - > Settings -> Other the EventSystem is enabled?

I have seen that any enabled Python Event (the integrated one in Event system with Lua, Blockly...) will cause this error.
Even if enable the sample code the signal 11 error will come up.

It's not easy to go back - because system hang very fast...
Enable sample event:
2017-12-27 16:21:38.559 ...

have tried your latest version "1.1.0" - but still the error.
2017-12-27 11:52:33.453 (eBus-t-all) Calling message handler 'onCommand'.
2017-12-27 11:52:33.454 Error: (eBus-t-all) 'onCommand' failed 'TypeError':'argument of type 'int' is not iterable'.
2017-12-27 11:52:33.454 Error: (eBus-t-all ...

Please check:
http://www.domoticz.com/wiki/Using_Python_plugins

# install dependencies
sudo apt-get install -y python3
# Domoticz Beta versions since V3.6129 also require...
sudo apt-get install -y python3-dev
# credit [https://www.domoticz.com/forum/viewtopic.php?f=65&t=16116&p=119747]

# update ...

hi,

you have changed the onCommand procedure?

I get now errors:
2017-12-25 16:56:22.594 (eBus-t-all) Calling message handler 'onCommand'.
2017-12-25 16:56:22.594 Error: (eBus-t-all) 'onCommand' failed 'TypeError':'argument of type 'int' is not iterable'.
2017-12-25 16:56:22.595 Error: (eBus-t-all ...

Not sure why,... but I made a second installation now with Stretch and new Python version - now all is stable since more than two hours.
It was not possible before.
At other installation nothing else was installed - it was also a minimal system with Z-Wave-stick only for plugin testing, but Jessie ...

Yes, I tried with refresh rate 300 - this is not the problem, because the Pi is in a loop between the calls.
Also the error come up after / while first call.
even tried with/without debug/cache...

But I made today a second image with Stretch and new Python version - now all is stable since more ...

ok, ... in the meantime I have seen that the error also depends on the number of elements (registers).
I have tred up to 5 registers - more or less stable.
With 15 registers - it will crash very fast.

Can you try to include most of your sensors from your JSON file?

Thanks!

interesting... maybe this could solve it? But you are om Pi with Jessie?

my: "PluginSystem: Started, Python version '3.4.2'."

2017-12-24 10:03:06.094 Error: Domoticz received fatal signal 11 !...
2017-12-24 10:03:06.094 Error: Domoticz received fatal signal 11 while backtracing !...
2017-12-24 10:03:06.099 Error: /home/pi/domoticz/domoticz() [0x236be4]
2017-12-24 10:03:06.099 Error: /home/pi/domoticz/domoticz(_Z14signal ...

Hi,

I was going back to stable version, because of problems with plugin in latest Beta (3.8795).
Original errors came from 3.8794. See also here:
https://github.com/domoticz/domoticz/issues/1891

But release version didn't help. I will update to latest version again and tell you.

Next beta will have a fix for this: Error: (ebus test3) Plugin did not stop after 5 seconds, waiting. and should not segfault on plugin stop or restart.

Hi,
this will not fix the other issue. the "not stop after 5 seconds" was caused by the wrong telnet port, as described above ;)

After ...

@micha_pr,

You are getting an error returned, not a crash. If you post some of your code I can have a look to see if the Send function can be improved.

No, it is an additional part of the crash. Maybe not everytime it will appear in the log,
Please look here, there is the plugin and more info ...