Posts made by Sebex

Hi all,

I'm running a Pro Mini on 1Mhz with a Si7021 sensor on 2x AA NiMh batteries (~3.6V). It all works fine for around 6hrs before it loses connection with the gateway it seems. It doesn't update anymore which results in a flatline in Home Assitant. Upon pressing the physical reset button on the Pro Mini everything goes back to normal; Temp/Hum are reported accurately every minute. The mysgw.log does not show anything strange, it just stops showing data from the specific node. I ran the Pro Mini on a steady 5V input which resulted in the exact same behaviour. Other than changing the freq. the hardware of the Pro Mini remains unchanged.

What can be the problem? How can I make sure it doesn't lose connection.

@Puneit-Thukral Will do!
After closer inspection the pins of the NodeMCU seem to be a lot bigger in size. However I am struggling to find the correct sizing of Arduino Pro Mini pins (width/thickness). The spacing between pins and length of them are easy to find but I cannot find the thickness at all. Do you have an idea?

@Puneit-Thukral cool, from what I read the pins are the same size as on Arduino's. I'll use this design to create one for myself.

@Puneit-Thukral in your screen it shows a number right?

edit: is there a method to resize uploaded pictures here?

@Puneit-Thukral haha okay I see.

Another question, your case that you use in the video snaps onto the pins perfectly it seems. Did you 3d print that yourself? I'm looking to 3D print a case for my pro mini and some other sensors that snaps in a similar way so that nothing moves around. However I'd rather copy a proven design than figuring out the tolerances myself.

@Puneit-Thukral interesting! Seems as a better option than Dupont, I'm gonna look into it.
You mention hot glueing the wires yourself as extra protection. But I imagine you can also put a layer of solder on it right?

@krabbi I have a similar issue as un4 described.
When nWake is connected on GND it works fine, when connecting to D3 (6) it stops working. I'm using the same sketch source as krabbi. Any suggestions?

Ok thnx guys, guess I'll be ordering a pro mini very soon!

@mfalkvidd thanks makes sense, eventually I will switch to NiMh. Had a look at the different cases, gives some good inspiration thanks for pointing in the right direction!

Now that I want to desolder the regulator and LED on the Nano, I just want to verify something, since the video shown is about the mini pro.

(1) Is the circled part in the image below, indeed the regulator on the Nano?
(2) On the battery powered sensor page, step 4 states to cutout the Vout pin. Why does this lower power consumption, and how can I locate this on the Nano?

@sineverba thanks, I got it working and it's up and running. Still have to desolder the led and remove the regulator, will do that later.
Regarding the BOD, what happens if I disable it? Will it run for longer as it does not shutdown? Or is any voltage below 1.8v bad for the arduino?

A bit off topic maybe, but I was wondering how the 'pros' around here make the sensor small and sturdy for Arduino's with Si7021+ 2xAA battery pack. My DuPont wires seem a bit loose, so I'm wondering whether I should solder them. And perhaps someone 3d printed a case for an Arduino+Batterypack or some sorts.

Hi Guys, I need some help on this guide.
I am running a Nano with radio and Si7021 sensor on 1Mhz to lower the required operating voltage, other than this is unmodified no desoldered led or regulators etc.. I tried running it on 2x 1.5v AA batteries connected to Vin and GND, the LED powers on but nothing else happens. When using 3 AA batteries it does send data, so apparently it needs more than 3v. How can I ensure that the setup is fine with 3V, I bought the 3V AA battery holder but I cannot seem to run it at that currently. Which steps can I take to do so? Help is appreciated.

@niclas hey man it seems to be working due to putting the version in the config file, at the right indent. So your suggestion worked after all, guess I had to wait a bit before it was recognised by HA. Thnx, problem solved

@niclas interesting, was not aware of that.
I had a quick look at my configuration file and did see something strange, within the mysensors gateways code two devices were listed. The second one is unknown to me and was misplaced in the code (indents etc.). So I fixed that. All mysensors nodes are saved in mysensors.json. I have no idea what /dev/ttyACM1 is doing here, neither is mysensors1.json anywhere to be found.
As a gateway I use a RPI, as you can see below the version is mentioned. Rebooting the HA after ordering the configuration had no visible effect.

mysensors:
  gateways: 
    - device: '192.168.178.26'
      persistence_file: 'mysensors.json'
      tcp_port: 5003
    - device: '/dev/ttyACM1'
      persistence_file: 'mysensors1.json'
  persistence: true
  version: '2.3'

Hey there!

Last weekend I got my CCS811 sensor working to measure the eCO2 and TVOC lvls. It reports the values just fine and the sensor is recognised by HA. Upon creating a UI where the values can be seen in a graph, I am getting the HA error that the sensors has no unit of measurement.

Which was true so I added the V_UNIT_PREFIX to the message, unfortunately this did not solved the error. I am not sure whether the prefix is not send correctly or that HA just can't deal with it. I presume the former and looking for any advice to ensure that it is sent correctly to the HA/controller and getting insight in my mistake. I have read about solving the issue within HA but I'd rather fix it at the core in the sketch.

Below the code, everything works fine. Hope the community can help out!

// Enable debug prints
#define MY_DEBUG

// Enable and select radio type attached 
#define MY_RADIO_RF24


// Include libraries
#include <MySensors.h>
#include "Adafruit_CCS811.h"
#include <SI7021.h>


static Adafruit_CCS811 ccs;
#define CHILD_ID_eCO2  0
#define CHILD_ID_TVOC 1


// Sleep time between sensor updates (in milliseconds)
static const uint64_t UPDATE_INTERVAL = 10000;

void presentation()  
{ 
  // Send the sketch info to the gateway
  sendSketchInfo("eCO2, TVOC", "0.02");

  // Present sensors as children to gateway
  present(CHILD_ID_eCO2, S_AIR_QUALITY, "eCO2");
  present(CHILD_ID_TVOC, S_AIR_QUALITY, "TVOC");


}

void setup() 
{ 
  while (not ccs.begin())
  {
    Serial.println(F("Sensor not detected!"));
    delay(5000);
  }
  Serial.println("CCS811 test");

 
}

void loop() {
  if(ccs.available()){
    if(!ccs.readData()){
    // Read temperature & humidity from sensor.
    const float eCO2 = float(ccs.geteCO2());
    const float TVOC = float(ccs.getTVOC());
    
    Serial.print("CO2: ");
    Serial.print(eCO2,0);
    Serial.print("ppm, TVOC: ");
    Serial.print(TVOC,0);
    Serial.println("ppb");

    static MyMessage msgeCO2(CHILD_ID_eCO2,  V_LEVEL);
    static MyMessage msgeCO2Prefix(CHILD_ID_eCO2, V_UNIT_PREFIX);
    static MyMessage msgTVOC(CHILD_ID_TVOC, V_LEVEL);  
    static MyMessage msgTVOCPrefix(CHILD_ID_TVOC, V_UNIT_PREFIX);     

    send(msgeCO2.set(eCO2, 0)); //1 decimal
    send(msgeCO2Prefix.set("ppm"));
    send(msgTVOC.set(TVOC, 0));
    send(msgTVOCPrefix.set("ppb"));
        
    }
    else{
      Serial.println("ERROR!");
      while(1);
    }
  }

  // Sleep until next update to save energy
  sleep(UPDATE_INTERVAL); 
}

@NeverDie could you share your Honeywell code, I have trouble getting it to work. An example will help me a lot t learn from!

@mfalkvidd thanks, I was wrongly under the impression that sudo mysgw would show the logs but it creates a second instance. Thanks for helping !

@nekitoss very helpful and clear post regarding battery powering!
I have Atmega328 16mhz, is it possible to change the 16 to 8mhz so that it can be powered by two AA batteries?

I'm getting a bad file descriptor error, any advice? Seems only 1 instance to be running.

pi@raspberrypi:~ $ sudo mysgw
Mar 19 20:14:04 INFO  Starting gateway...
Mar 19 20:14:04 INFO  Protocol version - 2.3.2
Mar 19 20:14:04 DEBUG MCO:BGN:INIT GW,CP=RNNGL---,FQ=NA,REL=255,VER=2.3.2
Mar 19 20:14:04 DEBUG TSF:LRT:OK
Mar 19 20:14:04 DEBUG TSM:INIT
Mar 19 20:14:04 DEBUG TSF:WUR:MS=0
Mar 19 20:14:04 DEBUG TSM:INIT:TSP OK
Mar 19 20:14:04 DEBUG TSM:INIT:GW MODE
Mar 19 20:14:04 DEBUG TSM:READY:ID=0,PAR=0,DIS=0
Mar 19 20:14:04 DEBUG MCO:REG:NOT NEEDED
Mar 19 20:14:04 ERROR bind: Address already in use
Mar 19 20:14:04 ERROR Failed to bind!
Mar 19 20:14:04 DEBUG MCO:BGN:STP
Mar 19 20:14:04 DEBUG MCO:BGN:INIT OK,TSP=1
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 DEBUG TSM:READY:NWD REQ
Mar 19 20:14:04 DEBUG ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor
Mar 19 20:14:04 ERROR accept: Bad file descriptor

Here I am again, I had a second node running and tried to make it battery powered but it doesn't seem to work on battery only. Anyway along the process of finding out what the problem is I encountered two other problems:

• I'm getting a ERROR accept: Bad file descriptor in mysgw, only 1 instance seems to be running though:

Any suggestions on this?

  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:05 /sbin/init
    2 ?        S      0:00 [kthreadd]
    3 ?        I<     0:00 [rcu_gp]
    4 ?        I<     0:00 [rcu_par_gp]
    8 ?        I<     0:00 [mm_percpu_wq]
    9 ?        S      0:00 [ksoftirqd/0]
   10 ?        I      0:05 [rcu_sched]
   11 ?        I      0:00 [rcu_bh]
   12 ?        S      0:00 [migration/0]
   13 ?        S      0:00 [cpuhp/0]
   14 ?        S      0:00 [cpuhp/1]
   15 ?        S      0:00 [migration/1]
   16 ?        S      0:00 [ksoftirqd/1]
   17 ?        I      0:00 [kworker/1:0-mm_percpu_wq]
   19 ?        S      0:00 [cpuhp/2]
   20 ?        S      0:00 [migration/2]
   21 ?        S      0:00 [ksoftirqd/2]
   23 ?        I<     0:00 [kworker/2:0H-kblockd]
   24 ?        S      0:00 [cpuhp/3]
   25 ?        S      0:00 [migration/3]
   26 ?        S      0:00 [ksoftirqd/3]
   29 ?        S      0:00 [kdevtmpfs]
   30 ?        I<     0:00 [netns]
   33 ?        I      0:00 [kworker/2:1-mm_percpu_wq]
   34 ?        S      0:00 [khungtaskd]
   35 ?        S      0:00 [oom_reaper]
   36 ?        I<     0:00 [writeback]
   37 ?        S      0:00 [kcompactd0]
   38 ?        I<     0:00 [crypto]
   39 ?        I<     0:00 [kblockd]
   40 ?        S      0:00 [watchdogd]
   42 ?        I<     0:00 [rpciod]
   43 ?        I<     0:00 [kworker/u9:0-hci0]
   44 ?        I<     0:00 [xprtiod]
   47 ?        S      0:00 [kswapd0]
   48 ?        I<     0:00 [nfsiod]
   59 ?        I<     0:00 [kthrotld]
   60 ?        I<     0:00 [iscsi_eh]
   61 ?        I<     0:00 [dwc_otg]
   62 ?        I<     0:00 [DWC Notificatio]
   63 ?        S<     0:04 [vchiq-slot/0]
   64 ?        S<     0:01 [vchiq-recy/0]
   65 ?        S<     0:00 [vchiq-sync/0]
   66 ?        S      0:00 [vchiq-keep/0]
   67 ?        S<     0:00 [SMIO]
   69 ?        S      0:00 [irq/86-mmc1]
   71 ?        I<     0:00 [mmc_complete]
   74 ?        I<     0:01 [kworker/0:1H-mmc_complete]
   75 ?        I<     0:00 [kworker/1:1H-kblockd]
   76 ?        S      0:00 [jbd2/mmcblk0p2-]
   77 ?        I<     0:00 [ext4-rsv-conver]
   79 ?        I<     0:00 [ipv6_addrconf]
   96 ?        I<     0:00 [kworker/3:2H-kblockd]
  101 ?        S      0:00 [irq/166-usb-001]
  114 ?        Ss     0:01 /lib/systemd/systemd-journald
  144 ?        Ss     0:01 /lib/systemd/systemd-udevd
  159 ?        S<     0:00 [SMIO]
  181 ?        I<     0:00 [mmal-vchiq]
  183 ?        I<     0:00 [mmal-vchiq]
  185 ?        I<     0:00 [mmal-vchiq]
  198 ?        I<     0:00 [cfg80211]
  202 ?        I<     0:00 [brcmf_wq/mmc1:0]
  203 ?        S      0:00 [brcmf_wdog/mmc1]
  247 ?        Ssl    0:00 /lib/systemd/systemd-timesyncd
  290 ?        Ss     0:55 /usr/local/bin/mysgw -q
  295 ?        Ss     0:00 /usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --deviceglob /dev/input/ev
  297 ?        Ss     0:00 /usr/sbin/cron -f
  298 ?        Ss     0:01 avahi-daemon: running [raspberrypi.local]
  299 ?        Ss     0:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
  303 ?        Ssl    0:00 /usr/sbin/rsyslogd -n -iNONE
  311 ?        Ss     0:00 /lib/systemd/systemd-logind
  315 ?        SNs    0:00 /usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon
  319 ?        Ss     0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
  344 ?        SLsl   0:00 /usr/sbin/rngd -r /dev/hwrng
  356 ?        S      0:00 avahi-daemon: chroot helper
  395 ?        I      0:00 [kworker/2:3-mm_percpu_wq]
  456 ?        Ss     0:00 /sbin/dhcpcd -q -w
  461 ?        Ss     0:01 /usr/sbin/nmbd --foreground --no-process-group
  463 ?        Ssl    0:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
  466 ?        Ssl    0:02 /usr/bin/containerd
  467 ?        Ssl    0:11 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
  468 tty1     Ss+    0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux
  469 ?        Ss     0:00 /usr/sbin/sshd -D
  479 ?        S      0:00 /usr/bin/hciattach /dev/serial1 bcm43xx 3000000 flow - b8:27:eb:d7:7e:1b
  481 ?        I<     0:00 [kworker/u9:2-hci0]
  483 ?        Ss     0:00 /usr/lib/bluetooth/bluetoothd
  489 ?        Ss     0:00 sshd: pi [priv]
  511 ?        Ss     0:01 /lib/systemd/systemd --user
  514 ?        S      0:00 (sd-pam)
  525 ?        Ss     0:00 /usr/sbin/smbd --foreground --no-process-group
  536 ?        R      0:03 sshd: pi@pts/0
  539 pts/0    Ss     0:01 -bash
  542 ?        S      0:00 /usr/sbin/smbd --foreground --no-process-group
  543 ?        S      0:00 /usr/sbin/smbd --foreground --no-process-group
  552 ?        S      0:00 /usr/sbin/smbd --foreground --no-process-group
  794 ?        Ss     0:00 /bin/sh /usr/sbin/hassio-supervisor
  821 ?        Sl     0:01 docker start --attach hassio_supervisor
  873 ?        Sl     0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/af8bfda572398f9806ba54d
  890 ?        Ss     0:00 s6-svscan -t0 /var/run/s6/services
 1045 ?        S      0:00 s6-supervise s6-fdholderd
 1192 ?        Ss     0:00 udevd --daemon
 1267 ?        S      0:00 s6-supervise supervisor
 1271 ?        Ssl    0:17 python3 -m supervisor
 1354 ?        S      0:00 socat UDP-RECVFROM:53,fork UDP-SENDTO:172.30.32.3:53
 1398 ?        Sl     0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/21403e3385d0ce05418df7e
 1409 ?        Sl     0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/2b6193b6744b35b8d848671
 1433 ?        Ssl    0:01 coredns -conf /config/corefile
 1437 ?        Ss     0:00 s6-svscan -t0 /var/run/s6/services
 1625 ?        S      0:00 s6-supervise s6-fdholderd
 1919 ?        Ss     0:00 udevd --daemon
 1951 ?        S      0:00 s6-supervise bridge
 1952 ?        S      0:00 s6-supervise pulseaudio
 1955 ?        Ss     0:00 socat UNIX-LISTEN:/data/external/pulse.sock,fork,unlink-early,mode=777 UNIX-CONNECT:/data/internal/pulse.sock
 1956 ?        S<sl   0:05 pulseaudio --system -vvv
 2004 ?        Sl     0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/00ef0f54f7a780be3af62a1
 2019 ?        Ssl    2:07 /usr/local/bin/python3 -m homeassistant --config /config
 2036 ?        Ss     0:01 udevd --daemon
 2353 ?        Sl     0:00 containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/9ca754987ee52a3a48c5290
 2369 ?        Ss     0:00 /sbin/docker-init -- /init /run.sh
 2462 ?        S      0:00 s6-svscan -t0 /var/run/s6/services
 2487 ?        S      0:00 foreground  if   /etc/s6/init/init-stage2-redirfd   foreground    if     if      s6-echo      -n      --      [s6-init] 
 2488 ?        S      0:00 s6-supervise s6-fdholderd
 2499 ?        S      0:00 foreground  s6-setsid  -gq  --  with-contenv  backtick  -D  0  -n  S6_LOGGING   printcontenv   S6_LOGGING    importas  S
 2632 ?        S      0:02 /usr/local/bin/python /usr/local/bin/hass-configurator /etc/configurator.conf
 2677 ?        S      0:02 /usr/sbin/smbd --foreground --no-process-group
 2837 ?        I<     0:00 [kworker/1:2H]
 2854 pts/0    T      0:00 sudo nano mysensors.conf
 2859 pts/0    T      0:00 nano mysensors.conf
 2903 ?        I      0:00 [kworker/u8:2-events_unbound]
 2937 ?        I<     0:00 [kworker/3:0H]
 2939 ?        I      0:00 [kworker/3:2-mm_percpu_wq]
 2968 ?        I      0:00 [kworker/1:2-events]
 3008 ?        I      0:00 [kworker/u8:0-events_unbound]
 3021 ?        I<     0:00 [kworker/0:2H]
 3022 ?        I      0:00 [kworker/0:0-events]
 3036 ?        I      0:00 [kworker/3:0-events]
 3037 ?        I<     0:00 [kworker/2:2H]
 3043 ?        I      0:00 [kworker/0:1-events_power_efficient]
 3068 ?        I      0:00 [kworker/u8:1-events_unbound]
 3070 ?        I      0:00 [kworker/2:0-mm_percpu_wq]
 3071 ?        I<     0:00 [kworker/3:1H-kblockd]
 3074 ?        I<     0:00 [kworker/0:0H]
 3075 ?        I      0:00 [kworker/3:1-events]
 3076 pts/0    R+     0:00 ps -ax

Yea that solved it, I copied the file in the library. Thanks!

Hi, when making this sensor battery powered (and thus enabling "#define REPORT_BATTERY_LEVEL"), I get the verification error of "Vcc.h: No such file or directory". How can I solve this?

@monte man you're 100% right. Now that I have connected external screen/keyboard, it actually reports the low voltage quite regularly in cmd line... I've ordered one and should solve the issue

@monte good idea I'll try that.

Regarding IPv6, there's no particular reason and I haven't noticed actually. I have been using ssh pi@raspberrypi.local to login, I can also connect directly to the IPv4 address. You think that can resolve it?

@monte I had tried that one before, but know that it's useful to restore the file doesn't seem to work and I get an error. Perhaps bad luck, will have to try again.

In the meantime while reinstating HA I'm facing quite some difficulties in getting HA to install within docker via link. I'm facing a broken pipe quite often and have no idea how to fix this, tried different ssh settings but when installing HA it seems to get stuck at

pi@raspberrypi:~ $ sudo su
root@raspberrypi:/home/pi# curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s -- -m raspberrypi3
[Warning] No NetworkManager support on host.
[Info] Install supervisor Docker container
packet_write_wait: Connection to fe80::233b:33dc:8d3e:eb75%en0 port 22: Broken pipe

Yesterday it did pass but then hassio had troubles successfully launching. It got the below error in the logs, not sure what caused it.
error /usr/share/www/manifest.json

Now trying to install hassio again, any suggestions are welcome. I'm going to try a different SD card and wifi connection instead of ethernet.

@monte thanks it worked using Samba. I use ssh from my mac. I also found the copied folder that I tried to copy with scp

I tried pulling a new version but that didn't seem to work so easily. It seems to get stuck on initialising after which it shuts down and tries again. The logs show the error below, it's missing a file/directory. Not sure how to solve this.

2020/01/23 17:13:08 [error] 7#7: *1 open() "/usr/share/www/api/websocket" failed (2: No such file or directory), client: ::ffff:192.168.178.16, server: , request: "GET /api/websocket HTTP/1.1", host: "192.168.178.27:8123"
2020/01/23 17:13:15 [error] 7#7: *3 open() "/usr/share/www/api/websocket" failed (2: No such file or directory), client: ::ffff:192.168.178.16, server: , request: "GET /api/websocket HTTP/1.1", host: "192.168.178.27:8123"
2020/01/23 17:13:21 [error] 7#7: *4 open() "/usr/share/www/api/websocket" failed (2: No such file or directory), client: ::ffff:192.168.178.16, server: , request: "GET /api/websocket HTTP/1.1", host: "192.168.178.27:8123"

What I did to update the container is stop all running containers, and remove images, and re-execute the cmd for homeassistant again. Was this the way to go?

Also is there a way to copy the RPi settings? I quite often get a broken pipe and not sure what's causing it. I am thinking about reflashing the SD and reinstating the settings.

@Nca78 said in Particle Powered Air Quality Sensor Logging to Google Docs:

@Sebex said in Particle Powered Air Quality Sensor Logging to Google Docs:

Perhaps I don't necessarily need to use the same pins

Both the sensors you quote are using I2C. So they both use the same 2 pins (SDA, SCL) to communicate. You can put many I2C sensors on those same pins, they each have an address to know which sensor is receiving/sending data to the master (here, your arduino).
Look for a tutorial on I2C first.

Thanks I get it now

@monte can you copy this over ssh? tried using scp -r, which seemed to work but can't find the downloaded files somehow.
And in regard of updating HA(within UI I see that and update is available). I can just stop the container and run a new updated version right, without it affecting config files?

Furthermore I wondered about HA speed, if I want to look at the history of a sensors it takes quite a while to poll the data and create a graph. Is this subsequent to HA/rpi or can the performance be improved somehow?

@monte, I'm seeing that a HA update is available. Since I'm using HA via docker the following applies to update.
$ sudo docker pull homeassistant/home-assistant:latest
To be on the safe side I'd like to backup my HA and/or RPi first to prevent me from losing all my settings. In your experience what's the most convenient for doing this. I did make a clone from the sd card a few weeks ago but it's not the most labour efficient method, do you make regular backups?

@jaredwolff thanks. I noticed that for the CSS811 there's no mysensor sketch example, any suggestions for a good guide to build one myself?

Something else I wondered is adding multiple sensors to 1 pin. I want to combine the CCS811 with the Si7021 that I am running now on an Arduino. Perhaps I don't necessarily need to use the same pins but lets say you have running X amount of sensors that it becomes inevitable to use a similar pin. Is it possible to share pins in arduino sketches, if so how does this work? Or is every value sent by the sensor tagged. Couldn't find the answer anywhere on the forum.

@monte seems to do the trick thanks again!!

Ok so I am experiencing node loss. After a while my sensor node is not recognized anymore by the gateway/mothernode. It seems to be related to the persistence file that is not accessible although the user account should have the correct rights, not sure how to verify. See HA dev logs below.

Developer Tools
Permission denied when writing to /config/home/pi/.homeassistant/mysensors.json
10:13 PM /usr/local/lib/python3.7/site-packages/mysensors/persistence.py (ERROR) - message first occurred at 10:06 PM and shows up 42 times
Node 1 is unknown
10:11 PM __main__.py (WARNING) - message first occurred at 10:06 PM and shows up 116 times
Failed to load sensors from file: home/pi/.homeassistant/mysensors.json
10:06 PM /usr/local/lib/python3.7/site-packages/mysensors/persistence.py (WARNING)
File does not exist or is not readable: home/pi/.homeassistant/mysensors.json.bak
10:06 PM /usr/local/lib/python3.7/site-packages/mysensors/persistence.py (WARNING)
Trying backup file: home/pi/.homeassistant/mysensors.json.bak
10:06 PM /usr/local/lib/python3.7/site-packages/mysensors/persistence.py (WARNING)
File does not exist or is not readable: home/pi/.homeassistant/mysensors.json
10:06 PM /usr/local/lib/python3.7/site-packages/mysensors/persistence.py (WARNING)```

# MySensors gateway
mysensors:
 gateways: 
  - device: '192.168.178.27'
    persistence_file: 'home/pi/.homeassistant/mysensors.json'
    tcp_port: 5003
 persistence: true  

logger:
  default: info
  logs:
    homeassistant.components.mysensors: debug
    mysensors: debug

@drock1985 saw your post in another thread related to this, do you have a suggestion?

So @jaredwolff & @FotoFieber what sensor would you suggest to use for measuring air quality using an Arduino (nano/uno), with the option to make it battery powered in the future. From my understanding this will remove the BME from the list due to memory/computing requirements. What are your suggestions?

@monte ah smart makes sense and probably looks most neat as well. Thanks!

@monte ok it seems to work. Temp/humidity sensor is recognised by HA and data is getting through so looks good! Only connection isnt stable which is most likely due to that I still need to get capacitors for the NRF24L01+ on both ends, and need to solder the cables to the sensor. So still some tweaks to do but happy that it works, thanks for the support @monte

Two general questions, any advice for which capacitor to select? Apart from 4.7 or 47uF, there's different types. Tanto, elco, bipolaire etc.
Furthermore I wondered why the 64bit hassio software didn't work on my Arduino, while it is a 64bit RPi 3+. Does Raspbian (or dockers?) as default run in 32?

@monte ok thanks, will take it into account.
Out of curiousity, since MQTT takes additional setup what''s the benefit of using MQTT? Do you know?

Ok so homeassistant is running and not crashing Now building the gateway, @monte to eventually communicate with hass.io do I need to select the gateway as --my-gateway=ethernet or mqtt?

@monte yea it made me wonder as well whether I should have selected the rpi 3 64bit version for docker image.
I have a Raspberry pi 3 b+ (so 64bit).
uname -m shows armv7l, when googling I got the answer that this can also be due to that Raspbian is running in 32 mode?

I tried running the script without -m MY_MACHINE returns an error for setting the machine.

root@banana:/home/pi# sudo curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s
ModemManager.service enabled
[Warning] ModemManager service is enabled. This might cause issue when using serial devices.
[ERROR] Please set machine for armv7l

I've just completely reflashed my Pi and used a different microsd card (couldn't format the original one anymore). Reinstalled raspbian, docker and hass.io. For the latter I selected raspberrpi3 (instead of rpi3-64). After accessing localip:8123 it seems that hass.io is accessible It's currently preparing so looking good!!

@monte yes tried rebooting it several times and also reinstalled but no changes so far, it still crashes.

I tried your commands, after sudo docker start homeassistant it immediately crashes according to the logs below.

CONTAINER ID        IMAGE                                                 COMMAND                  CREATED             STATUS                     PORTS               NAMES
0b0ffff70832        homeassistant/armv7-hassio-dns:1                      "coredns -conf /conf…"   5 minutes ago       Up 5 minutes                                   hassio_dns
3b83e6f9db07        homeassistant/raspberrypi3-64-homeassistant:0.103.5   "/bin/entry.sh pytho…"   2 hours ago         Exited (1) 2 seconds ago                       homeassistant
9fd90364c61f        homeassistant/armv7-hassio-supervisor  

sudo docker logs homeassistant
[FATAL tini (6)] exec /bin/entry.sh failed: Exec format error
[FATAL tini (6)] exec /bin/entry.sh failed: Exec format error

Thanks for the help so far @monte hope we can fix it

@monte said in Raspberry Pi gateway + hass.io + MQTT + MySensors:

@Sebex what exactly did you do? Did you use install script, or followed some guide on mentioned forum thread.
To see if supervisor is running execute sudo systemctl status hassio-supervisor.service
Also you can use sudo docker ps command to list running docker containers, sudo docker ps -a will show every container even if it is stopped.

I followed your github link, and used the cmd below to instal hassio.

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s -- -m MY_MACHINE

When I run your suggested status cmd I indeed see that hassio is running:

Dec 29 23:18:24 banana hassio-supervisor[1046]: 19-12-29 22:18:24 INFO (MainThread) [__main__] Run Hass.io
Dec 29 23:18:24 banana hassio-supervisor[1046]: 19-12-29 22:18:24 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
Dec 29 23:18:24 banana hassio-supervisor[1046]: 19-12-29 22:18:24 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
Dec 29 23:18:24 banana hassio-supervisor[1046]: 19-12-29 22:18:24 INFO (MainThread) [hassio.addons] Phase 'system' start 0 add-ons
Dec 29 23:18:24 banana hassio-supervisor[1046]: 19-12-29 22:18:24 INFO (MainThread) [hassio.addons] Phase 'services' start 0 add-ons
Dec 29 23:18:24 banana hassio-supervisor[1046]: 19-12-29 22:18:24 INFO (SyncWorker_1) [hassio.docker.interface] Start homeassistant/raspberrypi3-64-homeassistant
Dec 29 23:18:33 banana hassio-supervisor[1046]: 19-12-29 22:18:33 ERROR (MainThread) [hassio.homeassistant] Home Assistant has crashed!
Dec 29 23:18:33 banana hassio-supervisor[1046]: 19-12-29 22:18:33 INFO (MainThread) [hassio.addons] Phase 'application' start 0 add-ons
Dec 29 23:18:33 banana hassio-supervisor[1046]: 19-12-29 22:18:33 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
Dec 29 23:18:33 banana hassio-supervisor[1046]: 19-12-29 22:18:33 INFO (MainThread) [hassio.core] Hass.io is up and running

But I tried accessing hassio multiple times via <raspberrypi local ipadres>:8123, which is unresponsive. Any suggestions? The Pi is connected via wifi, ip adres is not yet static but doubt that this is the cause.

-- update

Now that I am looking into it again after setting Pi's IP to static, the bottom 4th line shows an error. Home assistant has crashed. So something is going wrong...

@michał-szura here and there I do read the possibility of a Pi acting as a gateway and controller. But you mention that it is not possible whatsoever? Why not?

@Dave-Myers I agree that it is not possible via HassOS, but it should be possible when run via a virtual enivroment as monte suggested.

@monte hassio now shows up in docker as a container. But I am struggling to run it, what's the command to run hassio_supervisor? attach hassio_supervisor causes it to become unresponsive.

@monte does docker allow complete functionality of hass.io? Here it's mentioned that docker will limit functionality, is that correct? For clarification, how would docker relate to a manual installation of hass.io

Thanks @monte, I'm gonna try that first

So I successfully installed hass.io and enabled MQTT on my raspberry Pi 3+ (64) but now I am struggling to get a gateway running on the raspberry while I have read on multiple places that it should be possible, acting as a gateway and controller. Overall I am a bit lost in which step is next. Should I enable MySensor in hass.io or ensure that the Raspberry Pi becomes a gateway first? Or is this exactly the same thing.

I need some guidance in getting to the next step, any advise is welcome.

For context:
My first step is to create a sensor that measures humidity and temp. connected to an arduino which sends the data via NRF24L01 to my Raspberry.

@crankycoder Any advice on how? HA is running on my raspberry Pi and I can access it just fine. How can I make it a gateway as well? The first step is to log in to my raspberry but I can only log in via HA. Any advice?

@alexc I can't help you but I do have a question. What steps did you take to make the raspberry the serial gateway and run hass.io on the same time. To run hassio you need to flash the raspberry sd card right?

Beginner here and I am gathering a list of parts to buy, the NRF24L01+ module is one of those. While browsing for buying advise I came across this, old but relevant, threads. Is there a list of verified vendors? As a beginner I want to minimise my variables early on so hope some one can help me. Couldn't find another thread that covers this question.

@nca78 appreciate the elaborate answer, thanks!
Regarding NDIR sensors, how frequent do they need to be recalibrated to maintain accuracy?

@rejoe2 thanks for the answers, really helpful! I'll give a go on the CO2 search, I will prevent making this a new thread regarding that question.

@HJ_SK yea makes sense to test it individually first and reduce variables. Regarding the 1 gateway, you mean stay away from home automation at first?

Hi all, I am very much a MySensor noob and hope some of you could help me out! Recently I have become really enthusiastic about home automation and the possibility of creating sensors to measure air quality in different indoor rooms. Since the holidays are around the corner it's a good time for to gather a list of the materials I need to start the project I have in mind and I hope some of you can provide me advise.

On the short term I want to use Home Automation to measure the air quality in different rooms and report on it, in the future the scope will expand to actual automation but for now I want to measure the air and report on it. Currently my scope would be to create wireless sensors that measure temperature, CO2 and humidity.

I came across the /iot link to create the wireless sensors but still have some unclarity as creating the sensors is a bit more complicated than setting up the Raspberry Pi. Below some Qs I have.

• Uno vs Nano. Is the Arduino Uno best for testing but the nano best for eventual deployment?

Temperature sensor
DS18b20 Dallas Temperature Sensors Module or DS18B20 Dallas Temperature Sensors. What's the benefit of just the sensor, since it's more expensive per piece in the end.

Humidity Sensor
Si7021 Sensor Module 3.3V vs 5V. What's the benefit of choosing different voltage?

CO2 sensor
Any idea's? Could not find a sensor on the build part of the website.

Wireless sensor
Quite some choice here as well it seems. Before browsing I personally was thinking to try and create zigbee sensor, in order to create a meshnetwork. Is this a possibility or a very stupid idea?

To my understanding so far, the Arduino board powers the attached sensors and wireless module. How long would an arduino with 3 sensors + wireless module last realistically. I know it will depend on polling etc, but just to get an idea.