jeff.cartwright.562

(I am writing this on my cell phone at my lunch break. Apologies in advance if I am not clear). The sensor is directional. Current will only flow in one direction. If it is hooked up backwards it will not work.So, I would start with a voltmeter and determine which wire on the sensor needs to be an input to your gpio pins. You should see a difference if the sensor is close to the metal bar or if it is far away. The sensor acts like an on/off switch.If I remember correctly, a resistor is required to prevent the sensor from floating and giving erratic results.Attach the sensor to your raspberry pi. Open a terminal window and run the gpio read pin command with the metal bar near and far away. This should return either a 1 or 0.Once you are certain the gpio command is reading the sensor correc…

(I am writing this on my cell phone at my lunch break. Apologies in advance if I am not clear). The sensor is directional. Current will only flow in one direction. If it is hooked up backwards it will not work.So, I would start with a voltmeter and determine which wire on the sensor needs to be an input to your gpio pins. You should see a difference if the sensor is close to the metal bar or if it is far away. The sensor acts like an on/off switch.If I remember correctly, a resistor is required to prevent the sensor from floating and giving erratic results.Attach the sensor to your raspberry pi. Open a terminal window and run the gpio read pin command with the metal bar near and far away. This should return either a 1 or 0.Once you are certain the gpio command is reading the sensor correctly, and the sensor is setup correctly, then the gpio read command can be issued from either phone or python using some type command line execution. Both languages have the ability to do this, or you can use the gpio library.If hooked up backwards the sensor can make a gpio pin stop working. If this happens try another input pin.

It has been awhile, but If I remember correctly there are add on device file libraries for fritzing. I think this was in an Adafruit supplied library that I found by googling.

Yes, you can use 5v.

See the image in Step 3. The image shows the connections as labeled on the bottom or side of the button and how those wires connect to the pi. I don't have the breadboard setup any more.

I would suggest ensuring that the pins are wired correctly first. Sometimes a pin can "burn out" if not used correctly. Any GPIO pins can be used. So, if not working try another.The GPIO commands can be run from the command line.For example, $ gpio readall shows the state of all gpio pinsHere is a more complete description of how to use the GPIO pins:http://www.embeddedpi.com/documentation/gpio/mypi-...

GET and POST are part of HTTP protocol. Yes, I am using GET within php code. I may have this confused, put from my point-of-view, I am trying to retrieve (or GET) information from a URI variable called trigger. W3Schools provides a better explanation: https://www.w3schools.com/tags/ref_httpmethods.aspThe section of php that starts with:if ($trigger == 0) {determines which image to display

Streaming video uses much less than 100Mbps (10-20Mbps per tuner). So, it wasn't the USB tuner or Ethernet not being able to handle the bit rate. In my setup, a tuner is only tuned to one channel at a time. In the US, over-the-air TV using ATSC is sent at HD resolution of 720p.My assumption was the RPI CPU couldn't keep up. However, I have no data to support that conclusion. 1 or 2 tuners worked fine, but as I added more it "broke", in that, the tv channel did not play clearly or without interruption. Moving to a higher-performing CPU resolved the issue.Yes, I have spent a lot more money on my projects than is justifiable. In general, you won't save money or time building your own system. I do it because it is fun and educational (or frustrating). I bought and returned multiple …

Streaming video uses much less than 100Mbps (10-20Mbps per tuner). So, it wasn't the USB tuner or Ethernet not being able to handle the bit rate. In my setup, a tuner is only tuned to one channel at a time. In the US, over-the-air TV using ATSC is sent at HD resolution of 720p.My assumption was the RPI CPU couldn't keep up. However, I have no data to support that conclusion. 1 or 2 tuners worked fine, but as I added more it "broke", in that, the tv channel did not play clearly or without interruption. Moving to a higher-performing CPU resolved the issue.Yes, I have spent a lot more money on my projects than is justifiable. In general, you won't save money or time building your own system. I do it because it is fun and educational (or frustrating). I bought and returned multiple tuners until settling on the 9xx. Yes, it takes a long time until your vision can be realized.

That sounds like a great Idea.Buy one and measure it. Your channels, resolution, etc. are going to drive CPU usage. My first build was on a Raspberry Pi 3B+. And the RPi could not handle 4 tuners.My Intel based desktop is unlikely to translate to a router's CPU. The hard part with tuners is finding the driver that will run on your system. I ended up talking with some very helpful people at Hauppauge.Good luck! I hope to hear how your measurements go.

So, I played around a lot with this. The easiest way is to just hook it up to 3v gpio and ground. The fan runs all the time. If you don't have a resistor, then the GPIO pins have an internal resistor, and you can try that. The reason for a resistor is all explained in step 2. I am not sure I can explain it any better by repeating the above.Are you using the transistor?If this is too complicated, then try this: https://sites.google.com/site/cartwrightraspberryp...

When I wrote this instructable 3+ years ago, I don't remember shinken being available via pypi, and I don't think pypi came installed.My pip install of shinken (Step 6) is probably causing the problems. (Run $ pip uninstall shinken)Instead of my instructions, you might want to try these instructions: https://pypi.org/project/Shinken/

... someone else was having this problemTry $ sudo shinken-2.4.3 --init

Well, something must have gone wrong.If you did Step 6 and installed shinken and it started running, then shinken is installed.My guess is some error should appear when you run this command:sudo pip install shinken This must have failed. Try it again and let me know what you see.

No, I cannot help. This is a raspberry pi project. I know nothing about arduino

I am sorry, I do not know the answer to your question. The doorbell with no circuit works because the push button closes a circuit in the garage door opener sending a small positive voltage.#1 Guess) I am not sure if doing it in parallel would work, because your circuit board may be sending more than just a momentary short. Perhaps, it is sending some type of command.#2 Guess) The circuit board may receiving signals from your remote, and the circuit board is sending the positive voltage to the garage door opener. Then it might work. To make it work, I think you would have to insert the relay connections between the circuit board and the garage door opener. You may want to insert a diode on the positive line to the circuit board so no current flows back into the board. You would want the e…

I am sorry, I do not know the answer to your question. The doorbell with no circuit works because the push button closes a circuit in the garage door opener sending a small positive voltage.#1 Guess) I am not sure if doing it in parallel would work, because your circuit board may be sending more than just a momentary short. Perhaps, it is sending some type of command.#2 Guess) The circuit board may receiving signals from your remote, and the circuit board is sending the positive voltage to the garage door opener. Then it might work. To make it work, I think you would have to insert the relay connections between the circuit board and the garage door opener. You may want to insert a diode on the positive line to the circuit board so no current flows back into the board. You would want the existing functionality to work and the new functionality. You might to try a breadboard and play around with it until all features work as desired#3 Guess) Shorting the circuit may cause an over voltage on your circuit board and cause damage to it. Then a fun DIY project turns into a nightmare.

RPi 3 B+ has built in Wi-FI and should be able to play OTA TV in another room. Some of my TVs use Kodi and Wi-Fi.I run these on Roku: Netflix, Amazon Prime, Hulu, YouTube, ... I tried many tutorials and could never get these to run on Raspberry Pi without being choppy.Only OTA TV runs on KodiThe PVR needs to be another computer fast enough to keep up with the TV tuner. The TV tuner is connected to the antenna. I could get one end to work or the other, but I could never get 2 Raspberry Pis to capture AND play OTA TV. IMO, either the PVR or the Kodi machine has to be a PC class processor. Also, the PVR needs to have a large disk drive. You can use a USB drive on an RPi, but there is a limit of 400Mbps on the RPi bus (which includes ethernet, microsd card, USB, ...).The RPi plugs into one TV…

RPi 3 B+ has built in Wi-FI and should be able to play OTA TV in another room. Some of my TVs use Kodi and Wi-Fi.I run these on Roku: Netflix, Amazon Prime, Hulu, YouTube, ... I tried many tutorials and could never get these to run on Raspberry Pi without being choppy.Only OTA TV runs on KodiThe PVR needs to be another computer fast enough to keep up with the TV tuner. The TV tuner is connected to the antenna. I could get one end to work or the other, but I could never get 2 Raspberry Pis to capture AND play OTA TV. IMO, either the PVR or the Kodi machine has to be a PC class processor. Also, the PVR needs to have a large disk drive. You can use a USB drive on an RPi, but there is a limit of 400Mbps on the RPi bus (which includes ethernet, microsd card, USB, ...).The RPi plugs into one TV using an HDMI cable. The HDMI cable can only be plugged into one TV. So, one RPi and one Roku for each TV. The TVs should have two HDMI ports.I hope this helps.

1. In my setup, each TV has a raspberry pi running kodi on osmcI have a pc running tvheadend on Ubuntu with four USB TV tuners. So, at most four TVs can be tuned to four separate TV channels. Start with one and add more as required2. The raspberry pi via kodi connects to a tuner and tells it the channel to use. If another TV tries to connect and no tuner is available, then it will show an error message like tuner not available.3. Kodi is the smart portion. It shows video on TV through HDMI cable. But sod my TVs are smart and they connect either wirelessly or via Ethernet to my LAN. I don't use smart TV features often.4. Tvheadend is the dvr. You can set and play recordings through any kodi device.5. My tvheadend pc was a gaming machine that I bought for my son. It came with a terabyte dri…

1. In my setup, each TV has a raspberry pi running kodi on osmcI have a pc running tvheadend on Ubuntu with four USB TV tuners. So, at most four TVs can be tuned to four separate TV channels. Start with one and add more as required2. The raspberry pi via kodi connects to a tuner and tells it the channel to use. If another TV tries to connect and no tuner is available, then it will show an error message like tuner not available.3. Kodi is the smart portion. It shows video on TV through HDMI cable. But sod my TVs are smart and they connect either wirelessly or via Ethernet to my LAN. I don't use smart TV features often.4. Tvheadend is the dvr. You can set and play recordings through any kodi device.5. My tvheadend pc was a gaming machine that I bought for my son. It came with a terabyte drive. He didn't want it any more and I converted it from windows to ubuntu. So, the TV headed pc acts as the Nas for all rpis.I use a Logitech harmony remote o control all devices connected to the RPi: demon, Blu-ray, kodi and roku... And gaming gear

I am interpreting your question as two questions. #1 Can I control the system remotely? Yes, but I didn't implement a lot of controls. For example, I didn't see the need to change the zones remotely. From my cell phone, I can turn the alarm on and off. And I can trigger the alarm remotely, if some other device in my home automation system is reporting something wrong (or if I just want to annoy my wife).#2 Can the system send notifications when something is wrong?Yes, the system sends a text alert when it detects an issue. The python scripts contain the code. Basically, it sends a text alert through my gmail account to my phone.

Sorry, it looks like a typo. It should be: 239.255.0.1:1234, which should be channel 1. It should come from what you added when the command was run $ sudo nano klru.cfgand add # unique-multicast-ip:port always-on pid 239.255.0.1:1234 1 3 239.255.0.2:1234 1 6If 239 works, let me know and I will fix the typo.

You are correct. I missed that.

Thank you.A1. I don't think the button has a built in resistor, but the GPIO pin does. I could have used the GPIO pin resistor. A2. My understanding is for the reset to work on the Raspberry Pi is for the circuit to be normally open. My guess for an on-off button, would be pressing opens the circuit (i.e., makes it off). So, you would want to use this in a situation where the circuit is normally complete and opening it would do something.

Sorry. I am not understanding the question. On which step did you get stuck or did things go wrong?

Thank you! This wasn't a problem in the past, but the images look like a mess now.

That is so bizarre. The steps to setup the OTA receiver are just gone. I went through the history, and there are no steps in the history either. I am not sure what happened.

I realized what I did. This is just the RPi set up. The OTA TV Tuner is setup in this instructable: https://www.instructables.com/Multicast-TV-Using-Raspberry-Pi-3-WinTV-HVR-955Q/, which refers to this instructable.

Can you check if you have the latest version of code from github? From your explanation, it seems there is a bug in the code.My design or explanation may not be the best. Basically, turning the fan on is dependent on the temperature, and turning it off is dependent on meeting a threshold temperature. However, the measurement of the temperature is not simultaneous with turning the fan on or off. There is a time delay, which allows the temperature to increase/decrease before it is reported. Depending on the application being run, the CPU can increase 20 degrees C in a few seconds. Increasing the delay may increase the size of this fluctuation.The above is why even though the fan starts at 50 it doesn't report the temperature until it is 52.6, and while it shuts off at 45 it doesn't report t…

Can you check if you have the latest version of code from github? From your explanation, it seems there is a bug in the code.My design or explanation may not be the best. Basically, turning the fan on is dependent on the temperature, and turning it off is dependent on meeting a threshold temperature. However, the measurement of the temperature is not simultaneous with turning the fan on or off. There is a time delay, which allows the temperature to increase/decrease before it is reported. Depending on the application being run, the CPU can increase 20 degrees C in a few seconds. Increasing the delay may increase the size of this fluctuation.The above is why even though the fan starts at 50 it doesn't report the temperature until it is 52.6, and while it shuts off at 45 it doesn't report the temperature until it has risen to 48.9.Of course, the CPU cannot be cooled to (50-40) 10 degrees Celsius. Try using a higher starting temperature, and 5 degrees or so cooler for a stopping temperature. A raspberry pi can operate up to about 85 degrees Celsius. You will prolong the life of a CPU if it is kept away from the maximum operating temperature. I am not sure but this project will not be effective outside an undetermined temperature range (say 50 - 85, below 50 the fan cannot cool enough and at or above 85 the fan will always be on). And I haven't spent the time to figure out the optimum temperature range, but my assumption is this depends on the application. While running Kodi, my settings work reasonably well. When I was trying to gather some data points, compute intensive applications pushed the temperature up very quickly. To do a proper analysis of the effective temperature range requires tools I do not have.The implementation is relatively simple. This link describes a much more sophisticated implementation and may meet your needs: https://www.npmjs.com/package/rpi-fan-controllerAny improvements would be appreciated.

I was unable to get Netflix to work just on a raspberry pi. I was able to get netflix to work using plex running on a PC and with a raspberry pi. IMO, that isn't really working on a raspberry pi. Right? If you got it to work, I would love to know how you did it.

did you try usr / psswd:admin, raspberry-pi-passwordand did you try restarting

The video seems to have been removed. Can you please fix?

#1 Did you try:sudo nano /etc/network/interfacesand does it look like this (its all on one line):auto lo iface lo inet loopbackbut it should look like this:auto lo iface lo inet loopbacksave and reboot. Open a browser on a PC/MacBook and enter http://♣ip-address♣:7767#2 run the unattended install script, it can find or fix most issues

I am not sure if this got to you.Can you send your code as an attached zip file?I don't think quartarian's code and mine are the same. I am sending code from my project, and I assume you are plugging it in to q's. I went back and looked at a very old version of mine.The CSS has a {display:block;width: 400px;height: 400px;padding: 0px 0 0 0;}a:active {background: url('../remote-press.jpg') top left no-repeat;}And the PHP has:<?phpif ($trigger == 0) {echo "<a href='/?trigger=1'></a>";} else {echo "<a href='/'></a>";}?>Basically, the css is changing the image in the defined html element "a".However, this probably won't work for you.I assume you got the garage door to work without the image. Is that correct?If not, the code associate…

I am not sure if this got to you.Can you send your code as an attached zip file?I don't think quartarian's code and mine are the same. I am sending code from my project, and I assume you are plugging it in to q's. I went back and looked at a very old version of mine.The CSS has a {display:block;width: 400px;height: 400px;padding: 0px 0 0 0;}a:active {background: url('../remote-press.jpg') top left no-repeat;}And the PHP has:<?phpif ($trigger == 0) {echo "<a href='/?trigger=1'></a>";} else {echo "<a href='/'></a>";}?>Basically, the css is changing the image in the defined html element "a".However, this probably won't work for you.I assume you got the garage door to work without the image. Is that correct?If not, the code associated with the trigger and the write to the gpio pin is what opens and closes the door.<?php$switch = exec('gpio read 3');if(isset($_GET['trigger']) && $_GET['trigger'] == 1) {error_reporting(E_ALL);exec('gpio write 7 0');usleep(1000000);exec('gpio write 7 1');$trigger = 1;} else {$trigger = 0;}?>

The comment editor doesn't allow php code. So, remove the quotes and spaces from "< ? php" and "? >". This is how I added the image."< ? php"if ($trigger == 0) {echo "<td colspan=\"4\" align=\"center\"><a href='/index.php?trigger=1'><img src=\"remote-background.jpg\" alt=\"garage remote\" style=\"width:50%\"></a></td>";} else {echo "<td colspan=\"4\" align=\"center\"><a href='/index.php/'><img src=\"remote-background.jpg\" alt=\"garage remote\" style=\"width:50%\"></a></td>";}"? >"

I added the step you suggested. Thank You.

1. HostnameWhen you set up the raspberry pi, you should have set the hostname. To see the hostname type:$ cat /etc/hostname shinkenwhich, assumes you set the hostname to shinken.If you want to change hostname, use:$ sudo nano /etc/hostnameand change to whatever you want. To save and exit nano editor, use CTRL-o, ENTER, CTRL-x2. Also, when you setup raspberry pi, you should have setup avahi. Avahi allows you to access by name rather than IP (my shinken IP is 192.168.1.100, yours may be different)$ sudo apt-get install avahi-daemon$ sudo nano /etc/hosts192.168.1.100 shinkenTo save and exit, use CTRL-o, ENTER, CTRL-x$ sudo /etc/init.d/hostname.sh $ sudo reboot3. Make sure gateway is setup correctly on raspberry pi$ sudo route -n If your ISP gateway doesn't show with correct address, mine is …

1. HostnameWhen you set up the raspberry pi, you should have set the hostname. To see the hostname type:$ cat /etc/hostname shinkenwhich, assumes you set the hostname to shinken.If you want to change hostname, use:$ sudo nano /etc/hostnameand change to whatever you want. To save and exit nano editor, use CTRL-o, ENTER, CTRL-x2. Also, when you setup raspberry pi, you should have setup avahi. Avahi allows you to access by name rather than IP (my shinken IP is 192.168.1.100, yours may be different)$ sudo apt-get install avahi-daemon$ sudo nano /etc/hosts192.168.1.100 shinkenTo save and exit, use CTRL-o, ENTER, CTRL-x$ sudo /etc/init.d/hostname.sh $ sudo reboot3. Make sure gateway is setup correctly on raspberry pi$ sudo route -n If your ISP gateway doesn't show with correct address, mine is 192.168.1.254$ sudo route add default gw 192.168.1.2544. AccessingIf you have already done everything above, then open a browser on laptop or PC and enter the following and remove spaces around the colon, :http : //shinken.local:7767If you don't want to use avahi, then just use the IP address of your shinken device (mine is 192.168.1.100) and remove spaces around colon:http : //192.168.1.100:7767

Yes, skip WiFi. I scanned through and the other steps should work for RPi3. Let me know if you have any issues.

Just raspberry pi.

Disconnect all pins. Put battey in geiger counter. Does geiger counter work? Geiger counter battery must be removed before connecting to raspberry pi. If geiger counter doesn't work, then you likely have a short. If geiger counter works, then ONLY connect ground and 3.3v, don't connect data pins. Measure voltage on geiger counnter between 3.3v pin and ground. What do you measure? On raspberry pi, measure voltage between ground and 5v pin. Please report what you measure.

Unplug the power from the raspberry pi.Before removing the PITFT display, check that it is properly aligned with the correct pins. If it was installed incorrectly, then you may have damaged the raspberry pi.Remove the PITFT display. You can put it back on once you have identified a working 3.3v pin.Disconnect all the jumper cables between the raspberry pi and the mighty ohm. Plug the power into the raspberry pi. Does it turn on? If no, then there is something wrong with the raspberry pi. If yes, then power off the raspberry pi and unplug the power. Do a simple test on the geiger counter. Only connect the following: - Ground: Mighty Ohm Pulse pin 1 connects to PiTFT pin 14 - 3.3v: Mighty Ohm Pulse pin 3 connects to PiTFT pin 1 Plug power back into the raspberry pi. Does the raspberry pi p…

Unplug the power from the raspberry pi.Before removing the PITFT display, check that it is properly aligned with the correct pins. If it was installed incorrectly, then you may have damaged the raspberry pi.Remove the PITFT display. You can put it back on once you have identified a working 3.3v pin.Disconnect all the jumper cables between the raspberry pi and the mighty ohm. Plug the power into the raspberry pi. Does it turn on? If no, then there is something wrong with the raspberry pi. If yes, then power off the raspberry pi and unplug the power. Do a simple test on the geiger counter. Only connect the following: - Ground: Mighty Ohm Pulse pin 1 connects to PiTFT pin 14 - 3.3v: Mighty Ohm Pulse pin 3 connects to PiTFT pin 1 Plug power back into the raspberry pi. Does the raspberry pi power up? If no, then the power supply is probably not to spec. Do not use the standard supply that comes with the pi, please use the one specified. The raspberry pi, wifi, geiger counter and display all draw power. The power supply must be adequate for all the components to work. Check if the geiger counter starts to ping. If geiger counter doesn't start pinging, then toggle sound on/off using the mighty ohm button. If yes, then something else is wrong.If no, then perhaps there is something wrong with 3.3v pin #1 on the raspberry pi. Luckily, the raspberry pi has another 3.3v pin. Repeat the above steps, but this time use 3.3v pin 17.If the 3.3v pins do not work, measure output with voltmeter. Disconnect everything and restore power to the raspberry pi. Measure voltage between ground and the 5v pin, and ground and the 3.3v pin.