eBUS Binding 3.x [3.4.0;3.9.9)

csowada · March 5, 2020, 5:47pm

Could you provide a raw telegram that you want to decode? I can check it against the latest version.

witek_1308 · March 6, 2020, 6:57am

@csowada,
based on the return temp configuration:
[…]

 {"type": "static", "default": "0D 98 00"}

[…]
should I understand these are telegrams I need?

cat /var/log/openhab2/openhab.log | grep '0D 98 00'
2020-03-06 07:52:01.982 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Send: FF 08 B5 09 03 0D 98 00 B7 @ 0. attempt
2020-03-06 07:52:02.126 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Succesful send: FF 08 B5 09 03 0D 98 00 B7 00 05 EB 01 14 FE 00 8D 00
2020-03-06 07:53:01.931 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Send: FF 08 B5 09 03 0D 98 00 B7 @ 0. attempt
2020-03-06 07:53:02.075 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Succesful send: FF 08 B5 09 03 0D 98 00 B7 00 05 E9 01 16 FE 00 24 00
2020-03-06 07:54:02.110 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Send: FF 08 B5 09 03 0D 98 00 B7 @ 0. attempt
2020-03-06 07:54:02.245 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Succesful send: FF 08 B5 09 03 0D 98 00 B7 00 05 E9 01 16 FE 00 24 00
2020-03-06 07:55:01.941 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Send: FF 08 B5 09 03 0D 98 00 B7 @ 0. attempt
2020-03-06 07:55:02.085 [DEBUG] [dev.ebus.core.EBusLowLevelController] - Succesful send: FF 08 B5 09 03 0D 98 00 B7 00 05 E7 01 18 FE 00 4D 00

btw I observed some other problem too:

cat /var/log/openhab2/openhab.log | grep pump
2020-03-06 07:51:26.334 [DEBUG] [.csdev.ebus.command.EBusCommandUtils] - Value state_pump with 94 is larger then allowed 1
2020-03-06 07:52:26.347 [DEBUG] [.csdev.ebus.command.EBusCommandUtils] - Value state_pump with 94 is larger then allowed 1

Roland62 · March 9, 2020, 8:16am

I have activated this parameter also on my system. And yes, there are comming 5 bytes (not 3). Telegram:
2020-03-09 09:05:04;“FF”;“08”;“B5 09”;“03 0D 98 00 B7 00 05 17 03 E8 FC 00 B2 00”;

But I have not activated this on my system. Think equal is on your system?: I have a VRC700 implemented. Here some telegrams are in general active between VRC700 and BAI00. I try to have as less poll sequences as possible on my system to reduce the traffic on the ebus.
Here with the telegram ‘boiler.control.getopdata’ the return temerature can be read along without dedicated separate poll.
Maybe those idea is working also on your system?

witek_1308 · March 9, 2020, 9:30am

@Roland62 it is a great hint! for some reason I wasn’t using it before (don’t know why, maybe when I started using eBus binding 2y ago it wasn’t there?), anyways it does what I need, thanks!
I’m not sure whether it optimizes traffic on ebus or not as eventually this needs to be queried (either as separate thing or as main thing) but if it does, then it’s even better

Trainer · March 11, 2020, 4:40pm

@csowada can you please check vaillant_template.json and 39200.15.392_configuration.json

i got

ERROR: 500 - Internal Server Error

with the last update

csowada · March 12, 2020, 6:54am

Hello @Trainer,

I’m busy at least the next two weeks. Could you please create a GitHub issue?

Trainer · March 14, 2020, 6:24pm

thank you.
i can wait.

Here you can find my bug

modenet · March 14, 2020, 6:51pm

can someone explain me how to update definitions of ebus_configuration objects?
my BAI00 is full of NaN

Roland62 · March 15, 2020, 11:39am

Hi @modenet I think the simplest way is to delete BAI00 in paperui->Configuration->Things, Restart openhab and let find BAI00 as new device. What you have to do afterwards is to activate poll (if you had before).

modenet · March 15, 2020, 4:02pm

I deleted the BAI00, restarted the service and automatically a new item BAI00 was added.
nothing is changed.
what did it mean “activate poll”?

Roland62 · March 18, 2020, 6:41pm

Hi @modenet with active poll I mean if you had activated polling on a channel of BAI00. Those information will not be overtaken.

My tip was, that a change of a json config (e.g. after an update) not completely will be overtaken. After this step this cant be ‘your’ issue.
Could you give an example (the channel), where you get an NaN? And is this happend in paperui->control, also in sitemap ?

Trainer · April 19, 2020, 1:11pm

Trainer:

vaillant_template.json and 39200.15.392_configuration.json

thank you.
i can wait.

Here you can find my bug

hey @csowada, do you got some time to take a look over the *.json files?
hope you are well

Trainer · April 26, 2020, 11:51am

if someone has the same problem with the Espadapter v2.2 as i have, please check, if you use the right colour of a low current LED.

witek_1308 · April 30, 2020, 12:57pm

I have problem with binding stability after upgrading OH to 2.5.3 and now to 2.5.4. I don’t know whom to blame, not sure how to check it best. Symptoms are the following:

binding simply stops working after couple of days whereas before was rock-solid and months without restart was normal
log entries start to show: Send queue is full! The eBUS service will reset the queue to ensure proper operation.
interestingly everything else works normally (mqtt, rules etc). I don’t know for how long this would work as I’m restarting OH as soon as I detect eBus issues. Simply eBus is the simply the first to die.

Now - I’m far from saying it is a binding problem, maybe OH2 and new releases but definitely new release of OH + the current binding don’t like each other. How can I debug it further?

Edit
It seems something is leaking tasks in my OH, don’t know what but I guess this is the issue. Need to identify which binding/add-on it is

Roland62 · May 1, 2020, 9:20pm

I had the issue also months ago. Had toggeld the bridge configuration between jSerialComm and nrjavaserial. So far I remember sometimes the first, than the other was running for a longer time. Now I have jSerialComm and it is running without issues.
A little bit I have the impression it is not so important what is set - instead of thas the change of the setting seems to change somewhat more. But poor guessing from my side. Maybe it will help you, too…
Roland

witek_1308 · May 1, 2020, 10:04pm

@Roland62 thanks for the hint, let me try and report results after some time

witek_1308 · May 1, 2020, 10:31pm

No change. Threads are growing the same quick.
Btw - there is a 3rd option in drivers in my case - apart from the 2 which @Roland62 listed there is one for /dev/tty/USB0 too (which i am using). By default it chose nrjavaserial after binding upgrade so I didn’t touch it but maybe I should change to the usb one? What’s the difference?

csowada · May 2, 2020, 7:43am

I run the binding with openHAB 2.5.3 without any issue. But I restart the server every week.
Last week I’ve replaced the active USB hub the third time because I was not stable after attaching a zigbee stick weeks ago. This caused strange issues on all USB devices incl. my eBUS adapter.

witek_1308 · May 2, 2020, 9:41am

it seems I identified leaking binding (which I’m almost 100% sure was causing problems with eBus indirectly i.e. leaking tasks in OH and therefore problems with eBus).

witek_1308 · May 2, 2020, 5:24pm

I’m still investigating leaking events and I as mentioned above I think I identified the leaking binding. Definitely it isn’t as before, number of threads isn’t growing fast but what worries me is huge amount of threads from ebus in Blocked state. They started growing during the day, not immediately after restart.

openhab> shell:threads | grep 'BLOCKED' | wc -l
101
openhab> shell:threads | grep 'BLOCKED'
"pool-332-thread-1" Id=4766 in BLOCKED on lock=org.openhab.binding.samsungtv.internal.handler.SamsungTvHandler@e81770
"pool-333-thread-1" Id=4767 in BLOCKED on lock=org.openhab.binding.samsungtv.internal.handler.SamsungTvHandler@e81770
"upnp-main-326" Id=5215 in BLOCKED on lock=java.lang.Object@17e15c7
"OH-discovery-217" Id=5316 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-82" Id=5406 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-83" Id=5471 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-84" Id=5485 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-85" Id=5486 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"OH-discovery-225" Id=5534 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"OH-discovery-226" Id=5535 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"OH-discovery-228" Id=5593 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-88" Id=5617 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-89" Id=5626 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"OH-discovery-230" Id=5811 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-91" Id=5850 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-93" Id=5918 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-94" Id=5993 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-96" Id=6133 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-97" Id=6134 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-99" Id=6208 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-100" Id=6301 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-102" Id=6411 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-105" Id=6488 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-107" Id=6629 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-110" Id=6729 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-111" Id=6827 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-112" Id=6930 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-113" Id=6959 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-115" Id=7014 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-116" Id=7084 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-118" Id=7131 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-120" Id=7205 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-122" Id=7209 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-123" Id=7362 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-125" Id=7469 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-126" Id=7483 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-127" Id=7538 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-128" Id=7643 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-131" Id=7730 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-134" Id=7888 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-137" Id=8022 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-138" Id=8093 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-139" Id=8138 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-142" Id=8292 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-143" Id=8343 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-145" Id=8420 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-147" Id=8532 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-148" Id=8614 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-150" Id=8769 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-151" Id=8822 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-152" Id=8863 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-158" Id=9165 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-159" Id=9200 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-160" Id=9206 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-162" Id=9309 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-166" Id=9466 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-167" Id=9538 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-171" Id=9654 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-172" Id=9720 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-173" Id=9725 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-174" Id=9728 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-175" Id=9828 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-177" Id=9892 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-179" Id=10016 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-184" Id=10230 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-185" Id=10310 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-186" Id=10340 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-188" Id=10465 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-189" Id=10468 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-190" Id=10598 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-192" Id=10707 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-194" Id=10759 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-195" Id=10833 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-198" Id=11007 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-199" Id=11082 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-201" Id=11122 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-202" Id=11143 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-204" Id=11238 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-206" Id=11315 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-208" Id=11398 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-209" Id=11415 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-210" Id=11533 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-211" Id=11539 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-213" Id=11645 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-219" Id=12020 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-220" Id=12105 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-221" Id=12144 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-226" Id=12301 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-230" Id=12440 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-231" Id=12504 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"upnp-main-857" Id=12590 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-234" Id=12614 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-235" Id=12693 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-237" Id=12795 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-242" Id=12963 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-244" Id=13054 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-245" Id=13101 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-246" Id=13131 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-247" Id=13177 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"ebus-receiver-249" Id=13339 in BLOCKED on lock=org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl@125f710
"pipe-grep 'BLOCKED'" Id=13538 in RUNNABLE

majority come from ebus. @csowada, do you have any idea what can be causing it? I’m thinking whether it has anything to do with my config/OS setup?
If they don’t get cleared, this will fill out all my Max Tasks set to 4400 within a week or two. Increasing tasks obviously is possible but it’s not the point, leak is the problem.