openHAB 2.5.7 release discussion

same here. Never seen so many errors…
BUT, now did :
sudo systemctl stop openhab2.service
sudo apt update and sudo apt upgrade (this time 2 updates were available)
after this, a sudo reboot
result: No Errors :slight_smile:

Someone using Deconz binding? There should be an addition of a “last seen” channel?
I don’t find it. Or do I have to re-add all my Deconz items? (hope not)

1 Like

Delete the Things and then rediscover or manually readd them, in order to update the Thing definitions from the binding. This is true of all bindings.

When Thing features change, you generally have to delete old Thing and discover/create new to get the new definition. If you take care to give the new Thing the same name, all the old Items etc. stuff will link up.

thx!
it works :slight_smile:

After upgrading, I’m now getting the dreaded ‘An I/O error has occurred while writing a response message entity to the container output stream’ exception.

I get this message when I do a pull from the REST API for items:
http://hab:8080/rest/items (edit: corrected link)

Several clear caches, reboots, still getting it.

Breaks the Paper UI as well.

Any hints where to look? Seems like it doesn’t like a value in an item somewhere and throws this exception trying to render it to JSON.

After updating from 2.5.5 to 2.5.7 I get the following error related to “sendBroadcastNotification” action. This rule was working in all previous versions.

[ERROR] [ntime.internal.engine.ExecuteRuleJob] - Error during the execution of rule 'Trockner': The name 'sendBroadcastNotification' cannot be resolved to an item or type; line 176, column 4, length 100

that’s the line the error is referring too:

sendBroadcastNotification("Trockner - Knitterschutz beendet.\n Schalte Trockner in 10 Minuten aus.")

Any clue why this is happening?

thanks
Stefan

I saw something similar with ‘sendMail’.

It appears to be a temporary issue because later, sending email does work.

Can you verify that Broadcast notifications are working? If so, I think you can ignore it.

Narrowed it down to ecoBee sensor temperatures. If I remove those Item Links from org.eclipse.smarthome.core.thing.link.ItemChannelLink.json by hand, I can get items again.

Once I add a link to an ecoBee Sensor Temperature, I don’t get any Items from http://hab:8080/rest/items and the Paper UI breaks around items.

Still working through this, stay tuned.

1 Like

Deleted the Temperature Items and recreated them, that fixed everything.

Looked at the Item json file, no changes to Temperature Items other than the location in the file.

No idea what was going on but it’s fixed now. Whew.

what I wrote in my previous post:

The raspberrypi-kernel package was updated yesterday, resulting in the kernel version to jump from 4.9 to 5.4.

Following Telegram problem here:

2020-07-24 22:45:02.264 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule 'Telegram senden, wenn die Alarmanlage unscharf ist': An error occurred during the script execution: Could not invoke method: org.openhab.binding.telegram.bot.TelegramActions.sendTelegram(org.eclipse.smarthome.core.thing.binding.ThingActions,java.lang.String,java.lang.Object[]) on instance: null

Furthermore there is no access through openhab:8080 to the PaperUI, Basic UI, etc.
App is working wonderfully instead to 2.5.7 --> no eclipse error for the time being

I reboot the Raspberry Pi3 three times but no good result. The last shutdown with power off did it not too.

Related recent post -

I saw this after my post. Different to my problem is that I made an update to the newest version and had the error after a reboot. The TE had it after a shutdown. I am trying to delete the addons.cfg tomorrow and look what happen then.

A fresh install is a possibility too. Clicking the addons and copy the configuration files must be done in minutes…

Thank you for your help.

hm, you are way ahead then.
openhabian here, freshly updated and it identifies like:

uname -r
4.19.66-v7+

Delete, why would that make anything start working?
You could just look in it in the first place, and see what it looks like. There are examples in that thread of what to expect.

Don’t get addons.cfg muddled up with addons.config, the “cached” version.

I think the location of each entry in the json is random anyhow

1 Like

this is normal for me after every upgrade. just wait. it takes a looooong time (10min?) to load everything. and then do another restart. fixes all my problems

1 Like

This was indeed the solution to get my modbus binding working again.

But I also had the clean the cache in between.

Since the update of the deconz binding, the deconz things are updated cyclically every 5 minutes. This can also be seen in the log:

2020-07-26 14:53:51.283 [me.event.ThingUpdatedEvent] - Thing 'deconz:lightsensor:LightlinkPi:HueMotionLightLevel' has been updated.
2020-07-26 14:58:51.369 [me.event.ThingUpdatedEvent] - Thing 'deconz:lightsensor:LightlinkPi:HueMotionLightLevel' has been updated.
2020-07-26 15:03:51.458 [me.event.ThingUpdatedEvent] - Thing 'deconz:lightsensor:LightlinkPi:HueMotionLightLevel' has been updated.
2020-07-26 15:08:51.535 [me.event.ThingUpdatedEvent] - Thing 'deconz:lightsensor:LightlinkPi:HueMotionLightLevel' has been updated.
2020-07-26 15:13:51.598 [me.event.ThingUpdatedEvent] - Thing 'deconz:lightsensor:LightlinkPi:HueMotionLightLevel' has been updated.

I always thought the deconz binding was based on a websocket connection where no pollen is necessary?