29 posts were split to a new topic: UoM default units and consequences
A post was merged into an existing topic: openHAB 4.0 SNAPSHOT discussion
just a few posts up. its because of - Java 17 needed. i upgraded to 17 and it started working but i think some bindings broke for me. so i reverted back to stable 3.4
I need a little more help. I can’t figure it out. Do I need to go to each “Hue Item” I created and do this. Also, where on the Item screen do I enter this.
Folks, let’s hold off on the 4.0 snapshot issues until we can get a thread started for that. I don’t want to pollute this thread with issues unrealated to 3.4.
A new thread has been opened. Please report 4.0 snapshot problems here: openHAB 4.0 SNAPSHOT discussion
@BiloxiGeek, I’ll move your post over to there.
I had to look twice into the config, but just “2” steps for migrating to https:
- Make sure the bridge is set to https
- Make sure port is changed from 80 to 443
Somehow since the 3.4.0 update my Hue binding has significant delay. Does anyone else face this issue?
I get the following error after upgrading to 3.4: “ImportError: cannot import name Transformation”, triggered by the following import in my jython scripts:
from core.actions import Transformation
What do I need to change to make it work again?
@sucre I have the same issue. I don’t know what it is yet.
EDIT: It is a known issue, and here is the solution:
Thx a lot, that worked!
i updated to 3.4 and now i cant access:
if i click on them nothing happend.
has anybody else the same problem?
it only works if i type the ipadress:port/setting in my browser.
in Openhab app they are also not accessable
No, I just checked. I can click on them all and it works. What browser are you using, has your startup finished, have you restarted your browser?
tryed a few times.
after i accesed the setting by ip:port/settings
so for now problem is solved, but its strange
same procedure as every half year, here’s my moderator’s request:
Please only post to this thread on issues specific to 3.4 code, i.e. issues that were introduced with 3.4 and didn’t exist before, that you can reproduce and confirm to be general issues with the code and not your installation.
Help us keep communication clean and effective. So for anything else, please open your own thread.
10 posts were split to a new topic: Setpoints and Drayton binding in 3.4
I upgraded to OH 3.4.0 this morning and had several messages indicating issues with shelly username/password. After 3 or 4 reboots those messages dissapeared though.
All 30+ shellies working fine now on OH 3.4.0…
If this happens you can try Ctrl+F5 (command+R on Mac) or other techniques to Wikipedia:Bypass your cache - Wikipedia.
Or, on Chrome-based browsers, open the developer tools (usually F12), click Application, check all the boxes and then Clear site data. You will be signed out.
Normally you wouldn’t have to do all this but there were some more caching lately introduced so you can try starting with a clean state.
There’s a potentially breaking change on UoM (units of measurement), 3.4 introduced default units for all UoM item types now.
It’s a complex, multi-layer implementation and discussion, I moved it here:
let my openHABian update from 3.3 to 3.4 packages, I stopped all services, cleaned cache etc. in prior.
Seems everything is working, on short term, but those messages spams after update my log files:
... 2022-12-21 19:51:50.188 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ShellyRelayHandler tried updating the thing status although the handler was already disposed. 2022-12-21 19:51:50.191 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ShellyRelayHandler tried updating the thing status although the handler was already disposed. ...
It’s barely possible to read logs on WebIF (PaperUI) … all Shelly devices can be controlled properly incl. Shelly Manager App. Message is a warning, so most probably nothing critical.
Any ideas how to fix or get rid of that messages spam?