Skip to content


Frequently asked questions and possible issues you may face when working with Cloud4RPi:

How to avoid an Installation Error?

You can get one of the following errors when you use the sudo pip install cloud4rpi command to install the Cloud4RPi client library:

  1. InstallationError: Command "python egg_info" failed with error code 1
  2. Error while finding spec for 'pip.__main__' (<class 'ImportError'>: cannot import name 'IncompleteRead'); 'pip' is a package and cannot be directly executed

This happens because the setuptools and/or pip packages your Python interpreter uses are outdated. Update the packages with the following command:

sudo pip install --upgrade setuptools pip

After updating, reinstall cloud4rpi:

sudo pip install cloud4rpi

Raspberry Pi does not recognize my 1-Wire device

Follow the instructions below if you experience issues with the 1-Wire interface on Raspberry Pi.

  1. Run sudo raspi-config and make sure that the 1-Wire interface is enabled (Interfacing Options | 1-Wire menu).
  2. Add the dtoverlay=w1-gpio string to your /boot/config.txt file (echo dtoverlay=w1-gpio | sudo tee -a /boot/config.txt).
  3. Reboot (sudo reboot command).
  4. Double-check the wiring and your device's operational voltage. The 1-Wire DATA bus should be connected to GPIO4 (Pin 7) and pulled-up to VCC.

How to avoid the "Insecure Platform" warning?

The InsecurePlatformWarning: A true SSLContext object is not available... notification appears when you run Cloud4RPi on a Python v2.7.9 and earlier. Use the following command to check the Python version:

python --version

You can use one of the following approaches to install the latest version.

Where are the log files?

Use one of the following commands to read the logs containing the service's output and errors:

  • less /var/log/cloud4rpi.log — if your init manager is init and you have left the service name and log path unchanged;
  • sudo journalctl -u cloud4rpi — if your init manager is systemd and you have not changed the service name.


Use the ps -p 1 command to see your operating system's init manager. Refer to your init manager's documentation for more information or contact us if it differs from init and systemd.

You can also call the following function at the beginning of your script to save the script output. It is useful if you do not run your Cloud4RPi-enabled script as a service:


How to update Cloud4RPi client installation?

The Cloud4RPi client library is a PyPI package the pip utility manages. Execute the following command to update the Cloud4RPi client library:

sudo pip install --upgrade cloud4rpi

How to use the service installed using the script?

The default service's name is cloud4rpi (can be changed in You can use the following commands if your init manager is init:

sudo service cloud4rpi start|stop|status|restart|uninstall

If your init manager is systemd, you can use the same commands except for uninstall. To remove the systemd service, execute the following commands:

sudo systemctl stop cloud4rpi.service
sudo systemctl disable cloud4rpi.service
sudo rm /lib/systemd/system/cloud4rpi.service
sudo systemctl daemon-reload

How to choose the DATA_SENDING_INTERVAL value?

You should call device.publish_data() and device.publish_diag() functions frequently to update the monitored variables. The update frequency depends on the variable dynamics, for example, atmospheric conditions do not change every minute. This means the delay between updates for a weather station should be one to ten minutes.

If you monitor several variables with different dynamics, the delay between updates should be the shortest.


The variable update interval does not affect commands, and variable changes made through the Web UI (Switch or Slider widget) are applied instantly.