openHAB 3.3 Release discussion

Can you show the query that is used by nodered?

Not sure what you mean by query @J-N-K , but in node red we have several nodes, and one of them listens for state changes as a way to initiate a flow, or rule, if you will.
When deploying / starting the nodes, they will “query” or “read” the states of the devices to which we set them up to.
So for example, if I have a rule that starts whenever the state of the kitchen light changes, and I deploy that, the current state of the light would be read, and updated whenever it changes.
Currently the problem is that it is being read only once. No further updates after that first one is received.
Yesterday the dev of the nodered-contribute-openhab3 node sent an update, but it didn’t fix the issue, at least in my case.

Further discussion here: Openhab 3.3.0 RC1 · Issue #38 · jeroenhendricksen/node-red-contrib-openhab3 · GitHub

I have no insight on nodered. I can only guess that it uses the REST API and SSE events. So I need to see the call to the REST API and also the m

Problems with Hue Things after change to 3.3 from 3.2 (openHABian)

Detailed 


Maybe you have the same issue, as I had with my ZWave Controller. I had to change 0 to false in the thing configuration (Code):

I would assume, that you have (at least) to change ledindication channel to false, as stated in the error message. Maybe you have to change other channels too


This helped for me

1 Like

Thx 
 unfortunately still un-initialized.
The Led-Indication is off (and was) 
 so I guess it is a wrong value in the device-database.

Can you send the Code of the Thing?

Maybe there are more channels to change?

MAybe you can have a look in openhab.log and paste output
(The timeslot when the thing goes tries to go online)

I double checked all my things manually, which took a lot of time. I found an issue within my Openweathermap things definition. I used “local” two time. Changing one to “local2” solved the issue.

image

So the error message “Last segment must not be blank” is misleading. Furthermore it would save so much time, if the error message would tell me the filename and line in which the error occurs or at least some other hints like binding name.

helped to fix this

Following issues occur.

2022-06-28 12:19:43.669 [INFO ] [af.deployer.kar.KarArtifactInstaller] - Found a .kar file to deploy.

2022-06-28 12:19:43.670 [INFO ] [af.deployer.kar.KarArtifactInstaller] - KAR openhab-addons-3.3.0.kar is already installed. Please uninstall it first.

Rules defined in .rules do not appear in the user interface and are not triggered / running. In the start log i can’t find errors expect those meassages at the end of the start up procedure (see above)
Any solution for that?

I was on M7 before so didn’t expect trouble, however, text to speech with googletts broke for me with the released version. Downgrading to M7 helped and things run again.

The relevant part of openhab.log in the released 3.3:


2022-06-28 16:51:22.923 [INFO ] [org.openhab.core.model.script.voices] - talkAction: say
2022-06-28 16:51:22.928 [INFO ] [org.openhab.core.model.script.voices] - Problem? <speak>es ist 16 Uhr 51   Wir haben Dienstag, den <say-as interpret-as="ordinal" format="dd" detail="1">28</say-as> Juni. Die Phase ist: afternoon </speak> - googletts:deDEWavenetC - chromecast:audio:murmel - 45
2022-06-28 16:51:22.930 [DEBUG] [.googletts.internal.GoogleTTSService] - Synthesize '<speak>es ist 16 Uhr 51   Wir haben Dienstag, den <say-as interpret-as="ordinal" format="dd" detail="1">28</say-as> Juni. Die Phase ist: afternoon </speak>' for voice 'googletts:deDEWavenetC' in format AudioFormat [codec=PCM_SIGNED, container=WAVE, bigEndian=true, bitDepth=16, bitRate=705600, frequency=44100channels=1]
2022-06-28 16:51:22.932 [DEBUG] [lient.internal.OAuthStoreHandlerImpl] - Decrypting token: AccessTokenResponse [accessToken=3mjMXWWljJ8/17J5S29VLjbZdWASp593cQi7/m4ZHb8238N23X5/anDnoUeWGWuyLukXnb4BBaZ0wLYe2+MDrMycksuNzdjykZIEmKeKndvsSUoSE0Mlx61XkTl4z1wl3dzVxYsqzOwFL28D3ZyN+HZdEeu0ot/foZY16ZzLkUWmWTivo9KUyw/FVv9r5P0HD7Ut5ZDO0Js5lfZzORxbdAroiBRLhU3LP5+4+PiWrbC3V6BZanXNXh46vHvMkxfqz9L8ryvWDMlwgLozXtOlYi8YLakV5Z638yntjODAUA86b5KEbE4Vnj+HzHEMuAiC5NCotNjeZjWomXfXJNK3dw==, tokenType=Bearer, expiresIn=3385, refreshToken=null, scope=https://www.googleapis.com/auth/cloud-platform, state=null, createdOn=2022-06-27T23:45:12.214905]
2022-06-28 16:51:23.135 [WARN ] [jsr223.jython                       ] - Traceback (most recent call last):
  File "/etc/openhab/automation/lib/python/core/log.py", line 96, in wrapper
    return function(*args, **kwargs)
  File "/etc/openhab/automation/lib/python/core/rules.py", line 108, in execute
    self.callback(inputs.get('event'))
  File "/etc/openhab/automation/jsr223/python/personal/945_voices.py", line 128, in voice_sayUtter
    Voice.say(utterance, defaults["voice_id"],defaults["sink"], PercentType(defaults["volume"]))
NullPointerException: java.lang.NullPointerException

and with the M7 after downgrade:


2022-06-28 17:53:53.022 [INFO ] [org.openhab.core.model.script.voices] - Problem? <speak>es ist 17 Uhr 53   Wir haben Dienstag, den <say-as interpret-as="ordinal" format="dd" detail="1">28</say-as> Juni. Die Phase ist: afternoon </speak> - googletts:deDEWavenetC - chromecast:audio:murmel - 45
2022-06-28 17:53:53.024 [DEBUG] [.googletts.internal.GoogleTTSService] - Synthesize '<speak>es ist 17 Uhr 53   Wir haben Dienstag, den <say-as interpret-as="ordinal" format="dd" detail="1">28</say-as> Juni. Die Phase ist: afternoon </speak>' for voice 'googletts:deDEWavenetC' in format AudioFormat [codec=PCM_SIGNED, container=WAVE, bigEndian=true, bitDepth=16, bitRate=705600, frequency=44100channels=1]
2022-06-28 17:53:53.035 [DEBUG] [lient.internal.OAuthStoreHandlerImpl] - Decrypting token: AccessTokenResponse [accessToken=LdEWmHAg7GjsYW8XBtoBIWPo7Y1oW3lX4tWVbxkZUw4yzxsrVPhAm2YJHEyB3vvO9mK3h6RJ26OCCfGz5lhZ6j4nmHIyiRkv/GNKdeK7yey85xsMRaPfK6Fd48a+5rQh17Iamybo1ZvC8Xlb5YAfCrmCN0Mx/Ziu1D7cMLKl8iKqvlXa5x3PL8TtQyrCILUWG/AebJ7WmWETjwDJ0Gt1+Zj73By8G4O6PEOHQ+hZfiMlA8l3CCayCNvABy0RqxQP, tokenType=Bearer, expiresIn=3461, refreshToken=null, scope=https://www.googleapis.com/auth/cloud-platform, state=null, createdOn=2022-06-28T17:53:33.196313]
2022-06-28 17:53:53.572 [DEBUG] [ce.googletts.internal.GoogleCloudAPI] - Caching audio file deDEWavenetC_6c50e71684e03e3e6ecca036eea87b9e.wav
2022-06-28 17:53:53.583 [DEBUG] [ce.googletts.internal.GoogleCloudAPI] - Caching text file deDEWavenetC_6c50e71684e03e3e6ecca036eea87b9e.txt
2022-06-28 17:53:54.101 [INFO ] [org.openhab.core.model.script.talk  ] - murmel status: Casting: Notification
2022-06-28 17:54:02.443 [INFO ] [org.openhab.core.model.script.talk  ] - murmel status: Default Media Receiver

(edith says: typos)

Hi, XXX is my bridge ID

UID: hue:0106:XXX:79
label: Hue ambient light sensor 1
thingTypeUID: hue:0106
configuration:
  tholddark: 3
  ledindication: 0
  tholdoffset: 100
  on: true
  sensorId: "79"
bridgeUID: hue:bridge:XXX

I disabled and enabled, so 


2022-06-28 20:33:54.705 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:XXX:79' changed from OFFLINE (CONFIGURATION_ERROR): Es wurde kein Sensor mit der angegebenen ID an der Hue Bridge gefunden. to UNINITIALIZED

2022-06-28 20:33:54.738 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:XXX:79' changed from UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): {ledindication=Der Datentyp des Wertes (class java.math.BigDecimal) stimmt nicht mit der Typen-Deklaration (BOOLEAN) in der Konfigurationsbeschreibung ĂŒberein.} to UNINITIALIZED (DISABLED)

2022-06-28 20:33:56.481 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:XXX:79' changed from UNINITIALIZED (DISABLED) to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): {ledindication=Der Datentyp des Wertes (class java.math.BigDecimal) stimmt nicht mit der Typen-Deklaration (BOOLEAN) in der Konfigurationsbeschreibung ĂŒberein.}

2022-06-28 20:33:58.618 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'hue:0106:XXX:79' changed from UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): {ledindication=Der Datentyp des Wertes (class java.math.BigDecimal) stimmt nicht mit der Typen-Deklaration (BOOLEAN) in der Konfigurationsbeschreibung ĂŒberein.} to UNINITIALIZED (HANDLER_MISSING_ERROR)

What is misleading here? the expected value is a boolean, so true/false not 0.

1 Like

set ledindication: false

and try please

1 Like

Wow, you 're right 
 i was not able to do so in the GUI but it can get fixed manually in the yaml! :grinning:
Irritating - but solved.
So the upgrade process isnt that easy.
Thx a lot

You can‘t set it in the UI? That sounds like a bug if a valid setting can‘t be used.

Hi!

I have a similar experience as @Mikel_2 with a couple of my ZWave bulbs. Config parameters are invalid as of 3.3 and can’t be changed from the UI:

This is an Aeotec ZWA001 Bulb 6 Multi-White:

Thing 'zwave:device:512:node34' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): {config_82_2=The value 6500.0 does not match allowed parameter options. Allowed options are: [ParameterOption [value="5000", label="Cold White (0x1388 (5000k) ~ 0x1964 (6500k))"]]}

This field is not editable in the UI.

This is a Hank HKZW-RGB01-V1.0:

Thing 'zwave:device:512:node24' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): {config_255_4=The value 1.0 does not match allowed parameter options. Allowed options are: [ParameterOption [value="1431655765", label="Resetting to the factory default"]]}

This field is editable in the UI as a button/bullet that can be selected but I don’t really fancy factory resetting the device. And I see no way to enter the mentioned value in there.

I had to downgrade back to 3.2.0 to get the things to work again. This downgrade then corrupted my Thing json db. At startup of 3.2.0 a large number of these where shown:

[ERROR] [re.storage.json.internal.JsonStorage] - Couldn't deserialize value 'org.openhab.core.storage.json.internal.StorageEntry@48e9e6a'. Root cause is: org.openhab.core.thing.internal.ThingStorageEntity cannot be found by org.openhab.core.thing_3.2.0

I had to restore this file from a backup to get all my things back and working again.

Both these devices (bulbs) need a slight DB change (most straightforward would be to add the missing option, but I think changing the “Limit to Options” flag to false will work as well) to pass the handler validation introduced between 3.2 and 3.3. Do you have DB access? The blog will provide the steps to attain that access.

Bob

1 Like

Have you guys checked the API explorer?? I don’t think it’s working


image

Starting to get a feeling that the Node Red issue might be related to this??

Isn’t it possible to consider a default header value if no value is provided?