Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARNING: A device with this name [Archive] already exists, but was connected to a different hardware id. #4

Open
mabahj opened this issue Jun 5, 2022 · 2 comments

Comments

@mabahj
Copy link

mabahj commented Jun 5, 2022

I'm trying to switch from a different jottacloud docker image to this, but I got this error message, which I see in your entrypoint.sh (the TODO) is really not supported. It then fails:

Devicename[bluet-jottacloud]: Archive
WARNING: A device with this name [Archive] already exists, but was connected to a different hardware id.
        You can choose to connect to this device but it is not recommended.
        Do you want to connect to [Archive]? (yes/no): couldn't read file "remote": no such file or directory

I've tried to use "expect" myself, but I really never understood how it works. So I'd like to help, but I'm not confident enough to provide a PR.

If this does not bother you, then please only consider this bug report as FYI. Thanks for sharing your setup.

@bluet
Copy link
Owner

bluet commented Dec 14, 2022

Hi @mabahj sure would you like to share your fix? :D

@mabahj
Copy link
Author

mabahj commented Dec 14, 2022

I'm sorry, it is quite a while ago and I do not remember how I solved it. I'm using a very messy locally changed version of https://github.com/maaximal/jottadocker now, probably a merge of your version and that version. I do not have any code to solve that question in my version, so I assume I just changed the device name.

I guess something like

expect \"Do you want to connect to [*]? (yes/no):: \" {send \"yes\n\"} 

Could work? (Not sure about the * syntax). And I am not sure if "except" is mandatory or not, i.e. if it will just proceed if that message was not printed or if it will wait forever. I guess that was the problem I could not solve myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants