For a while I’m using the Tiny Tiny RSS server. Lately I updated it to the latest version and since then I got the ‘60 SSL certificate : unable to get local issuer certificate‘ error for some of the feeds.
After some research I found the solution by adding these lines to the php.ini:
The cacert.pem file can be downloaded from https://curl.haxx.se/docs/caextract.html.
Remark: As you can see I gave the certificate file the .txt extension. If you just use the .pem extension you will probably get an error like this:
cURL error 77: error setting certificate verify locations:
Currently I have the following devices and services setup:
- Klik-aan-klik-uit (Kaku) remote (433Mhz)
- Nest thermostat
- Philips Hue lighting
- TV (infrared)
- PVR (infrared))
- Receiver (infrared)
- Kodi (trigger like: ‘on movie start’, ‘on pause’)
- Fibaro motion sensor (Z-wave)
- #Slack (for notifications)
- Buienradar (trigger to inform you when it starts to rain)
Adding new devices is very simple, because Homey will recognize most devices automatically. If an infrared device is not recognized automatically, you can learn Homey each key manually.
Homey already supports a lot of devices and Apps. Apps can be added via the Homey App store. Because Homey is open, it’s also possible to create you own Apps. So the number of Apps can grow fast if a lot people start developing themselves.
Homey comes with a build in Flow Editor. The Flow Editor makes it possible to create several flows. A flow is constructed by defining the IF (trigger) and a THEN (action). Optional you can use logical expressions to fine tune the IF.
Below an example of a flow to turn on the TV including the PVR and receiver. The flow is trigger by pressing a button on the Kaku-remote. When the button is pressed the led-ring of the Homey will turn red and an infrared signal is send to the TV, PVR and receiver. At the end Homey will say that the TV is turned on.
Another flow I have running is turning on the lights in the hallway when motion is detected. Another flow is turning of the light when motion is no longer detected. For detecting motion a use the Fibaro motion sensor.
I nice feature is that you can send notifications to your mobile or to #Slack. So even when I’m not home, I still know what is happening at home.
Still in beta
There are still some flaws in the software and Homey is not always triggering the flows when it should, but hey I still love my Homey. The guys at Athom are working really hard on the software and with each update Homey works better. Most of the issues I had where solved by looking for answers on the forum or with a software update.
Only speech recognition is not working as it should, but I hope this will be improved in one of the next updates.
If you have a Windows 10 IoT Core device and want to change some basic settings, follow the instruction below.
First we need to set up a connection with the device
- Start Powershell (as administrator)
- First start the WinRM service by running: net start WinRM.
- Now run the following command: Set-Item WSMan:\localhost\Client\TrustedHosts -Value <machine-name or IP Address>.
Press ‘Y’ to confirm the change.
- Now start a session with the Windows 10 IoT Core device: Enter-PSSession -ComputerName <machine-name or IP Address> -Credential <machine-name or IP Address or localhost>\Administrator. As password use: p@ssw0rd.
|Change Administrator password
Remark: Once this is done, you’ll need to establish a new PowerShell session using Exit-PSSession and Enter-PSSession with the new credentials.
|net user Administrator [new password]|
|Change device name
Remark: You will need to reboot the device for the change to take effect
|Reboot device||shutdown /r /t 0|
I while ago I bought myself a Raspberry Pi 2 to play around with. I wanted it to run on Windows 10 IoT Core. That worked fine, with a display connected to HDMI. When the official Raspberry Pi 7″ Tochscreen Display came out I wanted to buy one immediately, but I was to late. The first batch was sold out :-). So I waited for the next batch and bought one.
I directly downloaded the latest version of Windows 10 IoT Core (build 10556), but the screen was not working. Using HDMI it was working…Argh. First I thought maybe the display is not properly connected, but when I tried Raspian, it work fine (even with touch).
I’ve let it rest for a while and today I picked it up again and found a forum post, stating that build 10556, wil not work with a v1.1 of the Rasberry Pi Display, but it will work with the latest preview build 14262. So assuming that I have a v1.1 of the display, I downloaded the preview version and yes, it’s working! Even with touch 🙂
Now the development can begin.
What is Homey?
Homey is your personal assistant who will make your home personal again. Whatever you want to do, Homey takes care of the technical parts, so you’re left with the fun. Interact with your home and your devices in the way you interact with anyone else: using natural, spoken commands.
They just started delivering the first batch, so I hope to receive mine this month.
Update (13-01-2016): Looks my Homey will be shipped around 15 February 2016.
For some time a technology that is very popular with Java developers, but Microsoft has been working hard with Sonar Source to support it, starting from the release of Visual Studio 2015 for the .NET platform. The result is a great free Code Analysis tool to clarify Technical Debt, but also to show that it is eliminated.
Having problems starting the Apache service on Windows 10? Probably port 80 is used by another process.
When you check which process is using port 80 (use Resource Monitor), it probably is the ‘System’ process (PID=4).
This means that a process by default installed and started by Windows is using port 80. Big chance that the ‘World Wide Web Publishing Service’ is running. Just stop it and set the Startup Type to ‘Manual’
Now try starting the Apache service again. If it is running, the Resource Monitor should now show that the ‘httpd.exe’ process is using port 80.