I assumed that at least running another server uses more RAM - but I did not research this in detail, I am just getting started with OpenHab.
However, configuring the light bulbs now nearly works for me.
Concerning the tasmota usage with HTTP, this is my nearly complete configuration for the things:
UID: http:url:86e189c392
label: Lampe .30
thingTypeUID: http:url
configuration:
authMode: BASIC
ignoreSSLErrors: false
baseURL: http://192.168.178.30/
delay: 0
stateMethod: GET
refresh: 2
commandMethod: GET
timeout: 3000
bufferSize: 2048
location: Wohnzimmer
channels:
- id: OnOffSwitch30
channelTypeUID: http:switch
label: OnOffSwitch30
description: null
configuration:
onValue: ON
stateExtension: cm?cmnd=Power
offValue: OFF
commandExtension: cm?cmnd=Power %2$s
stateTransformation: JSONPATH:$.POWER
- id: Dimmer30
channelTypeUID: http:dimmer
label: Dimmer30
description: ""
configuration:
onValue: "100.0"
offValue: "0.0"
stateExtension: cm?cmnd=Dimmer
commandExtension: cm?cmnd=Dimmer %2$s
stateTransformation: JSONPATH:$.Dimmer
- id: Color30
channelTypeUID: http:color
label: Color30
description: ""
configuration:
colorMode: HSB
stateExtension: cm?cmnd=HSBColor
commandExtension: cm?cmnd=HSBColor %2$s
stateTransformation: JSONPATH:$.HSBColor
- id: Lichttemperatur30
channelTypeUID: http:number
label: Lichttemperatur30
description: ""
configuration:
stateExtension: cm?cmnd=CT
stateTransformation: JSONPATH:$.CT
commandExtension: cm?cmnd=CT %2$s
(which is copied 4 times, for light bulbs under the adresses .30, .31, .32 and .33) and linked to items for on/off, brightness, color and temperature, and the ui:
config:
label: Overview
layoutType: responsive
blocks:
- component: oh-block
config: {}
slots:
default:
- component: oh-grid-cells
config: {}
slots:
default:
- component: oh-toggle-card
config:
title: Wohnzimmerlampe an/aus
item: Wohnzimmerlampe
- component: oh-cell
config:
action: analyzer
actionAnalyzerItems:
- Wohnzimmerlampe
actionAnalyzerCoordSystem: time
trendItem: Wohnzimmerlampe
header: Lampe-Analyse
title: Lampe-Analyse
- component: oh-slider-item
config:
title: Dimmer Lampe1
item: WohnzimmerlampeHelligkeit
min: 0
max: 100
step: 1
- component: oh-colorpicker-card
config:
title: Farbe
item: WohnzimmerlampeFarbe
modules:
- wheel
- component: oh-slider-item
config:
title: Temperatur Lampe 1
item: Lichttemperatur
min: 153
max: 500
step: 1
masonry: []
grid: null
Setting on/off, changing brightness and color works nicely for all light bulbs. Unfortunately, setting the light temperature does not work as expected.
While setting the color temperature via for i in 30 31 32 33; do curl 192.168.178.$i/cm?cmnd=CT%20300; done
works nicely, changing the slider results in the slider just jumping back to the original value.
events.log
contains
2021-12-09 22:53:08.066 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'Lichttemperatur' received command 386
2021-12-09 22:53:08.067 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Lichttemperatur' predicted to become 386
2021-12-09 22:53:08.072 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Lichttemperatur' changed from 300 to 386
2021-12-09 22:53:09.069 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Lichttemperatur' changed from 386 to 300
which indicates to me that it first changes to 386 and then changes to 300 back again.
Do you see any configuration which could lead to this problem?
EDIT I just wrote commandTransformation
instead commandExtension
. I fixed this and now it works fine. The above example can be used for HTTP tasmota configuration.