Have you tried using openhabian-config tool selecting “Apply Improvements” and “Install needed packages”?
Yes, that’s why I’m bringing it up as a topic here Thinking about it, last time I ran into this issue I ended up with installing Debian 9 as a virtual server on my Ubuntu 18 to go around the issue. I’m hoping there are better ways though.
Currently I would say that openhabian-config is not compatible with Telldus-core on Ubuntu.
Telldus-core is not maintained by Telldus any more. On my rpi I was using this guide https://www.kentsvanberg.se/tellduscenter/guide.php, newest raspian have the same libconfuse2 (1) problem.
Tellstick Binding are not working when upgrading to 2.5.0-1 from 2.4.0-1 losing sensors at least. “Telldus Live Gateway” that is my problem. Got back to 2.4.- and sensors came back.
This is a distribution problem from what I understand. It’s not a matter of finding the libconfuse library. The problem is that it’s depending on an old libconfuse library that isn’t available in Ubuntu 18.
I tried to see if the libraries can co-exist but they can’t since both of them, the required libconfuse1 and the available libconfuse2 both depend on libconfuse-common but in different versions.
Trying a manual install of libconfuse1 taken from Debian 9 repo gives this
sudo dpkg -i libconfuse1_3.0+dfsg-2+deb9u1_amd64.deb
dpkg: dependency problems prevent configuration of libconfuse1:amd64:
libconfuse1:amd64 depends on libconfuse-common (= 3.0+dfsg-2+deb9u1); however:
Version of libconfuse-common on system is 3.2.1+dfsg-4ubuntu0.1.`
As @rhis mentioned this seems to be a problem on newest Raspian as well. If the option of installing telldus-core are to remain in openhabian-config tools I think this needs to be adressed.
Does anyone know what sources are used to compile the telldus core package referred to by openhabian-config?
I can compile the sources above on github with libconfuse2 without any problems, so it seems to be a matter of recompiling and repackaging, but what should be recompiled?
Thanks for the link @Bruce_Osborne. This particular add-on depends on an external library as stated in the docs.
The telldus-core bridge uses a library on the local computer which is a .dll file for
Windows and a .so file for Linux. The default one is usually correct.
The issue here is that we can’t install that external library, so it’s kind of outside the scope of the 2.5 repo. The external library is provided by the openhabian-config tool but it gets failed dependencies on newer distributions of Linux. However, one solution would be to re-write the addon to talk directly to the tellstick without using that external library.
Thanks for the link @Joachim_Brolin. It’s infomative on how to compile the sources I will continue to look for the tdtool-improved sources, but for now I’ll probably just settle for Debian 9 on my upcoming installation.
which describes how to compile a debian package from source.
My solution for debian based distributions are as follows
# Add telldus repository to apt sources
sudo apt-key add telldus-public.key
sudo echo "deb-src https://s3.eu-central-1.amazonaws.com/download.telldus.com unstable main" >> /etc/apt/sources.list.d/telldus-unstable.list
sudo apt-get update
# Get packages needed for general builds
sudo apt-get install build-essential fakeroot devscripts cmake
# Needed to sucessfully run build of telldus-core but not specified as build deps
sudo apt-get install libftdi-dev libconfuse-dev help2man
# Get build deps that are specified in the package telldus core
sudo apt-get build-dep telldus-core
# Add the linker flag for pthread, otherwise linking will fail
# Get the source of telldus core
apt-get source telldus-core
# Build packages (unsigned)
debuild -b -uc -us
# In case the build complains about a missing Doxyfile.in, create an empty one
# Install the newly built packages
sudo dpkg -i libtelldus-core2_2.1.3-beta1-1_amd64.deb
sudo dpkg -i telldus-core_2.1.3-beta1-1_amd64.deb
Hi, i was trying to install (compile) this on newly installed Pi but not a chance, is there any plans to uppdate this guide, last time i installed openhabian it was part of the optional components but not any more, and now im stuck with no light switches any more (not a very high waf)…