You are aware that OH 2 can and does run OH 1.x bindings right? You may choose to stay on OH 1.8, but the lack of a 2.x version of any binding doesn’t mean you are stuck on OH 1.8.
I am aware of that possibility but I didn’t want to distract this thread by getting into the big issue of OH2’s future and upheaval (from a relative outsider’s point of view).
Suffice to say that, for me personally, I’m looking at an OH2 Insteon binding being a milestone at which I’ll put in the effort to upgrade. Otherwise I may look at other options if there’s no way to keep on with OH. 
So, I take it that not signing the old repo is intentional?
I’m guessing not, hang tight, it probably got destroyed at the same time as above one and you are just first to report it on the 1.8 repo
Hi @chrisdumont, not signing the old repo was unintentional, sorry! We haven’t touched it in a while, so there wasn’t a need to update the old repo and I hadn’t realised it was affected!
It’ll have to use the same key as the openHAB2 repo so the steps to recognise the key should be the same.
openhab-linuxpkg/pull/153 has been merged, and I’ve just queued the resigning build. Should be ready within the next 30 minutes now. For openHAB 1.8.3 your sources.list file should look like this:
deb [arch=all] https://dl.bintray.com/openhab/apt-repo stable main
1 Like
It’s nothing to do with that. But your post made it sound like you cannot run a 1.x binding on 2.x which is incorrect. There is already so much FUD and incorrect information on this forum on this topic that I cannot leave that sorry of impression unchallenged as some future forum reader will see the post and come to the wrong conclusion. 1.x bindings work just as well in OH 2.x as they ever worked on 1.8. you are not “stuck” on 1.8. you choose to remain on 1.8, which is fine. It’s your choice to make.
1 Like
Thanks @Benjy for fixing this so quickly. It’s working for me now. Apologies to @rlkoshak I really didn’t mean to stir the pot.
1 Like
Thanks, DiMa – that did the trick!!
- Edit, nothing to see here. If I didn’t have typos I wouldn’t have any typing.
1 Like
hi,
Now the link has expired…showing 404 error
i couldnt download the gpg key
Please read the docs, we had to move to artifactory, as bintray is stopping its service.
You will find several posts here about moving repos.
So how should i install openhab2 for raspberrypi on raspberry jessie OS
Please help me out
Do yourself a favour and download the openHABian image, it will take care about many installation issues.
Sir,
Iam trying to install hestiapi on my raspberry through manual installation
Here I face a problem that after installing openhab …when i load it through localhost and try to install standard mode…its got stuck there for hours… i couldn’t find out the problem
HestiaPi is a third party system, so you better check their community. We cannot give full support on third party systems.
What I could see, their installation instructions are outdated, cause they still refer to bintray, not artifactory.
Thank you sir…for the quick reply
Very sorry to see someone being redirected to documentation with instructions that create the exact same error and leave the user feeling frustrated.
I am coming from the stable 2.5 snapshot. My REST api was suddenly missing, and I was unable to install it. I saw that 3.0 was out and decided to upgrade. following the instructions on Download openHAB | openHAB (you know, the first page people find when they google something)
wget -qO - 'https://openhab.jfrog.io/artifactory/api/gpg/key/public' | sudo apt-key add -
sudo apt-get install apt-transport-https
echo 'deb https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable main' | sudo tee /etc/apt/sources.list.d/openhab.list
sudo apt-get update && sudo apt-get install openhab
This is where things failed for me. Witness:
pi@OpenHAB:~ $ sudo apt-get update && sudo apt-get install openhab
Ign:1 http://repos.azulsystems.com/debian stable InRelease
Hit:2 http://repos.azulsystems.com/debian stable Release
Hit:3 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Err:5 https://dl.bintray.com/openhab/apt-repo2 stable InRelease
403 Forbidden [IP: 3.125.168.216 443]
Hit:7 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease
Reading package lists... Done
E: Failed to fetch https://dl.bintray.com/openhab/apt-repo2/dists/stable/InRelease 403 Forbidden [IP: 3.125.168.216 443]
E: The repository 'https://dl.bintray.com/openhab/apt-repo2 stable InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Using the instructions from here openHAB on Linux | openHAB gives the same darn error.
Finally, a hail mary (per the instructions from july 2019)
wget -qO - 'https://bintray.com/user/downloadSubjectPublicKey?username=openhab' | sudo apt-key add -
gpg: no valid OpenPGP data found.
what fixed the error for me was
sudo rm /etc/apt/sources.list.d/openhab2.list
So the documentation is of no help to users here. It’s probably wise to mention the old repo file needs to be deleted.
1 Like
You need to remove the bintray paths from the apt repos. Bintray is basically gone (they shutdown their support for open source projects) so we had to move to jfrog.
The output is showing that it’s reading jfrog just fine but failing on bintray, as expected.
From a terminal, navigate to /etc/apt and run
grep -R bintray
That will tell you which file(s) is trying to use bintray. Open the file and comment out those lines and the error will go away. Since the jfrog is working that should be all you need to do.
1 Like
That might be a worthwile addition to the installation docs 
Hi All,
Please see the following thread:
Note that if you have the Artifactory repository AND the Bintray repository listed, the error will not mean that you cannot update openHAB, it is simply telling you that it can’t get any information from the Bintray server.
2 Likes
Better check before claiming. The docs @hmerk referred to are up to date and the OP did not even mention what link.