Für viele mag das überraschend sein, aber auch wenn wir die Hardware physikalisch besitzen: Die IoT Produkte gehören uns gar nicht.
Die Situation ist zwar auf den ersten Blick etwas besser, als wenn man z.B. e-books liest. Dabei besitzt man ja nicht einmal ein physikalisches Exemplar, das man anfassen kann.
Aber für viele IoT Geräte benötigt man nicht nur die Software in den Geräten – das ist ja für uns inzwischen normal – sondern auch einen Cloud Service. Und wenn dieser Cloud Service nicht mehr zur Verfügung steht, dann kann man auch das Gerät ggf. überhaupt nicht mehr benutzen.
Also sollte man sich diesen Randbedingungen auch vorher bewusst sein. Entweder man akzeptiert das, und das Gerät kann ggf. neu gekauft werden. Oder es besteht die Möglichkeit, das Gerät auch ohne den Service zu betreiben.
Ansonsten kann es passieren, daß man für sein Smart home die Geräte ein paar mal kaufen muß.
You wanna try out your AR makeup with the google search? This feature helps you making better decisions with your makeup. Regardless if it’s related to lipsticks or eyeshadows.
So you can stay beautifully and safe at home at the same time 🙂
And there is even no need to move away from the search results to the shops…
What a cracy world we are living in. The very popular software Notepad++ is banned in China. Let’s see how long that ban will be active. On the other hand I guess that there will be other similar software solutions available for China.
More and more countries are banning software. And looking at the tiktok battle that is going on between the US and China, it’s getting more and more obvious that this is a fight for power.
I’m betting that the US is loosing that conflict in the long term. They cannot just block hardware like Huawei and software like tiktok. It’s getting clear that the US is getting behind and is no longer „first“ in these technologies.
But instead of putting plenty of money in the development of such technologies to stay competible, they are putting their money in the development of weapons.
Like the technical evolution turned from a hardware focus to a software focus, there will also be a shift from the physical weapon power to the power of economics.
After having some trouble with my existing system I decided to upgrade to a RPi4 powered system, together with a SSD as a new storage medium.
As I wanted to migrate the old data to the new system I had to come up with a strategy how to get there.
First I prepared the RPi4 to boot from another storage device as the standard SD card, based on the following tutorial.
Then I flashed the SSD with the currently available latest raspbian buster version and attached it to the blue USB 3.0 slot.
While booting I got some errors from the fsck utility, but after some booting time it ran through. I tested a bit further and was rebooting a few times. Every time another error occured and finally – after some hours – I had the idea to put an USB hub between the SSD and the RPi4. So it looks that the USB hub solves the problem, although it’s not even powered. Weird, isn’t it?
And, voila, from now onwards the booting and also the working of the system was perfect.
Now as the base system was running and the RPi4 was able to boot from the SSD I had to migrate the software and the data of the old system to the new system.
For this I used the backup of the old system I made with raspiBackup, just flashing it completely onto the SSD.
The final step was now, to copy the .elf and .dat files from the still existing boot partition of the SD card to the boot partition of the SSD, so that the RPi is booting from the SSD.
Now the system is up and running and it is really very fast 🙂
But hold on, we are not done yet!
IP and DNS entries
I have setup the new system with a new IP address, running in parallel to the RPi3 live system. I thought, „OK, let’s just switch the port forwarding of the router to the new IP address with the ports 80, 443, for IPV4 and IPV6 addresses and it should work.“
Unfortunately it did not work.
I forgot, that I had to reconfigure also the DNS forwarding at my domain hoster with updating the CNAME. And, unfortunately again, there is a time to live (TTL) set for the CNAME entry. So it’s much recommended to set this TTL value to the lowest possible value some days in advance. Otherwise it takes a few hours that the CNAME changes are taking effect through all the DNS servers.