openHAB 3.2 Milestone discussion

You already have installed openHAB, therefore just edit the file /etc/apt/sources.list.d/openhab.list and replace stable with testing.
After having done, just issue the following commands

sudo apt-get update
sudo apt-get upgrade

openHAB 3.2 Milestone 3 should now be installed.

Who knows ??? It should upgrade your system without any issue.

1 Like

Lovely, cheers, @hmerk . :+1:

Oh, and I wasn’t talking about all the other crap on the system, only openhab. But I guess I’ll find out, as I need that marketplace to run decent time of day stuffs.

Thanks again! :slightly_smiling_face:

I’ve moved the old openhab-2 one out … Is the openhab-linuxpkg.list needed? Or should I delete/backup that, too?

Looking at the installation docs, that is the one that’s mentioned. So maybe I should leave that there as stable … yeah … I’ll do that for now.


Just to be clear, that linked tutorial is for if you want to write rule templates. It does not help you write rules and it really just barely addresses installation and use of a template from the user’s perspective. Thankfully that part is pretty straight forward. Just install the template in Settings → Automation, add a rule and choose the template, then fill out the parameters.

Never mind, I thought that was a different tutorial linked to.

1 Like

Good morning.
Ist the Web Socket closed failure of the amazon echo binding fixed with Milestone 4. Cannot find it in the Release.

No, it is not. You still need the Smarthome/J version of the binding.

1 Like

Did the upgrade last night the result was:

Working directly after the upgrade.
Dropped a jar into the addons folder and then had every single thing from all bindings report that the handlers were missing, this was not caused by a bad jar.
Did a restart of just openHAB and all handlers were working again.

After running it for 12 hours I am happy all is working well.

1 Like

With M3 I had the smarthomej-transformation-basicprofiles installed. Obviously this has been removed from the marketplace.

As it hasn’t been found after the upgrade to M4, the first start was stuck until I made a restart of the openhab service. The next start was without that error. Nevertheless openHAB restarted several times automatically before it was running stable.

I would expect to get an error, not just an info and that the start is ongoing afterwards.

2021-11-08 18:16:15.566 [INFO ] [.jetty.server.handler.ContextHandler] - Started HttpServiceContext{httpContext=org.ops4j.pax.web.extender.whiteboard.internal.WebApplication$1@2514cd2b}
2021-11-08 18:16:15.711 [INFO ] [internal.service.FeaturesServiceImpl] -
2021-11-08 18:16:16.661 [INFO ] [internal.service.FeaturesServiceImpl] -   org.openhab.core.model.rule/3.2.0.M4
2021-11-08 18:16:16.738 [INFO ] [internal.service.FeaturesServiceImpl] -   org.openhab.core.model.script.ide/3.2.0.M4
2021-11-08 18:16:16.751 [INFO ] [internal.service.FeaturesServiceImpl] -   org.openhab.core.addon.marketplace.karaf/3.2.0.M4
2021-11-08 18:16:16.796 [INFO ] [community.CommunityKarafAddonHandler] - Reinstalling missing marketplace KAR: marketplace:127317
2021-11-08 18:16:16.923 [INFO ] [internal.service.FeaturesServiceImpl] - Adding features: smarthomej-transformation-basicprofiles/[3.2.6,3.2.6]
2021-11-08 18:39:17.003 [INFO ] [ache.karaf.main.ShutdownSocketThread] - Karaf shutdown socket: received shutdown command. Stopping framework...
2021-11-08 18:39:17.042 [INFO ] [org.openhab.ui.internal.UIService   ] - Stopped UI


I have been playing with openhabian OH 3.2 M4

The standard oh:icons are not appearing, user icons in \OPENHABIAN\openHAB-conf\icons\classic folder appear as do the f7:icons.
I set the icon in ui item metadata page.

Where do i find this Smarthome/J version?

1 Like

I don’t mean to ask for the background why all the Smarthome/J addons have been removed from the marketplace. Just one question from a users perspective: it’s anything wrong in using these addons?

Edit: I found some explanations in the HTTP Addon Thread. I think that will do for now. Sorry for asking here again…

I have trouble with my Nanoleafs. They lock, so that I cannot use the Nanoleaf app and any effect of the lights stops (changing colors). Some times it is possible for Openhab to change to another lightsetting, but not always, and it is is not possible for Openhab to turn the panels off

That is for sure not an issue with the nanoleaf binding. Since M4 it has become extremely stable. Can you please open a separate thread and explain in detail what you are experiencing?

Many thanks to @cweitkamp for this:
implicit variable


is now available!

1 Like

Running openHABian on RPi4, after upgrading to latest openHABian version / M5 (coming from M4), all my manual installed bundles remains in status resolved. Need to run bundle:start <bundleId> to get the bundles active, which works fine.

However, if I reboot, the bundles end up as resolved once again, and “manual” start of the bundles is required.

Anyone else?

After having the system settle for a day, I can now reboot, and all my bundles become active automatically, and within reasonable time.

3 posts were split to a new topic: Errors after upgrade to M5

Moderator’s request:
People please don’t post any type of issue here just because it happens to you on latest milestone.
This thread is when you have identified issues with the code of this milestone, i.e. they started to appear in this version and are not present in earlier ones.

For anything else such as identifying your problem in the first place, determining if it’s really an undesired software behavior and which software version it is with, please open your own thread(s).
Thank you.

1 Like

uh oh… we’re being bold again… :hushed:… tbh I’m a bit lost with the semantics of that argument Markus…the grand title wherein I (and others) posted does say ‘OH 3.2 discussion’.
Admittedly my issue first appeared going from 3.1.0.M4 to 3.1 stable (so I stayed on 3.1.0.M4) BUT it is still persisting (for me) in the 3.2 Milestones! I did ask about it under a 3.1 discussion back in July but got no answers really, so it seemed reasonable/ok/not off topic to raise it here in the hope of some enlightenment… :roll_eyes:

Markus is right here - this thread is specifically meant to report regressions that come up with milestone builds and is the corresponding discussion thread for the announcements in openHAB 3.2 Milestone Builds.
Keeping the scope to direct regressions over previous milestone builds helps the maintainers to ensure that nothing was accidentally broken, which is what we all want to avoid here.

Ok, I can see your point, hopefully someone will pick up on the moved post.

1 Like