vlad59

Members
  • Content Count

    154
  • Joined

  • Last visited

About vlad59

  • Rank
    Elite member

Recent Profile Visitors

945 profile views
  1. vlad59

    OPi Zero - 1 Wire DHT11 not detected

    You'll see, you won't regret it comparing to DHT11
  2. vlad59

    OPi Zero - 1 Wire DHT11 not detected

    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.
  3. vlad59

    Orangepi 3 h6 allwiner chip

    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).
  4. vlad59

    K-worker problem on A20 based boards

    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
  5. vlad59

    Home assistant

    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.
  6. vlad59

    Home assistant

    I'm using home-assistant. never tried hassio.
  7. vlad59

    Home assistant

    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.
  8. Just did right now, thanks for the reminder
  9. vlad59

    K-worker problem on A20 based boards

    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.
  10. 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.
  11. vlad59

    RTL8723BS Bluetooth

    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
  12. vlad59

    RTL8723BS Bluetooth

    Thanks all, indeed I was not clear at all. I'll update the script to use gpio356 and try to provide a patch soon
  13. vlad59

    RTL8723BS Bluetooth

    Think I found it : https://github.com/Miouyouyou/MyyQi/issues/7#issuecomment-388589883 The script is there : https://github.com/Miouyouyou/tinkerboard_rtl8723bs/blob/master/reset_bt_through_gpio.sh I'll try that monday after lunch, I forgot my Pine64 at work
  14. vlad59

    RTL8723BS Bluetooth

    @TonyMac32 Thanks will look for that then, thanks a lot
  15. vlad59

    RTL8723BS Bluetooth

    @Raffa As I said your method works fine on my Pine64 but only after the first poweron -> if I reboot (typing reboot on the console) then rtk_hciattach fail after 99 tries. Do you have the same problem with your Orange Pi Prime ?