openHAB 3.0 Milestone 1 discussion

Please enter an issue for openhab-core for that. There should ne no restriction for filenames.

I have a handful (3 maybe) of 2.x JARs that I use in place of what comes stock with OH. Mostly bindings that aren’t committed into code yet. Is there any expectation in either direction of them working on 3.0? I realize that the goal would be for the developer to move to 3.x but some haven’t been and I don’t want to lose that functionality in the interim.

If you have the source I believe there is a migration script that can help port it to OH3, You would then need to repackage it though.

Unfortunately I don’t. These are jars that the developers have posted on the threads here (for example the MyQ binding Chamberlain MyQ Binding).

No jython?
Seriously?

1 Like

See How to Setup Jython for Jython support.

Python 2 end of life is 01/01/2021.
The last version of jython is from 23/11/2017.
Jython 3 seems non existent.
So I think a choice as been made on openhab.

Maybe we can use https://github.com/bcdev/jpy i dunno

i think the current problem is not the eol of Python 2. Other options are to move to GraalVM.

I use Graal together with zulu 11 to check if there are differences, but up to now i see no difference.

Grall will/is support Python 3

1 Like

@Spaceman_Spiff’s HABApp is Python 3 but broken because of the REST API authentication.

Should not be broken anymore, since Basic Auth is not offered with https://github.com/openhab/openhab-core/pull/1713.

After the next snapshot is released.

I’ve been playing with home assistant lately. It’s all integrated. I didn’t even need to ssh top install thee deconz binding and i even can do they config from within home assistant and look at the zigbee map from within home assistant. I can even do ssh or edit files from within home assistant. I never have to leave home assistant. Documentation is a lot better. You feel it’s made for users
Than, looking at openhab, even number 3, it all looks datet. And the thing i liked the most of OH,jython… Well, thee answer is: here is the URL, and figure out out yourself. While, some time ago, oh3 would have the NRGE with jython as default language… Very disappointed… Apart from some ui change, oh3 will not be installed here. I’ll keep oh2.5 or go to home assistant…

I am strongly considering moving back to HA but I keep hoping somebody will fork OH.

Yes home assistant looks veel good. Quality of integrations (like bindings in oh) i use is also better. It’s sad, i was just getting used to oh…
But, looking for solutions is frustrating, because the docs are not updated, on several places,…
In HA i was able to find info much much quicker.
Well, i guess i’ll buy another raspberry, and use both, and the one that works best, has best support, and documentation, and looks best, will be choosen. At the moment HA has the best points. But, you never know, oh3 will become much better, but they have a lot of work… Also on the bindings. Let’s hope for the best. I liked OH, but the way it’s going now…

Home Assistant, at least a year ago was not stable and, last I checked a few months ago, the code quality was poor. I tried using their new Z-Wave2MQTT just after one of their main developers released an update. I needed to work around serious errors that prevented the code from even operating.

I just see enough discontent here to think there may be a fork soon that is more user focused.

Googling for the error it seems that this problem is due that the value is sometimes an integer and sometimes a decimal and InfluxDB doesn’t like that in the same serie.

But I’m curious about the cause because the fact to try to preserve the type was inherited from the old version from here org.openhab.persistence.influxdb.internal.InfluxDBStateConvertUtils#convertBigDecimalToNum
I don’t know if it can be a change in the Zwave addon that previously worked always in doubles? or some obscure effect on the new addon that I will have to investigate.

In any case, can you test if with that version that always uses doubles you have the problem?

It will be helpful if you can enter openhab console and set TRACE level for InfluxDB binding:

log:set TRACE org.openhab.persistence.influxdb

and then set prior log to the exception

I run into this issue with a humidity channel so I’ve created an issue for it:

Have you ever updated any of the docs?

2 Likes

I don’t think it is fair to compare openHAB 3 which is not released or finished yet and the docs are only just getting started. The milestone is for people to try and give feedback on and test for bugs. I agree with you the better software is going to come down to which one has better support for your hardware and quality of the bindings/integrations and HA may be better for some people. For me openHAB has better bindings as I have been testing both at the moment. As for support this forum is far more helpful.

Hopefully you have contacted the person that maintains the binding in openHAB with some feedback done in a nice friendly way?

5 Likes

Home Assistant claims to not be finished yet It has not even reached version 1.0