Thank you.
I thought this installation was also not working, but its inside the MQTT Binding so I don’t found it.
But now its working 
But I still have one issue. I cant delete an APP
I set the Active Switch to Off and then delete the Thing
But it will still shown on the clock
Hm I just tried it with one of my apps on the clock standing next to me. The app disappears as expected when I switch the active channel to OFF. Just to make sure: Did you send the OFF command to the active item or just updated the state? Does the app disappear when you switch the item to OFF and reappears later or does it stay when you flipped the switch? Could there be a rule that is reactivating the app accidentally?
I will test it with the next try. I helped me now with the AppLifetime 
It was then deleted.
Thanks for your help, and that’s a really nice binding, so thanks for your work too
Hey,
after Update OH to 4.2.1 the Problem with org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.mqtt.awtrixlight [243] is back.
Could you please check it and give an Update?
Thanks
Daniel
Hi Daniel,
thank you for reporting this. I can confirm that the binding does not seem to work with 4.2.1 and I will provide a fix for that as soon as I’m back from my holidays end of this week!
Regards,
Thomas
After my nightly backup (comes with a OH restart) my things are back online. Have you tried restarting OH?
Hi Thomas,
yes, several times. Also reboot the hole system - but nothing changed.
Regards,
Daniel
Hi Thomas,
after fixing the issue with installing the Binding in openHAB 4.2.1, could you please host the jar file on github and add a raw downloadlink to your first post. this should solve the marketplace issue.
Since it does work for me with OH 4.2.1 I don’t really know what to fix but I can compile it against the new version of course and we will see if this helps.
Ok I will change the file hosting, I already assumed that the hosting on Dropbox might be the problem.
I can also confirm that after deleting, restarting openhab, new downloading from Dropbox, restart openhab the Add-On is working again.
Thank you!
I changed the link in the first post now to a jar file hosted on Github. It’s the same release as before, just a different hosting provider to see if the binding now can be downloaded via marketplace.
just checked on my test system and it seems to work, finally
@DrRSatzteil
First of all, thanks for the Binding. I was able to discover the Ulanzi TC100 flashed with AWTRIX 3 (v0.97), created two things, the bridge and an app thing.
Now I struggle with allways having the message “NEW AWTRIX APP” scrolling before my custom App is showing. Any hint, how to get rid of this anoying message ?
Edit: Found it, there was somehow a fragment of an old app with wrong app name. after creating a new app thing with the false app name, i was ablle to deactivate it.
So one has to be carefull with renaming apps on thing level, which leads to this effect…
Yes that’s true. The reason is that I use retained mqtt messages for persistence. The binding should get the current app state from mqtt after a reboot and so should the clock. The downside is that if you just delete the thing the message will still be there and will be displayed on the clock. I wonder if there’s some kind of callback when the thing gets deleted, I should be able to use that to remove the app from the mqtt brother then (the same thing that happens when you disable the app).
Yes, it is reappearing after deleting the thing. So atm I need to have a dummy thing with this wrong app name and the power switch linked to it. Not nice, but I have a workaround. Would be great if you can find a permanent solution.
Edit: I found this topic about removing retained messages, might be helpful…
Clearing MQTT retained messages - Tutorials & Examples - openHAB Community
I just double checked my code. It’s actually quite simple. I could just delete the app when the app thing gets disposed (deactivated in the UI or deleted completely). This could replace the activate/deactivate channel. Instead one could just deactivate the thing.
Unfortunately my good old notebook died a couple of days ago, I’m currently waiting for my replacement. I can use this as my first project 
No, I need the activate/deactivate channel as I have two different apps to be controlled via rules. Dont want to go the “ugly” way of activating a thing through a rule.
Sure we can just keep this as well. The only downside with the activate channel is that you have to understand that it will effectively remove the retained mqtt message from the broker. Thus when you reboot your OH instance all items will be reset to the default values. It’s probably not an actual problem for most people but I never liked this behaviour because it’s hard to explain to users.
A good alternative is a short timeout on the timeout channel. This will leave a message on the broker and thus keep your data persisted across restarts. At the same time the app will be hidden on the clock after the timeout has passed.
This is not an issue for my use case. It is for our demo setup to be shown at FOSDEM in Brussels.
I will create a “init” rule to set all needed AWTRIX items with the desired values after powering the demo-case.
Another suggestion, I am missing channels to play sounds in the app Thing…