OpenMarine

Full Version: Second tinypilot as client
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi
I have not been able to connect my WiFi remote after new image.
Just tried the new (December). Following the instructions in the wiki I can do all steps until reboot. After changing host to 192.168.14.1 with nano and save I can go back and read the signalk.conf and it is the correct host 192.168.......
But after doing Sync and then reboot the file signalk.conf revert back to localhost as host.
how can I make The changes to stay after reboot???

Johan
It is possible another pypilot client process is running which already started with the localhost connection. If this connections succeeds on reconnect it would overwrite this file. I need to prevent this writing on a reconnect it seems.

For now either issue:
sv d pyilot
before using nano, or try editing the file on the sdcard from a reader on a different machine.
(2020-01-15, 12:25 AM)seandepagnier Wrote: [ -> ]It is possible another pypilot client process is running which already started with the localhost connection.   If this connections succeeds on reconnect it would overwrite this file.   I need to prevent this writing on a reconnect it seems.

For now either issue:
sv d pyilot
before using nano, or try editing the file on the sdcard from a reader on a different machine.

Thanks! it kind of works so now I know it possibleSmile 
using sudo sv d pypilot befor nano works when saving the conf file the remote directly connects to the main tinypilot. But after reboot file is back to localhost......

editing on a reader attached to a raspberry 4. if I use sudo nano to change the file I can save the file, but putting it back in the remote and turn it on the file is changed to localhost! 

something must be changing the signalk.conf at booting

Johan
I have written an interface to enable remote control from the lcd keypad menu for the next version.