jeff.cartwright.562

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.

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/id/Multicast-TV-Using-Raspberry-Pi-3-WinTV-HVR-955Q/, which refers to this instructable.

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.

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

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 associa...

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 i...

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

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.

I am a bit insane. Before I start on an instructable, I make a list of my requirements and then do a search for all possible solutions. Some solutions I throw out before I get too deep because they don't meet my requirements. Of those solutions remaining, I try to implement each one to some level. I'll start a draft instructable for each solution, and then at some point give up on it because it is more problematic than helpful. I then move on to the next one. I am sorry that OpenHab is not working for you.I found that OpenHab was confusing to install and get running, which is why I wrote the instructable. However, OpenHab meets my requirements and seems to be the most extensible home automation solution and works with my other home automation stuff: garage door opener, security system, ...

I am a bit insane. Before I start on an instructable, I make a list of my requirements and then do a search for all possible solutions. Some solutions I throw out before I get too deep because they don't meet my requirements. Of those solutions remaining, I try to implement each one to some level. I'll start a draft instructable for each solution, and then at some point give up on it because it is more problematic than helpful. I then move on to the next one. I am sorry that OpenHab is not working for you.I found that OpenHab was confusing to install and get running, which is why I wrote the instructable. However, OpenHab meets my requirements and seems to be the most extensible home automation solution and works with my other home automation stuff: garage door opener, security system, Ring, Nest, OpenSprinkler, Echo, etc. I haven't done lights yet. Yes, I agree there are issues. At about 2am one night, my garage door opened and then the security alarm went off when the door between the house and garage was apparently opened. However, I am still not sure what happened. Because my dog and I were up pretty quick and outside, but there was no one around. Did someone actually try to break in, or did something just go wrong in the code? I've put in some safeguards to prevent cached commands from being executed at unexpected times, and some more messages to log events if it happens again.There are many other DIY solutions. And, if you want to try off-the-shelf, I lean towards Samsung's SmartThings Home Automation Hub.

There is typo in this line (it should be openhab):sudo chown -R pi:pi /opt/opanhab/Explains the permission denied, and the issue in the first part. Running the UAI script would avoid things like this.

From your posts, it looks like you are trying things from other sites to get openhab to work. If you are trying my instructable and it does not work, I can help. I believe the unattended install script will fix many problems, but I have not tried it on other people's instructions. Have you tried logging into your raspberry pi and running these commands:$ ssh pi@♣ip-address♣ $ sudo wget "https://raw.githubusercontent.com/dumbo25/install-openhab-demo/master/openhab_uai.sh" $ sudo chmod o+x openhab_uai.sh $ sudo bash openhab_uai.sh $ sudo reboot Wait about five for the raspberry pi to boot and openhab to start. Open a browser on your laptop and enter:http://♣ip-address♣:8080/openhab.app?sitemap=demoBe sure to replace ♣ip-address♣ with the actu...

From your posts, it looks like you are trying things from other sites to get openhab to work. If you are trying my instructable and it does not work, I can help. I believe the unattended install script will fix many problems, but I have not tried it on other people's instructions. Have you tried logging into your raspberry pi and running these commands:$ ssh pi@♣ip-address♣ $ sudo wget "https://raw.githubusercontent.com/dumbo25/install-openhab-demo/master/openhab_uai.sh" $ sudo chmod o+x openhab_uai.sh $ sudo bash openhab_uai.sh $ sudo reboot Wait about five for the raspberry pi to boot and openhab to start. Open a browser on your laptop and enter:http://♣ip-address♣:8080/openhab.app?sitemap=demoBe sure to replace ♣ip-address♣ with the actual raspberry pi's ip address.Can you run the following commands and post results?$ cat /etc/*-release$ uname -mrs$ ps -A | egrep -i "gnome|kde|mate|cinnamon|lxde|xfce|jwm"Also, could you try the following command and post 100 or so lines to pastebin?$ sudo journalctl -fFinally, can you run this command and post the results:$ /usr/lib/systemd/system/openhab.service

A couple more guesses: * If all of the addons are installed, then it takes 5+ minutes for openhab to get to a stable state. Are you waiting long enough?* If the raspberry pi is operating correctly, then it should work the same way on every boot. Can you measure voltage on the raspberry pi 5v and ground pins? If voltage fluctuates and drops below 4.9v, then the power supply is at issue.

I am not sure I understand the issue. Is the Raspberry Pi hanging, or is your laptop unable to connect using a browser to OpenHab on the RPI? Please provide additional details.This seems to be an incomplete statement: "Boot message it is hanging on is:" What is the message it is hanging on? A boot message seems like the raspberry pi is hanging.Also, this doesn't look correct: "LSB: Rais network interfaces"Are you using Wi-Fi or wired connection? If Wi-Fi on Pi3, how is it configured?Are you using DietPi or Raspbian?Did you try running the unattended install, it should fix whatever is wrong?My wild guess is the openhab directory does not have the correct permissions. Some file in one of the sub-directories contains a file that cannot be read or written.

TO: jimmie.c.boswell, M2aestro and Gursimran Singh 425I read through the instructable and was interested by the comments and Singh's other projects. The combination of Singh's CFL-based light with wireless electricity is very cool. An LED-based lamp using only wireless electricity would be <fill in the blank> (more effective, higher lumens, more reliable, ... a bad idea, ???). And I am very tempted to pursue. However, this is way beyond my abilities/knowledge. Any chance one of you could make an instructable for this? Having reliable lamps that work at night and do not use electricity from the grid would be transformative.

You have jumped ahead of me. Try posting your question to this forumhttps://community.openhab.org/t/openhab-mqtt-inbou...This forum focuses on getting mqtt inputs & outputs to display in the browser.

To stop after auto reboot, try:$ sudo systemctl stop openhab.service I have not used debug. However, I use this command to view logs:$ sudo journalctl -f -u openhab.service

Did you use PC or MAC?

Thank You.