• Content Count

  • Joined

  • Last visited

About vlad59

  • Rank
    Elite member

Recent Profile Visitors

1060 profile views
  1. For the record my cable length was over 70m (meters not centimeters)
  2. 60cm should be very safe, it should not hurt to try 3K3.
  3. @eyatsko What is the total cable length for your 6 sensors ? Do you use CAT5 / CAT6 ? 5 or 6 years ago, I tried to add 4 sensors in each of my first floor rooms (in the ceiling) -> 4 * 4 = 16 DS18B20 but it was way too much cable length (even with cat5) to have a consistent sensor read. I often had only 8 or 9 sensor available (and sometimes to whole bus disappeared). I tried lowering the pullup, it helped. I tried replacing my only pullup with 3 (and even 4) 15k (distributed along the cable) : it also helped but it was never perfect. Finally I ended up with 4 buses of 4 sensors using 4 pins and it was flawless. Less interesting for you but now I have a single ESP8266 for each room with a some i2c sensors (SI7021, ...). All my DS18B20 were donated or binned. Hope this helps
  4. @TonyMac32 Did you order directly from Nvidia ? It seems impossible to order it from Nvidia website from Europe.
  5. You'll see, you won't regret it comparing to DHT11
  6. Are you sure that DHT11 is really one wire .... As far as I remember I had to use a specific program to access it. And the reliability of this sensor is so low that they went directly to the bin.
  7. almost agree with you... I'll be keeping emmc. About USB, If I remember correctly H6 only has 1USB2 and 1USB3 so just those too would be good (no need for internal usb hubs).
  8. There is a workaround and even when run at 100% CPU for several hours without any heatsink a Banana Pi does not heat that much and is very stable .... At least I'm not interested to spend time searching a fix for that
  9. I build this Dockerfile which allow me to install all the plugins I want : https://github.com/seblucas/alpine-homeassistant/blob/master/Dockerfile But I'm using an external MQTT server, ... I'm sure I don't have all the bells and whistles of hassio but I don't need them.
  10. I'm using home-assistant. never tried hassio.
  11. I'm using Home Assistant for more than one year and if you follow the armbian installation : use a Virtualenv !!!!! or you'll be facing very painful upgrades. I switched to docker images but that's the same spirit.
  12. Just did right now, thanks for the reminder
  13. It won't help a lot but every kernel I tried starting with 4.14 had this problem (I can't remember every single one). Removing the module fixes it for me with no problems.
  14. I know it's an old thread but I just got this problem (date was in 2114) with a recent dev kernel. The symptom was strange -> my DHCP server won't give my Pine64 an IP due to the date difference. I think the patch from Samuel Holland (https://groups.google.com/forum/#!searchin/linux-sunxi/pine64$20timer|sort:date/linux-sunxi/b27QfJJroR0/tZgFFQeCBAAJ was not applied (or I did not find it) so I'll try to build a kernel with it.
  15. I can confirm that running theses lines make bluetooth work even after a reboot : root@pine64:~# echo 356 > /sys/class/gpio/export root@pine64:~# echo high > /sys/class/gpio/gpio356/direction root@pine64:~# echo 0 > /sys/class/gpio/gpio356/value && sleep 1 root@pine64:~# echo 1 > /sys/class/gpio/gpio356/value I'll clean that up and do a PR