Openhab2.5 and ... Alexa-Google-Apple

Apps & Services myopenHAB
21

I found this two items
“Termostato -\u003e mqtt:topic:94757268:Termostato”: {
“class”: “org.eclipse.smarthome.core.thing.link.ItemChannelLink”,
“value”: {
“channelUID”: {
“segments”: [
“mqtt”,
“topic”,
“94757268”,
“Termostato”
“configuration”: {
“properties”: {
“profile”: “system:default”
“itemName”: “Termostato”
“Termostato -\u003e mqtt:topic:3248c919:Termostato”: {
“class”: “org.eclipse.smarthome.core.thing.link.ItemChannelLink”,
“value”: {
“channelUID”: {
“segments”: [
“mqtt”,
“topic”,
“3248c919”,
“Termostato”
“configuration”: {
“properties”: {
“profile”: “system:default”
“itemName”: “Termostato”

But I only have
Termostato
mqtt:topic:3248c919:Termostato
Switch
I think I can delete the other one.

Right?

Jad

22

Ok, no more broker hanging in the inbox, but still no humidity in Google Assistant.
And this worning:
Unrecognized heating cooling target mode: heat. Expected CoolOn, HeatOn, Auto, or Off strings in value.

Any other idea?

Tnx

Jad

23

:+1:

Guessing it expects to have this as a string not number.

You can try a rule to post the value as a string.

rule "Test String"
when
    Item YourHumidityItem changed
then
    YourHumidityItem.postUpdate(YourHumidityItem.state.toString)
end

If that fails then try using a proxy item for the humidity reading so the rule would change to use (ProxyItem.state.toString) in place of (YourHumidityItem.state.toString)

See more about item conversion here:

24

This for fix the problem in google with Umidity?
Or to fix the problem of the cooling target mode?
anyway I tried the rule, but … no change.
If I put the “String” value directly in the items file? like:
String Humidity items …

Jad