# Reducing Item updates (and thus log entries) caused by a Modbus TCP energy meter

**URL:** <https://community.openhab.org/t/reducing-item-updates-and-thus-log-entries-caused-by-a-modbus-tcp-energy-meter/146516>\
**Category:** Items & Sitemaps\
**Tags:** items\
**Created:** [May 6, 2023, 7:33am UTC](https://community.openhab.org/t/reducing-item-updates-and-thus-log-entries-caused-by-a-modbus-tcp-energy-meter/146516 "2023-05-06T07:33:33Z")\
**Posts on this page:** 2\
**Page:** 3

<div class="post-metadata">

**Author:** ![marco\_hoefle](https://community.openhab.org/user_avatar/community.openhab.org/marco_hoefle/32/79454_2.png) [@marco\_hoefle](https://community.openhab.org/u/marco_hoefle)\
**Post date:** [December 29, 2023, 7:36am UTC](https://community.openhab.org/t/reducing-item-updates-and-thus-log-entries-caused-by-a-modbus-tcp-energy-meter/146516/41 "2023-12-29T07:36:28Z")

</div>

Version 4.1.0  
It is only a startup warning, the throttling seems to work now. When changing the .rb file I do see the reload message in the log:

```yaml
08:33:58.264 [INFO] [port.loader.AbstractScriptFileWatcher] - (Re-)Loading script '/openhab/conf/automation/ruby/throttle_updates_profile.rb'

```

The message after starting OH4.1:

```yaml
08:32:44.831 [WARN] [e.thing.internal.CommunicationManager] - No ProfileFactory found which supports profile 'ruby:throttle_updates' for link 'Lueftung_Airflow -> knx:device:bridge:lueftung_fast_poll:Lueftung_Airflow

```

---

<div class="post-metadata">

**Author:** ![jimtng](https://community.openhab.org/user_avatar/community.openhab.org/jimtng/32/98543_2.png) [@jimtng](https://community.openhab.org/u/jimtng)\
**Post date:** [December 29, 2023, 7:57am UTC](https://community.openhab.org/t/reducing-item-updates-and-thus-log-entries-caused-by-a-modbus-tcp-energy-meter/146516/42 "2023-12-29T07:57:25Z")

</div>

> [@marco\_hoefle](#):
>
> It is only a startup warning, the throttling seems to work now. When changing the .rb file I do see the reload message in the log:

That’s because the item loaded before the script / profile was loaded. You could try loading the script at a lower startlevel, by placing it inside:  
`conf/automation/ruby/sl30/`

It may still not be early enough, because items would still be loaded first, but at least it will load before any other automation scripts you may have.

[Previous page](https://community.openhab.org/t/reducing-item-updates-and-thus-log-entries-caused-by-a-modbus-tcp-energy-meter/146516.md?page=2)