Allow sending discovery packets to static IP address #5
Comments
|
Hi, that's odd. Maybe the robot just wasn't responding to those discovery packets? Could you try it again multiple times, for some reason the vacuum does not always answer to those calls but I'm not sure what's the cause for it. |
|
I tried it from the raspberry PI I have HA and it's happening the same thing... I can ping the vacuum and I tried to ssh, but I'm getting "ssh: connect to host 192.168.8.1 port 22: Connection timed out". I didn't read the post you used to create the script or took a look at you code, so I don't know what I should expect. What I can say is that I did upgrade the firmware the first time I used the app... |
|
The vacuum doesn't accept incoming connections, port 54321 is the only way currently to communicate with them. You could try to see with wireshark if the device responds something to those discovery packets, other than that I can't really help without more information. |
|
I had to change s.sendto(helobytes, (addr, 54321)) to s.sendto(helobytes, ('192.168.8.1', 54321)) and get the response on wireshark, after that I could use the token with everything else... I'll try the HA integration now. Thanx anyway! |
|
Nice to hear you got it working, did you get it working with that on Windows or on Raspberry pi? |
|
After getting the token from wireshark it's working on both and on HA. |
|
Hi, I am trying to discover it but I have the same behavior : I am using windows 10 with pycharm, python 3.6 in a virtualenv. I tried many times. I tried to set the timeout to 20s but nothing better. I can try something with wireshark but I am not confident with it. |
|
This sounds like that is not working correctly on windows (10?), so I'll reopen this for now. Unfortunately I have no time to put into this, but maybe someone with a windows installation can help me out? Another possibility would be to just "broadcast" the message to that static IP for now but I feel that's the wrong way to do it (although sofar this IP has been always used by this vacuum afaik). |
|
Thank you for your anwser, I tried with "Ubuntu for windows", I tried with
a VirtualMachine Ubuntu : nothing works. I am going to try with a live
Ubuntu.
Le sam. 29 avr. 2017 à 00:50, Teemu R. <notifications@github.com> a écrit :
… This sounds like that is not working correctly on windows (10?), so I'll
reopen this for now. Unfortunately I have no time to put into this, but
maybe someone with a windows installation can help me out?
Another possibility would be to just "broadcast" the message to that
static IP for now but I feel that's the wrong way to do it (although sofar
this IP has been always used by this vacuum afaik).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AVLKy-o1aWjwZ_Mov4zSv1w0xmkDhxJqks5r0m1FgaJpZM4M9uit>
.
|
|
So I set-up ubuntu on another drive and it works.
Le sam. 29 avr. 2017 à 11:55, Pulse Mind <pulse.mind.com@gmail.com> a
écrit :
… Thank you for your anwser, I tried with "Ubuntu for windows", I tried with
a VirtualMachine Ubuntu : nothing works. I am going to try with a live
Ubuntu.
Le sam. 29 avr. 2017 à 00:50, Teemu R. ***@***.***> a
écrit :
> This sounds like that is not working correctly on windows (10?), so I'll
> reopen this for now. Unfortunately I have no time to put into this, but
> maybe someone with a windows installation can help me out?
>
> Another possibility would be to just "broadcast" the message to that
> static IP for now but I feel that's the wrong way to do it (although sofar
> this IP has been always used by this vacuum afaik).
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#5 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AVLKy-o1aWjwZ_Mov4zSv1w0xmkDhxJqks5r0m1FgaJpZM4M9uit>
> .
>
|
|
Otherwise with windows 10 the easiest way is to :
* reset wifi on the vacuum (press both button on the vacuum)
* reset the vacuum
* connect to the wifi of the pc to the wifi of the vacuum (rockrobo-xxxx)
* open packet sender (portable)
* set the ip : 192.168.8.1, hex :
21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff,
port : 54321, Protocol : UDP
* send
* In the answer as hex takes the last 16 characters (do not count white
spaces). This is the token.
* switch to your wifi
* use your mobile phone and mihome app to set-up the vacuum
* then you can use mirobo python to get values... (use export to set the IP
of the vacuum on the wifi and to set the token or use --ip and --token)
Le sam. 29 avr. 2017 à 11:54, Pulse Mind <pulse.mind.com@gmail.com> a
écrit :
… So I set-up ubuntu on another drive and it works.
Le sam. 29 avr. 2017 à 11:55, Pulse Mind ***@***.***> a
écrit :
> Thank you for your anwser, I tried with "Ubuntu for windows", I tried
> with a VirtualMachine Ubuntu : nothing works. I am going to try with a live
> Ubuntu.
>
> Le sam. 29 avr. 2017 à 00:50, Teemu R. ***@***.***> a
> écrit :
>
>> This sounds like that is not working correctly on windows (10?), so I'll
>> reopen this for now. Unfortunately I have no time to put into this, but
>> maybe someone with a windows installation can help me out?
>>
>> Another possibility would be to just "broadcast" the message to that
>> static IP for now but I feel that's the wrong way to do it (although sofar
>> this IP has been always used by this vacuum afaik).
>>
>> —
>> You are receiving this because you commented.
>> Reply to this email directly, view it on GitHub
>> <#5 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AVLKy-o1aWjwZ_Mov4zSv1w0xmkDhxJqks5r0m1FgaJpZM4M9uit>
>> .
>>
>
|
|
Great to hear that you got it working! As the robot is always on that given IP, maybe it makes sense at least to allow using a static IP for the discovery, so let's keep this issue open. |
|
@pulse-mind @FabioDeMiranda The same problem, the use of windows10 under the following PIP3 virtualenv interface error. I have reset the vacuum, I would like to ask you how to solve it? Please tell me the order, thank you! |
|
I do not know how to do the discover with python and how to adapt this code. |
|
@pulse-mind |
|
The tool here is great. It can does a discover = display the token. And then it can get the information of the vaccum and send commands. But to get the information and to send commands, you need the token. The token is used to encrypt and decrypt the command. Without the token it is "impossible" to communicate with the vacuum. |
|
@pulse-mind Thank you. I'll try it when I get home! Thanks for reply! |
|
@pulse-mind * open packet sender (portable) * hex:21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffff, port:54321, ip:192.168.8.1, protocol: UDP * send * in sixteen hexadecimal answer, the last 16 characters (not counting spaces). |
|
yes. |
|
@rytilahti Thank you！！ The article said that yesterday to see over the notebook computer can install the Mi application can capture. I haven't tested it yet! |
|
@pulse-mind Thank you It has been successful! |
rytilahti
changed the title
|
Considering that the new discovery is done over mDNS, and that the "handshake" discovery is sent to the given IP when executing any commands, I think this can be closed now. |
Hi there!
I reset the WIFI pressing the home and power buttons, after that I pressed the reset, but in both cases I'm getting the same message:
mirobo discover
INFO:mirobo.vacuum:Sending discovery packet to with timeout of 5s..
INFO:mirobo.vacuum:Discovery done
I'm using a Windows 10 machine with python 3.6.1 , I scanned with nmap the vacuum IP (192.168.8.1) and it seems the only ports open are 22 and 53... Am I missing something?
Thanx for creating this script and integrating with HA!
The text was updated successfully, but these errors were encountered: