MQTT Integration

[nonsleepr]

I have limited resources right now.
It would be awesome if someone integrates that package though: https://github.com/nonsleepr/python-eufy-security-mqtt

[rschoolm]

I’ll have mine installed this weekend. I can test if you still need it.

[joepadmiraal]

I would love to test this but I am having some trouble in running the example.
I changed the variables in subscribe.py and when I run it I get this:

python3 subscribe.py
Traceback (most recent call last):
  File "subscribe.py", line 2, in <module>
    from eufy_security.mqtt import DoorbellEvents
ModuleNotFoundError: No module named 'eufy_security'

What do I need to do before I can run the example?

[nonsleepr]

@joepadmiraal You need to pip install . first.

[joepadmiraal]

Thanks.

When I run it now I get this error:

Connection rejected with code '5'
Connection failed: ConnectException('Connection rejected by broker')

I got the userId by reading from the passport/login API call.
For email I used the same email address that I used in the app.
I red android_id by going into the adb shell of the emulator and running settings get secure android_id

I also changed the url to security-mqtt-eu.eufylife.com:8789 in the init file because I am based in the Netherlands.
But that gave the same results.

Googling code 5 seems to reveal it is an authentication issue.
Any idea what I could try next?

Thanks

[nonsleepr]

Try running the following script (requires mosquitto-clients installed, you can get eufy.crt from the package):

#! /usr/bin/env bash
set -x

device_sn=T8200N0XXXXXXXXX
email=YOUR@EMAIL.COM
# adb shell settings get secure android_id
android_id=deadc0dedeadc0de

username=eufy_$user_id
password=$email
client=android_EufySecurity_${user_id}_${android_id}

mosquitto_sub \
 --cafile eufy.crt \
 -C 1 -F '%p' -N \
 -h security-mqtt.eufylife.com \
 -p 8789 \
 -t "/phone/doorbell/$device_sn/push_message" \
 -u "$username" -P "$password" -i "$client"

[joepadmiraal]

I ran this (replaced some details with X):

set -x

user_id=cc05d0a796a1877a352e7ee80XXXXXXXXXXXX

device_sn=T8010PXXXXXXXXXX
email=XXXXXXXXXX@XXXXXXXXXX.nl
android_id=f404f4XXXXXXXXXX

username=eufy_$user_id
password=$email
client=android_EufySecurity_${user_id}_${android_id}

mosquitto_sub \
 --cafile eufy.crt \
 -C 1 -F '%p' -N \
 -h security-mqtt.eufylife.com \
 -p 8789 \
 -t "/phone/doorbell/$device_sn/push_message" \
 -u "$username" -P "$password" -i "$client"

Result:

mosquitto_sub --cafile eufy.crt -C 1 -F %p -N -h security-mqtt.eufylife.com -p 8789 -t /phone/doorbell/T8010PXXXXXXXXX/push_message -u eufy_cc05d0a796a1877a352e7ee80XXXXXXXXX -P XXXXXXXXX@XXXXXXXXX.nl -i android_EufySecurity_cc05d0a796a1877a352e7ee80XXXXXXXXX_f404f4XXXXXXXXX
Connection error: Connection Refused: not authorised.

After it did not work I replaced the android_id with one from a real device which also has the app installed.
That gave the exact same result.
Also replaced the host with security-mqtt-eu.eufylife.com.

Is it correct that the email address is used as password?

[nonsleepr]

Yes, that's how it's implemented in the Android app. Have you tried another host (security-mqtt-eu.eufylife.com) here too?

[nonsleepr]

@joepadmiraal Haven't tried to MitM, however, the code in the repo and the script works for me with wired doorbell and in the US though (used my primary account). I can run your case under debugger if you create a disposable account for me (can email it to me) and aren't concerned about the privacy implications that much.

…

On Wed, Jun 3, 2020, 1:56 PM joepadmiraal ***@***.***> wrote: Yes already tried security-mqtt-eu.eufylife.com. I have been using the main account to test. Did you also do this or did you use a dedicated guest account? Did you ever manage to do a mitm with mqtt on the eufy device? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR2WQW2TS6M3P3RAMP4GYTRU2FERANCNFSM4NMM2IGA> .

[joepadmiraal]

I figured out I mixed up two accounts.
So now it is not giving me any errors when I start the script.
However it also does not show any events at all.

I'll create a temp account and email it to you.

[PrayerfulDrop]

@joepadmiraal

How did you execute the passport/login API to get the userid?

[joepadmiraal]

I changed api.py so it reads and exposes auth_resp["data"]["user_id"].
With that I could let test_api.py print the userId.

[PrayerfulDrop]

@joepadmiraal @nonsleepr

Thank you for the info on finding the user_id. Needed to modify the api.py in my usr/bin/lib directory.

With the above script, are you doing this to acquire a new eufy.crt that is associated to your eufy doorbell?

If I create an executable script with my user_id, serial_number and email addy I get an error that the the file cannot be found.

If I copy the file eufy.crt from the src folder to my getcert.sh location then I get "connection refused not authorized."

What am I potentially doing wrong?

getcert.sh

set -x
user_id=955b3b9241fa76f2559ece18247XXXXXXXXXXXXX

device_sn=T8200N00XXXXXXXX
email=aXXXXXXXXXXXXXXXXXXXX.cc
android_id=deadc0dedeadc0de

username=eufy_$user_id
password=$email
client=android_EufySecurity_${user_id}_${android_id}

mosquitto_sub
--cafile eufy.crt
-C 1 -F '%p' -N
-h security-mqtt.eufylife.com
-p 8789
-t "/phone/doorbell/$device_sn/push_message"
-u "$username" -P "$password" -i "$client"

[keshavdv]

It's possible that the wireless version of the doorbell relies on the FCM path like the floodlight rather than MQTT, in which case, I don't think would show any events. I can confirm the MQTT integration did work for me with a wired doorbell so it's still probably worthwhile to integrate for at least that set of users to be able to get realtime motion events for HA.

[PrayerfulDrop]

@keshavdv i have the wired doorbell and cannot connect to the Mqtt service. Can you provide guidance?

[joepadmiraal]

@joepadmiraal @nonsleepr
With the above script, are you doing this to acquire a new eufy.crt that is associated to your eufy doorbell?

I deleted the certificate and ran make in the repository directory to create a new certificate.
I don't know if that is actually needed.

If I copy the file eufy.crt from the src folder to my getcert.sh location then I get "connection refused not authorized."

What am I potentially doing wrong?

I rechecked it today and I am now also getting errors again when using the eu servers.
With the standard security-mqtt.eufylife.com server from the script it does not give a authorization error.

Now that I think of it, another reason for why I don't get any MQTT messages could also be because I have a European model instead of a US model.