Balena-sense no data in dashboard

  • balena CLI version: 11.17.4
  • Operating system version: Ubuntu 19.10 64 bit
  • Install method:zip

Hi, I install balenaOS on Raspberry PI zero with BME680 sensor. After the end of installation process I open dashboard and see there’s no data.
My log file from dashboard:
Balena.log (156.4 KB)

I solder that BME680 sensor by myself and I don’t know if I make it wright because it was my first time. May that will be the reason there’s no data?

Regards,
Przemek

Hi @skweresp,

Looking at the logs, it does look like the Pi zero can’t isn’t able to find the sensors. I’m assuming you’re reading the blog post on this, here. There’s a few things it might be worth checking:

  • All the contacts are soldered correctly and there aren’t any pins which aren’t soldered
  • Are the right pins on the Pi Zero being used to plug the sensor into?
  • Are you plugging the soldered sensor header directly into the Pi Zero, or using cables for it? If cables, try plugging the sensor directly into the right pins on the Pi Zero to see if this makes a different

Best regards,

Heds

Hi, thanks for answer. I’m newbie with soldering so it might be wrong. Can I check that it’s soldeBME680 sensor has any led to tell me that is working wright?
Look at my project.

!

Hi, it is a bit hard to tell whether the pins are connected well from the image. You may use magnifying glass to check them - I use one and it is very handy. The sensor seems to be connected to the right GPIO pins.

You may use the i2cdetect program to check whether the device is detected. It is part of the i2c-tools package (apt-get install -y i2c-tools).

After you get it installed in the container then you may check with i2cdetect -y 1 or i2cdetect -y 0 (I am not sure whether it is 1 or 0 on the RPi Zero). You may plug the sensor and check with i2cdetect, unplug and check again and see whether there are any differences in the address output.

Please let us know how that goes for you.

Thanks,
Zahari

PS: Also it is always handy to have a RPi 3 B+ for testing purposes (not the RPi 4, which is too new and still not completely stable).

Also you may use a multimeter to make sure the connections are alright.

Additionally I use also Raspbian for comparison when I encounter hardware related issues to isolate them more. If it works on Raspbian but not on balenaOS, then it is related to balenaOS, etc.

Hi thanks for answer. I install Raspbian and skip with that tutorial
and have that error:

pi@raspberrypi:~/bme680/examples $ python read-all.py
read-all.py - Displays temperature, pressure, humidity, and gas.

Press Ctrl+C to exit!


Traceback (most recent call last):
  File "read-all.py", line 15, in <module>
    sensor = bme680.BME680(bme680.I2C_ADDR_SECONDARY)
  File "/usr/local/lib/python2.7/dist-packages/bme680/__init__.py", line 45, in __init__
    self.chip_id = self._get_regs(constants.CHIP_ID_ADDR, 1)
  File "/usr/local/lib/python2.7/dist-packages/bme680/__init__.py", line 319, in _get_regs
    return self._i2c.read_byte_data(self.i2c_addr, register)
IOError: [Errno 121] Remote I/O error
pi@raspberrypi:~/bme680/examples $ 

I try also this:

i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
pi@raspberrypi:~ $ i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
pi@raspberrypi:~ $ i2cdetect 0
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory

First is without BME680 sensor.

I test today Pins with wiringpi and it show:

The main 8 GPIO pins  0: 7:  OK
pintest: 101: pintest: let: not found
                The 5 SPI pins 10:14:  OK
pintest: 101: pintest: let: not found
               The serial pins 15:16:  OK
pintest: 101: pintest: let: not found
                  The I2C pins  8: 9:  OK

I have another PiZero and tommorow I will solder only those 5 pins from BME680.

Edit.
OK I make IT work on raspbian on another pi zero but when I put sd card with balenaOS and login to balena cloud dashboard still shows no data. Do I have to install everything once again on that new Rpi zero?

It works now so thank You for help.

That’s great to hear. I just was reviewing this thread as an outsider for the first time, and I wanted to drop a bit of advice based on my experience with the same sensor: if you want to use the temperature sensor functionality, it may be unduly influenced by proximity to the device, and connecting it at some distance via wires will yield a more accurate reading.

At any rate, best of luck with your project!

Yes, I noticed that. I have temperature 27C now and even I buy cu radiator for pi zero processor the temperature is still 27C. I will buy wires for that project.
Thanks for help.
Regards.

Hi, yesterday my balena-sense stop working. I just turn it off and on next day. It may be my poor soldering quality?

czujniki_rough-resonance-29.11.19_16_13_02_( 0000).log (130.4 KB)

Hi, it looks like the grafana service can’t access the influx database.
Can you check on the device dashboard if all services are up and running or if there is any error message?
Additionally, can you run device diagnostics check to see if any services are restarting uncleanly/unexpectedly?
You can access the device diagnostics page from the dashboard or directly with this URL https://dashboard.balena-cloud.com/devices/DEVICE_UUID/diagnostics

Hi, every service is running on dashboard. I run diagnostics and it looks like that:

Device Health Checks

Device diagnostics
cdac750ab46af76881b9662f56ec321e_29.11.2019_21_08_12 0000.log (406.1 KB)

Supervisor State:
Current Supervisor State

{
  "api_port": 48484,
  "ip_address": "192.168.0.24",
  "os_version": "balenaOS 2.44.0+rev1",
  "supervisor_version": "10.3.7",
  "update_pending": false,
  "update_failed": false,
  "update_downloaded": false,
  "status": "Idle",
  "download_progress": null
}

Target Supervisor State:

{
  "local": {
    "name": "rough-resonance",
    "config": {
      "RESIN_RESTART": "6812745735021459",
      "RESIN_SUPERVISOR_NATIVE_LOGGER": "true",
      "RESIN_HOST_CONFIG_disable_splash": "1",
      "RESIN_HOST_CONFIG_dtparam": "\"i2c_arm=on\",\"spi=on\",\"audio=on\"",
      "RESIN_HOST_CONFIG_enable_uart": "1",
      "RESIN_HOST_CONFIG_gpu_mem": "16",
      "RESIN_SUPERVISOR_POLL_INTERVAL": "900000"
    },
    "apps": {
      "1541221": {
        "name": "Czujniki",
        "commit": "63d38b0b06b456361f74a406f1b5ae9a",
        "releaseId": 1140313,
        "services": {
          "354983": {
            "restart": "always",
            "volumes": [
              "sense-data:/data"
            ],
            "imageId": 1665630,
            "serviceName": "influxdb",
            "image": "registry2.balena-cloud.com/v2/401e23ad5f6652ecc9d01f741fc64d32@sha256:5c5a7e6e8e23833e38dc44052f522f28c30ad16185526f7e007eefe2570d6d5b",
            "running": true,
            "environment": {},
            "labels": {}
          },
          "354984": {
            "restart": "always",
            "ports": [
              "80"
            ],
            "volumes": [
              "sense-data:/data"
            ],
            "environment": {
              "GF_PATHS_PROVISIONING": "/usr/src/app/provisioning",
              "GF_SERVER_HTTP_PORT": "80",
              "GF_SESSION_PROVIDER": "memory",
              "balenasense": "1"
            },
            "imageId": 1665631,
            "serviceName": "grafana",
            "image": "registry2.balena-cloud.com/v2/ae420434d731cde2ebc6282ad1b8f95e@sha256:f1b967f826c060f3115361a19fd4c229698651990081de884a23da3e50b759a4",
            "running": true,
            "labels": {}
          },
          "354985": {
            "privileged": true,
            "restart": "always",
            "volumes": [
              "sense-data:/data"
            ],
            "imageId": 1665632,
            "serviceName": "sensor",
            "image": "registry2.balena-cloud.com/v2/7ffb8a1357d9d0e759a445f0a4f82c9f@sha256:91b72fcdfde7397260fb2f887b6c5957850171106647824d12519ce111ccaf95",
            "running": true,
            "environment": {},
            "labels": {}
          },
          "354986": {
            "restart": "always",
            "imageId": 1665633,
            "serviceName": "telegraf",
            "image": "registry2.balena-cloud.com/v2/9cc95d61ad373218d0ec3c9645c91ab3@sha256:2fb5cbf04eb125a02a8b2ec2a27158824bc353454aae11ba0ccb76e5e13493f4",
            "running": true,
            "environment": {},
            "labels": {}
          }
        },
        "volumes": {
          "sense-data": {}
        },
        "networks": {}
      }
    }
  },
  "dependent": {
    "apps": {},
    "devices": {}
  }
}

I hope that helps.
Regards.

Hi,
Can you try using the Blink function from the dashboard and confirm that the led on the RPi is indeed working?

I saw in your attached logs that you are using balenaOS 2.44.0+rev1. We recently found out a race condition in that version because of which, there is a chance that the supervisor (and the users app) does not start after a reboot. Given this, there is a chance that an extra reboot can bring the device back to a working state.

We have now removed that balenaOS version from the versions that are available in the balenaCloud dashboard, and that’s also mentioned in the device diagnostic checks that you shared.
it is suggested that you download and flash the latest version of balenaOS that is now available.

We can also take a look at the device, just grant us support access from the actions menu and send us the dashboard url of that device.

Kind regards,
Thodoris

Hi, that blink function doesn’t work on my Raspberry Pi. Today I see sometimes that error when I want to enter grafana:

My grafana link:
grafana

When I click Reboot in dashboard i see error:

Request error: tunneling socket could not be established, cause=socket hang up

Do I need to flash new balenaOS and make eveything from the begginning?
I give Grand Access for 12 hours.
Regards.

Hi there. The reason you re experiencing those issues, is that your device seems to be offline. That said, it’s worth checking the power supply and network connectivity of your device.

Hi. I delete balenaOS yesterday and install Home-Assistant to check it out. Unfortunately I can figure how to make it working on home-assistant and I will install balena-sense from begginning today.
Regards.