… when it is actually usable one day.
The big problem of RISC-V is the fragmentation of the market, and it is not even a big market to start with.
There are GSM modems that can be used by the server to send an SMS. I nearly bought one when it was cheap, but noticed just in time that the GSM level of that device was 3, which is no longer available here. And it needs a valid Sim card to work.
A few days ago, I had a small glitch. I started a video and was presented with the first frame of what looked like an ad. Press play again, and the actual video played as it should.
I’m running a mosquitto here as the broker, and use MQTT Explorer for debugging.
Well, in my professional tasks, I have smoothed out about all trouble spots long ago. So having two new fields at once to work on and deal with their teething problems reminded me of times long ago.
The next step will be to implement two of the clients on RPi Pico W boards. The documentation on MQTT on that platform has quite some potential for improvement, to put it mildly.
That’s risky. Anyone who can access this can basically blow in some real voltage and power to burn the hardware.
Nearly everything. There are a few locks he can’t actually pick, and some others where he said he would use them himself, which I would take as a “basically unpickable for anyone else”.
I have no idea whether a smart lock ever entered this category.
Whatever lock you think of, check the lockpicking lawyer YT channel for it. If he has reviewed it, check how he rates it. In general, he opens those things in seconds.
Dr. Google MD at its best.
You don’t own anything that is not on your own system and/or without any DRM.
Well, I think it is necessary if you have mobile devices. Anything nailed down should be connected by wire, but if it is mobile, it should get the connection. Especially if the cell phone link is not that good inside the house.
I know that this would be the most secure way. But I seriously doubt that this level is necessary in a normal home network.
That’s what MAC whitelists are for. Your DHCP server should be able to handle this.
Identify your friendly devices and give them one setting with everything (full subnet and correct default GW). Identfy your IoT devices, and give them another (full, or specially limited subnet mask, and fake default GW, maybe a different nameserver, too). Anything else is guest and gets a very limited subnet mask and a working default GW.
I’m pretty sure I don’t do this ;-) I know how routing works.
Then why don’t you ask the people who do this?
But you don’t need several LANs for this. This can easily done with proper routing. A can access internet and internal network addresses. B can only access internet, and C can only reach internal addresses.
I’ll wait and see if they manage to get embedded system debugging to work properly. What I’ve seen in the past has been a pain in the you-know-what in that regard, showing clearly that their main focus was PCs.