MMM-WeasleyClock: authorization error
I’m a newbie here and I do not know if this is the right place for this post. So please apologize for possibly bothering you…
I realized my first magic mirror on a Raspi a few weeks ago and it worked instantly without any errors! (Thanks a lot to Michael Teeuw and all of you!!!)
I was so thrilled that I wanted to setup a second one with just the “Weasley Clock” for my youngsters - no sooner said then done. I set up my own MQTT broker (mosquitto) and installed the MMM-WeasleyClock. The broker is up and running and the installed owntracks apps on our mobile phones have been connected successfully.
When I start the magic mirror it crashes as soon as I include the MMM-WeasleyClock module. To my mind this is not a magic mirror error because there is no error when I remove the MMM-WeasleyClock module.
I set up mosquitto with TLS/certificates, ACL and user/passwords. Hence I think that I have a bad configuration of the MMM-WeasleyClock module:
Please accept my apologies if this is not the the right forum (and close/delete this issue).
Any hints highly appreciated. Thank you very much in advance.
May the code be with you!
@kai This is EXACTLY the right forum for your question.
You seem to have an error in your MQTT settings.
Maybe a wrong password?
Hey guys, the Weasley Clock is my module. I’m glad you got it working with your own MQTT server. The plan is to include instructions on how to do this. But I’m glad that you got it running for you.
If you have suggestions or better yet, a pull request, I’m all ears.
Do not try to connect to my MQTT server. Short version: It’s broken and I’m working on fixing it. It’s not you, it’s me.
Long version: The module relied upon an poor implementation of OwnTracks with regards to TLS encryption. The latest version of OwnTracks fixed the implementation, so the module stopped working. Essentially, I need to figure out a better way of distributing the authorization key with the module.
I have a fix in progress. I’ll let you know when I get it up & running.
Just an update: My MQTT server is back up & running again. It’s SSL enabled if you like, so you can just connect to it without specifying the CA file.
Updated version with better instructions coming soon.
@bhepler Hey. great addition when we can expect a repository refresh
Is there a chance to use the MQTT Broker and Location with Home Assistant?
@dudus200 - Hey sorry for the delay. I have another project that is taking up a lot of my time.
I’m working on the next version which will include instructions on how to set up your own MQTT server and how to connect to it with or without the TLS encryption. That should give you the option to roll your own or tie into your own MQTT server if you have one connected to Home Assistant or whatever.
I’m not terribly familiar with Home Assistant. What sort of integration did you have in mind?
thank you so much for all your effort! I really do love the Weasley Clock!
Since Sept 2021 I have difficulties with the OwnTracks app - probably due to the app’s update you mentioned here. (OwnTracks app always shows an “idle” state and does not connect to my MQTT server which has a signed cert from a known CA. Removing the app’s certificate didn’t help so far - or I did something wrong.)
Hence I’m eagerly awaiting your instructions on how to set up my own MQTT server and how to connect to it with or without the TLS encryption.
May the code be with you
(OwnTracks app always shows an “idle” state and does not connect to my MQTT server which has a signed cert from a known CA. Removing the app’s certificate didn’t help so far - or I did something wrong.)
This sounds like OwnTracks is in “manual” mode where it will not attempt to update location unless you touch the update button. If you are on the map screen and you see what looks like the Pause button on your stereo, I think that is the indicator. Press it a few times until it shows the “play” icon (triangle with a point facing to the right).
Then go back to the status page and see if it goes away from Idle. Let me know what you see.