On every event, Sleep as Android will publish a message to SleepAsAndroid topic in the following format:
This is a companion discussion topic for the original entry at https://docs.sleep.urbandroid.org//services/mqtt.html
This is a companion discussion topic for the original entry at https://docs.sleep.urbandroid.org//services/mqtt.html
I have configured Sleep as Android to send events to my MQTT broker using both a āremoteā URL and a local IP address. Sleep as Android appears to send events to the broker ie a notification appears showing the event being sent to MQTT; however it doesnāt seem to be received at the broker and no error messages are displayed. Has anyone got MQTT working?
Hello Benjamin, big thanks for reporting this. We did not yet test the MQTT implementation on a local server here, can you please use menu - report a bug after the event is send by SaA? That would be very helpful.
Hello Benjamin, I have now tested with a local mosquitto instance and it workedā¦ I think the problem is the URl needs to have protocol tcp or ssl not mqtt as stated in the hintā¦ Iām fixing this for the next BETA release, which Iām going to release nowā¦ there was also a crashing bug on disconnect which Iām fixing too so please updateā¦many thanks for your feedbackā¦
Hi Petr. Thanks for the update! Iāve submitted a new bug report as SaA itās now working with a URI like tcp://192.168.0.254:1833 but not tcp://user:pass@host.ddns.net:1883 ā¦ Ben
1 Like
@petr-urbandroid, Iāve just set up the MQTT integration to use with my openHAB home automation system, and it works great. Iāve written a tutorial for other openHAB users.
Is there a possibility of sending commands to Sleep as Android over MQTT in the future?
Thanks!
1 Like
Hello, big thanks for the guideā¦ this is great! Can we include a link into our documentation? We will look into feasibility of a listener for MQTT command son the SaA side although I see some technical issues hereā¦ big thnaksā¦
You can definitely include it here. Iāve already made some edits to improve it.
Iād be happy to test MQTT commands if and when youāve got something to try. If there are concerns about the impact on battery, perhaps it could be set to only listen when the device is charging?
New question for you: how are the value1, value2, and value3 codes generated?
It occurred to me that it would be valuable to be able to distinguish between alarms, and perhaps the values do that in some way. If not, it would be great if an alarm identifier could be added to the MQTT payload.
I had a connection with mqtt on my homeassistant yesterday however for some weird reason it didnāt show up today anymore. I hadnāt changed anything in the settings. I used ātcp://homeassistant:[mypassword]@[myduckdns].duckdns.org:1883ā and it was publishing fine on itās topic. Has there been an update breaking it or is it just me being stupid?
Mqtt works great on my OnePlus, but it often gets stuck on my wifeās Pixel 3XL. Randomly throughout the night, the MQTT notification gets stuck and doesnāt go away unless I force stop the app. After it gets stuck it doesnāt send anymore events. Any suggestions on how to fix this? Iāve already checked the power/battery management settings
For some reason everything is working again. Not sure if youāve patched it but if so. Thanks 
Hey,
when i activate my sleep tracking it first fires:
{"event":"sleep_tracking_started"}
and instantly after that:
{"event":"sleep_tracking_paused"}
and:
{"event":"not_awake"}
when still the 1min timer runs down.
This makes no sense because i am still āawakeā when the timer runs or when i extended the timer. Instead of ānot_awakeā, āawakeā should be fired when the timer starts.
Also when i turn on my screen again it fires:
{"event":"not_awake"}
I never saw:
{"event":"awake"}
Maybe this only shown after a longer time when moving the phone or something.
A nice feature would be to send the next activated alarm, so i can for example activate my ceiling light few minutes before the alarm starts.
Edit:
Also tested with the newest beta, it fires another sequence of events:
{"event":"sleep_tracking_started"}
like the normal version but then:
{"event":"not_awake"}
and after the 1min timer runs out
{"event":"sleep_tracking_resumed"}
For me this looks worse then the normal version, because its resumes without pausing it first.
Please fix it and think about my feature suggestion ^^
Hello, many thanks Iām preparing a fix for the immediate firing of the not_awake eventā¦ the reason is it takes some time (1-2 min and more) before the Awake heuristics get into a confident awake stateā¦
Edit:
Also tested with the newest beta, it fires another sequence of events:
{"event":"sleep_tracking_started"}
like the normal version but then:
{"event":"not_awake"}
and after the 1min timer runs out
{"event":"sleep_tracking_resumed"}
For me this looks worse then the normal version, because its resumes without pausing it first.Please fix it and think about my feature suggestion ^^
Little bit more info about the beta version behavior added. Thanks for quick answer @petr-urbandroid ^^
Our mqtt broker password has characters that are not acceptable in a URL, and I am not able to change the password. Is there an alternative way to provide the password?
Hello @Will_Freeman I guess you can simply URL encode the password? Please see https://www.urlencoder.org/
Hello! Do you have a list of the event name descriptions? Tasker has broken so I was trying to get mqtt to talk straight to node red. I want to set a lights event when sleep smart period starts. I suspect event is called sleep_smart_period? What other events can I use? When are they called and the name? Iād like one for when I dismiss my alarm too.
Thanks! You are an amazing programmer and I bought the unlock tonight. You have 1M supports so you should be doing well! Thanks again.
Hello Josh, Tasker should be working well, but you need to explicitedly enable Tasker support in Settings > Services > Automation > Taskerā¦ in the same scree you see all events and their descriptionā¦