Yes these are the two things that are supported by the binding. Can you add things or does this give you more exceptions?
Have you already had the mqtt binding installed?
I don’t know what the exception means, maybe this is just a small hickup right after the installation!? Please try to use the binding by adding things and tell me whether this works for you. Thank you!
I just got a TC001 and haven’t heard of Awtrix until today. Maybe it’s a stupid question, but what does it mean when it says here https://awtrixdocs.blueforcer.de/ that Awtrix 2.0 got discontinued? I don’t read anything about a successor. Is this even relevant for using the binding?
I didn’t use Awtrix 2.0 myself but as far as I unterstand it Awtrix was a complete DIY solution that you could build yourself. Awtrix light can be seen as a successor to Awtrix 2.0 but it can be installed on the ready to buy TC001 hardware. But that is just my understanding, please correct me if I’m wrong
Yes, correct.
There is even a firmware for old Awtrix2.0 displays to change them into Awtrix lite.
The naming is a bit weird as Awtrix lite is much more powerful than Awtrix2.0, but to be fair, Awtrix2.0 was able to - sort of - run standalone, where an Awtrix lite hardware is reduced to time and date without an additional server (which is irrelevant in openHAB context ).
It seems that something went wrong with the installation because I don’t see that you could add the device manually either which means that the binding is not installed. Do you have any errors in the logs after you dropped the jar file in your addon folder?
I just downloaded the file with wget again and used diff to compare with my local copy. The files are the same. So if the file is corrupt something went wrong on the way from Dropbox to your machine.
This is the result of md5sum of the package: 630ee046461de97f47c5b54140e00425
If you have the same file then something else must be wrong
Thank you for your input. This might help to track this issue down. My problem is that I cannot reproduce this on my system. It just works for me and also for other users. I’m also on OH version 4.1.0… weird that you don’t see any errors in the logs
One question: have you set proper file permissions? Is your OH user able to access the file?
i´m running it with docker under portainer in a stack - for testing i set also the file on 755
but openhab do not see it… other files like rules a without any problem
Yeah 755 should be enough. I always transfer ownership to the openHAB user. But I think it’s just a habit, technically I do not see why this would make a difference.
The latest binding builds will only work on 4.1.0 and up due to a missing gson dependency in older versions. So the error on 4.0.3 is expected. However it should install also in the 4.1.0 version and it sure does in mine.
I threw away the old 4.1.0 container and setup a new one with update from 4.0.3 (the version with active but framework error). After the update I put the jar in the addon folder an … YES