Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

make file has changed...no more librf24-bcm

jerseyguy1996 last edited by

Re: [Tutorial] Raspberry Pi NRF24l01 direct connection
The GIT library has changed. You will need to "cd Raspberry" and then sudo git clone https://github.com/TMRh20/RF24
cd RF24 and make all and sudo make install
next cd .. and sudo make all and sudo make install
Reply Quote 0
1 Reply Last reply
hek Admin last edited by

Use git pull to fetch from upstream.
Reply Quote 0
1 Reply Last reply

2
Posts

1345
Views

Log in to reply

Suggested Topics

Contribution
General Discussion • • edoardoo

2

0
Votes

2
Posts

1246
Views

Hi @edoardoo I actually stumbled on your post a couple of weeks ago! Great writeup! We certainly need contributors. We need help with everything from the visualisation of sensordata in the frontend (considering using d3.js) to mqtt/node.js backend for receiving and processing sensor data. Please contact me or Johan for further discussions.
PiHome relay set-up
Controllers • • A Former User

2

0
Votes

2
Posts

16
Views

Hi @Prohi, can you provide more information about your heating system? When searching about AirMax on the internet, I found this: https://www.airmaxhvac.com/ and this https://airmaxsc.com/ and this https://airmaxop.com/ and ... Is your heating system an hvac based system? With remote controls for each room?
Best choise for a controller
Controllers • • dzjr

48

0
Votes

48
Posts

938
Views

@monte said in Best choise for a controller: @neverdie but isn't Docker more efficient and simple solution compared to a VM? Considering it will be used for single process anyway. Yes, I think you're right.
[Answered] Any recommended load-and-go VM or Docker images for mysensors?
Controllers • • NeverDie

17

0
Votes

17
Posts

170
Views

Naturally, using Tasmota instead of ESPHome should work equally well.
testing with different controllers (mqtt brokers)
Controllers • gateway mqtt home assistant • • OldSurferDude

2

0
Votes

2
Posts

27
Views

@OldSurferDude use a host name for the broker in the configure command (--my-controller-url-address=). Add the host name to /etc/hosts on the rpi where the gateway is. Start the MySensors gatway. When you want to switch brokers, modify /etc/hosts again and restart the MySensors gateway.
Best PC platform for running Esxi/Docker at home?
Controllers • • NeverDie

75

0
Votes

75
Posts

516
Views

@mfalkvidd said in Best PC platform for running Esxi/Docker at home?: @NeverDie ...You can also use the command line tool fstrim to manually discard unused data. Looking into this, I think checking the "Discard" box on the "Hard Disk" tab of the "Create a Virtual Machine" dialog box inside ProxMox may automatically accomplish the same thing. Also the ProxMox dataset that the VM is saved on needs to be set to thin-client. So, those two things plus the ssd emulation that you mentioned, and of course automatic file compression like lz4 needs to be enabled. So, in total, four things need to be set correctly for it to work optimally. Originally I was concerned that because, if using ZFS as the file system, ProxMox only allows storing a VM as a pre-allocated "raw" file (rather than as a qcow2 file as ProxMox would if ProMox were using a linux ext16 file system instead of ZFS) that the file would take up enormous space even if the raw file (i.e. the VM's virtual disk) is mostly empty. So, I did the experiment, and it turns out that is true if the ProxMox dataset isn't configured as "thin-client" or if automatic file compression isn't turned on, but fortunately the true size of the raw file does indeed shrink down if those two conditions are enabled. So, having proved that to myself, I'll pass on the tip: I now create a VM's disk to be as large as I can imagine it would ever need to grow, and then I let the thin-client mechanism maintain the true size of the virtual disk to be only as large as what is actually necessary. This way I don't have to worry that I created too small a VM disk, or that the VM will later outgrow the disk size that was originally allocated for it.

31
Online

11.6k
Users

11.2k
Topics

113.0k
Posts

Copyright 2019 TBD | Forum Guidelines | Privacy Policy | Terms of Service

1 / 1