just posting my āupdate-experienceā to v2.3.
Using a Raspi (2 Model B rev 1.1) with openhabian and not knowing there was an openhabian update,
I executed an āsudo apt-get update & upgradeā yesterday with a succeding āsudo rebootā.
In the process I kept my old config files, when asked if I wanted to replace them with the āupdatedā ones.
Afterwards openhab2 was runnning, but PaperUI, Android and iOS App would show nothing. The log viewer stopped with the timestamp of the update and would not show anything ānewā. Neither did the log files accessed through ssh on the Raspi.
Reading about the new release and this thread helped me out.
First i tried the āopenhabian-configā update and repeated the ārelease updateā, this did not help.
Then I looked for āwifiledā - not installed in the first time.
And finally the problem solver for me:
tlc posted:
After it I could reach PaperUI, etc. again.
I noticed that my FritzDect 200 (switchable wall socket with temperature and usage) has problems with the new āunitā conversion. PaperUI screenshot below.
Entry in the logs:
2018-05-31 09:20:17.151 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value ā27.5ā of item FD_temp with format ā%.1f %unit%ā: Conversion = āuā
default.item:
Number FD_temp āFritzDect200_Tempā (gFD, gSmartPlug_others) { channel=āavmfritz:FRITZ_DECT_200:192___*:087610369753:temperatureā }
Is there anything I can do to correct this or is this a āBindingā problem.
I did run into it in a snapshot earlier this year. It was a unintended feature at first, so the transformation was just aligned with the documentation.
Ok, so here is my expereince on this update.
I updated through apt-get upgrade, and all went well until I got the webpage saying that it was installing the UI, and that it would take a few minutes.
5 hours later I still get the same message, so I rebooted, but I would still get the same message.
After searching a bit I found that I needed to run the following:
This changed everything; now I get absolutely nothing. No web interface, no Karaf, nothing.
The service is running but it shows nothing in terms of webpages, and the logs are empty with nothing happening in there.
What should I do? Backup my configuration, remove the broken installation, and re-install? or is there a way to get the openHAB heart to beat again?
now it is all back to how it was before the world started to crumble.
I will next try again the upgrade assuming that something might have gone wrong the first time.
Worst of cases I will revert and hope for a patch (assuming there is a bug).
Good news, It now works with the latest release, however when I run āopenhab-cli showlogsā I have just empty logs, which is strange,as I would at least expect the note of the service starting, and a connection error, which I expect because the corresponding device i currently turned off.
I saw some commits regarding MQTT (internal broker?) but nothing is mentioned in the change log / blog. Is there something new already in which is usable?
Check the permissions on /var/log/openhab2 and make sure the openhab user has permission to read/write to it. I ran into something like that at some point but wasnāt sure the cause and havenāt had a chance to look into it any further.
I ended up just deleting the byte logs and restarted openHAB, and that fixed it.
Now I have tons of errors to look and figure out what is going wrong with the rules, GPIO and serials.
The MQTT part works fine though.
thanks for your help.
It did solve half of the problem, the other half was solved by removing the Fritzdect from āThingsā in the PaperUI and then adding it again.
For some reason, a rule does not work as expected anymore. Until OH 2.2 / KNX 1 it worked as intended, since OH 2.3 / KNX 2. the rules fire EVERY TIME the respective cron jobs fire. They ignore the check for the current position of the rollershutters, which worked flawlessly before. So every 15 minutes I am receiving the info that āBeschattungā is onā¦
When trying to write the position of the rollershutter to the log, it reports a correct 85%.
Any ideas would be welcome
// Beschattung OST
rule "Shutter EAST set to ON to 85% when Outside Temp above 23 Grad and Shutter Auto set to ON"
when
Time cron "0 0/15 6-12 * * ?"
then
if (RL_Kueche_Ost.state != 85 && (Temperature_Aussen_Sued.state as DecimalType).floatValue >= 23 && (Beschattung_Automatik.state == ON)) {
Beschattung_Ost.postUpdate (ON)
sendTelegram("bot1","Beschattung OST am "+ Date.state.format("%1$td.%1$tm.%1$tY") +" um " + Date.state.format("%1$tH:%1$tM") + " aktiviert")
}
end
// Beschattung SUED
rule "Shutter SOUTH set to ON to 85% when Outside Temp above 23 Grad and Shutter Auto set to ON"
when
Time cron "0 0/15 10-17 * * ?"
then
if (RL_WoZi_Sued.state != 85 && (Temperature_Aussen_Sued.state as DecimalType).floatValue >= 23 && (Beschattung_Automatik.state == ON)) {
Beschattung_Sued.postUpdate (ON)
sendTelegram("bot1","Beschattung SĆD am "+ Date.state.format("%1$td.%1$tm.%1$tY") +" um " + Date.state.format("%1$tH:%1$tM") + " aktiviert")
}
end
// Beschattung West
rule "Shutter WEST to 85% when Outside Temp above 23 Grad and Shutter Auto set to ON"
when
Time cron "0 0/15 14-18 * * ?"
then
if (RL_Zimmer_West_West.state != 85 && (Temperature_Aussen_Sued.state as DecimalType).floatValue >= 23 && (Beschattung_Automatik.state == ON)) {
Beschattung_West.postUpdate (ON)
sendTelegram("bot1","Beschattung WEST am "+ Date.state.format("%1$td.%1$tm.%1$tY") +" um " + Date.state.format("%1$tH:%1$tM") + " aktiviert")
}
end
First of all, Iād like to thank you maintainers once more for all the work and effort and work which went into 2.3.
After reading some issues people seem to have after the upgrade, Iād like to quickly share that the upgrade process (Openhabian-Config) went extreemly smoothly for me.
I didnāt have to change anything in my Item configurations (i.e. Number:Temperature) and rules, etc are working like before.
Updated openhabian from 2.2 to 2.3 - all UIs are gone. Adding them in addons.cfg didnāt help.
Any ideas? Any way to install at least the paperui via console?