Yes, you will need 2.5.
Thx very much Guys Up till recently I was still running 2.1. No reason for me to update as it worked perfectly. After updating the repository I could update to 2.5. Now running the latest Nikobus binding.
If you were running a version that old, you should check to see how many of your other bindings now have a 2.x version. There has been a lot of development that has occurred in the past 2 1/2 years.
True, I had just one binding running until very recently, and then could add a nice second 2.x one.
I have no indication anybody involved in core development is even considering to remove text file configuration.
That is great news. I was asking because some of the discussions for the new UI gave that impression.
That will not happen as I need serial to run over 30 DIY devices running a custom protocol on serial. See the thread below. BTW I don’t believe other home automation packages have serial port support, Openhab is the only one as it has been around the longest.
This post was flagged by the community and is temporarily hidden.
Is the 2.5.1 stable version out for updating with openhabian.config right now?
If I do a “sudo apt-get upgrade -s” on a openhabian installation the 2.5.1 version isn’t found…
sudo apt-get upgrade -s
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
Verwenden Sie »sudo apt autoremove«, um es zu entfernen.
Die folgenden Pakete sind zurückgehalten worden:
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
No the release has not been announced They hope to do that in January last I heard.
It should be released now, see:
Sorry, I was traveling all day and am on a business trip this week. I missed the announcement.
Hi, tried to update to version 2.5.1 with openhabian-config tool.
Unfourtnately the version isn’t found by openhabian-config.
If I use function “03 | openHAB Stable Install or upgrade to the latest stable release of openHAB 2”
only Version 2.5.0 is found.
How can I update to 2.5.1 with openhabian-config?
Thanks a lot
Via OpenHabian I also am not able to upgrade, it always says I’m on the latest version, no upgrade is required.
Actually, 2.5.1 will say 2.5.0 on the dashboard because they did not ( ans likely will not) update openhab-core. 2.5.1 is designed so addons updates dab be released separately from the rest of openHAB.
I am away from home for the week so I cannot test to verify.
Please also be aware that the footer of the dashboard will still say “openHAB 2.5.0 Release Build” - this is because the version of the core runtime is show, which has not been touched at all. To see the detailed version information, please have a look at
userdata/etc/version.properties , which should look like:
openHAB Distribution Version Information ---------------------------------------- build-no : Release Build online-repo : https://openhab.jfrog.io/openhab/libs-release Repository Version ---------------------------------------- openhab-distro : 2.5.1 openhab-core : 2.5.0 openhab1-addons : 1.14.0 openhab2-addons : 2.5.1 karaf : 4.2.7
I also have a lot of serial devices. I have moved from serial binding to a global cache device.
- this device is more expensive than a serial cable but you can place it anywhere on your network there is a wireless and a wired version
- you have to make minor readjustments to your code ( for some characters you will need to use their hex code EX @ character for global cache is %40)
- it uses an End-of-message Delimiter to separate each message (it might not work for some devices)
- if you decide to use this device get the itach devices because their firmware is user upgratable while he GC- device need to be sent back to global cache to be upgrated
just use “sudo openhabian-config" and select " 02 | Upgrade System Upgrade all installed software packages to their newest version”.
You will not see the changes in your dashboard. But when logging in via Putty you can see:
I have looked at this a couple of times, as I have a large Insteon installation. It is quite a daunting proposition. The original InsteonPLM binding is a bit of a kludge (which the original author freely admits), and it doesn’t support a number of new devices (like motion sensor 2, siren module etc.). Also open/close sensors do not work well (triggers can get missed).
I finally decided to move to ISY (944i) for my Insteon interface. This works extremely well, is very fast, and is actively supported.
The problem now is how to interface ISY to OH2? There is an ISY binding for OH2 out there, for V2.3, not “official”, and not updated in 2 years. Might be worth looking at, needs some work, but less than the InsteonPLM binding.
What I did finally was to take the python interface to ISY (under active development), and interface it to MQTT (quite easily done in python). Now my Insteon devices are linked to mqtt2 items in OH2, and all my config/administration is done on the ISY. This is a much better solution than the direct interface via the InsteonPLM, I should have done this years ago.
This solves the following problems
- You can’t configure the Insteon devices from the insteonPLM binding, you still need some other way of doing that (I was using homelinc, but that has long been abandoned by Smarthome).
- Gives you an independent way to check/control/test/add/delete/link your Insteon devices (while OH is running).
- Can trigger scenes, including keypadlinc buttons, and setting button light state.
- Insteon device states are preserved if OH2 is restarted, as they are read from the ISY, which is on 24/7.
- No serial/USB interface required, works over the network, so no wired connection to your OH2 device.
- Because it’s python/MQTT it’s really easy to add/fix/change things. No arcane Java knowledge or massive development environments needed.
- PLM can be backed up or restored independently.
- Also supports Zwave if you get the Zwave version.
Drawback is that you have to buy an ISY 944i, and a new PLM.
So I think that you should take a look at the ISY v2.3 binding https://github.com/HentschelT/openhab2-addons/tree/master/addons/binding/org.openhab.binding.isy
And see if is worth porting the insteonPLM binding, or updating the ISY binding.
I’ve already ported the code, see New Insteon 2.5+ binding.
Is there already a timeline for 2.5.2?