Hello everyone, everything good? I really need your help, I have doubts about installing BlueOS on raspberry pi 4b. I tried to install it according to a bluerobotics guide, but when I start the raspberry pi 4b, after running some codes, a login and password are requested. I searched and found that by default this login and password are respectively “pi” and “raspberrypi”. I type the login and hit enter, when I try to type the password I can’t, because I click on the keyboard and the typing doesn’t appear on the line, only when I press enter I can type the password, but I don’t have time to finish typing, and then it appears ‘wrong password’. I would like your help with a detailed step by step on installing the software, in every way possible.
Hi @luizfelipecandido, welcome to the forum 
The default password is raspberry, not raspberrypi, but you also generally shouldn’t need to use the password because if you need terminal access you can use the web terminal (when in Pirate Mode)
after your tip, I managed to login, however, even with the login done, it does not proceed to the home screen, it is only on the screen where the lines of code are. how to solve this?Processing: IMG_20220924_122341.jpg…
BlueOS is a headless Raspberry Pi image (there is no visual interface over HDMI or VNC). It’s intended for use on vehicles that generally don’t have a screen to interact with directly, so instead its visual configuration interface is available over IP (internet protocol) via a web browser on a separate computer (or phone/tablet) with an ethernet (or shared wifi) connection to the Raspberry Pi running BlueOS.
Some functionalities are only available when the computer that’s interfacing with BlueOS is configured with a static IP address of 192.168.2.1.
thank you, you solved my problem!!
Now, is theres any solution to this problem?
this is the picture when i connect hdmi to raspberry 3.
Hi @sans, welcome to the forum
I’ve moved your comment to this post because it’s on the same topic. Please see the solution above
excuse me, do we really have to log in first to be able to access it via the webinterface?
I’ve flashed the sdcard with blueos, but I still can’t access it via web browser. I have also tried directly connecting the ethernet cable from the raspberry to my laptop (not via the tether cable) but it doesn’t work.
No - no login is required to access the web interface.
- Have you done the network configuration for your laptop?
- Note also that the first time you start BlueOS it may take a few minutes before being able to connect, because it re-sizes itself to make full use of the SD card
- If the SD card is not class 10 it can take longer
I also cannot run BlueOs on my computer. The network settings and Windows Defender firewall are all OK. When I type in 192.168.2.1 into the web browser, it does not load BlueOs. What now?
Hi @bajaMike,
192.168.2.1 is the IP address of the surface computer. You have to use 192.168.2.2 to access BlueOS, as it states in the software setup instructions:
Got it, thanks!
does this means i cannot develop any programs on the pi after installing blueos on it? how can i open the browser in pi? how can i access any pi functionality such as connecting to wifi?
Hi @axppxsky -
If you would like to use the HDMI output of the Pi after installing BlueOS on it, you are correct, this is not possible. This is a headless OS, using the Raspberry Pi as an appliance, similar to many other projects across a wide range of applications.
You can however continue to develop programs, as BlueOS has both Jupyter Notebook and VS Code extensions that allow you to develop and execute code from onboard the pi. You can also select WiFi networks, connect to them, and perform other network configuration, including installing the ZerorTier extension for remote network access. This should make using BlueOS for whatever vehicle related problem you’d like to tackle easy!
Hello, I recently bought Blueboat kit and I encountered a problem where I cannot access the IP address 192.168.2.2 – BlueBoat Raspberry Pi 4 IP address (BlueOS). The rest of the IP can be accessed.
When I enter the IP address 192.168.2.3, the last IP shows 192.168.2.4 instead of 192.168.2.2.
Did I make a mistake somewhere?
Thank you very much
Hi @hazim
Welcome to the forums.
Can you reach 192.168.2.4? This should be the BlueBoat Radio.
Have you waited a couple minuted for the Pi to start up, and heard the beep from the motors / ESCs indcatng the Pi has booted up?
If you open the main electroncs cover, is a blue light flashing on the Navigator, located on top of the Pi?
If the answer is no to both those questions, than your system isn’t booting correctly… you may need to reflash the SD card!
Thank you for the reply @tony-white ,
YES I can access IP address 192.168.2.4.
YES I did wait a couple minutes for the Pi to boot up and heard the beep sound.
It still produces the same problem where I cannot access the IP address 192.168.2.2.
Currently this is the method that I have tried:
- Reset the BlueOS IP by turning off the Raspberry Pi and restarting it without a LAN connection to force the fallback IP 192.168.2.2.
- Set a static IP on my laptop to be in the same subnet (IP 192.168.2.1, subnet mask 255.255.255.0).
- Connect the Raspberry Pi directly to the laptop using a different LAN cable to ensure there’s no issue with the cable.
- Use a router connection to find the Raspberry Pi’s IP if the IP has changed.
- Access BlueOS via HDMI and keyboard to check logs and system configuration.
- Temporarily disable the firewall on my laptop and use network scanner software to detect devices on the network.
Hi @hazim -
It’s very strange that your system boots up, but still can’t be reached at the default IP. Have you tried reaching it at blueos.local?
Is the blue light flashing on the Navigator?
What did you see when accessing with HDMI? The IP address should be displayed after boot…
Hi Tony,
I’m working together with Hazim on this system, and I will continue replying here.
We checked the WebFig interface, and the Wireless Client is assigned to 192.168.2.4 instead of 192.168.2.2, so we are not sure whether the BlueOS IP has changed or whether there is a connection issue on the Raspberry Pi side.
We have already tried accessing blueos.local, but it still doesn’t open. The browser shows this error:
This site can’t be reached
Check if there is a typo in blueos.local.
If the spelling is correct, try running Windows Network Diagnostics.
DNS_PROBE_FINISHED_NXDOMAIN
And when we try to access 192.168.2.2, the browser shows:
This site can’t be reached
192.168.2.2 took too long to respond.
Try:
– Checking the connection
– Checking the proxy and the firewall
– Running Windows Network Diagnostics
The blue light is on as shown in the attached picture. When we connect the Raspberry Pi to a monitor using HDMI, it only displays a terminal screen with a BlueOS login, but we are unable to log in.
Could you kindly advise if there are any steps we might have missed, or anything else we should do? Since I can only attach one picture per post as a new user, I’m unable to show all the components and connection setups at once.
One more question:
We did not purchase a modem or router for this setup. Could the lack of a router be the reason why we cannot access BlueOS? The set comes with an Ethernet cable, so I would like to confirm whether this cable is meant for connecting the Raspberry Pi board to a router, or if it is intended for another purpose.
Thank you, and we appreciate your guidance.
Hi @Nurul -
The WebFig interface is not relevant - however it may indicate what you’re finding by other means is true - BlueOS is not accessible via its normal web interface. Did you ever reach it, or is this happening with a new setup? I’m assuming we’re dealing with a new system here that has not been connected to your WiFi network or updated?
You could likely re-flash the SD card as mentioned if it is a new setup - if that doesn’t work the SD card may be faulty and can be replaced by contacting support (report a problem with a product.) Having your order number can speed this process up!
I see the blue lght on - but there should be an additional flashing Blue light that appeared when you heard the beep, 1-2 minutes after startup…
You do not need a modem or router - the BaseStation is creating a point to point WiFi link with the Mikrotik radio in the BlueBoat that you’re reaching ok at 192.168.2.4. I’m not sure which ethernet cable you’re referring to being included?