Okay, thanks for the hint. I am already using those HTTP cache items to reduce the polling. I have the slight feeling that not only the HTTP requests are responsible for the high CPU load but more or less the internal handling of the cached data OR applying the necessary transformations an the data to get the values for the items.
Currently I am using 3 Philips Hue Motion Sensors, 1 Philips Hue Dimmer Switch, and 2 or 3 other URLs to retrieve data from. My setup looks like proposed in this tutorial:
I am really looking forward to switch away from this setup and hope to see the Hue binding to support the sensor API in the near future.
