No, and mostly likely never will be. At least not from espressif otherwise they will probably loose their wifi certifications (which is mandatory in many countries). Other vendors do the exactly the same for regulatory reasons.
I’m not 100% sure but think that all of the modern wifi chips need to contain at least one binary blob which normally includes ota update mechanism…
You might want to call it that, yes. The computer/phone/tablet/whatever device you are using to participate in this forum most likely contains that “backdoor” too . It is typically used to get updated frequency rules/restrictions if I remember correctly.
And for sure you are also aware of the preinstalled rootkit threadx on your raspberry which is so kind to start your operating system of choice for you
And this is by far the best reason to bet all your horses on esp’s.
Over the last years probably a good dozen (including some more serious ones) vulnerabilities for esp’s were discovered. I often rolled out updates to all my esphome devices (thank’s to the update-all buttonfrom 2019 it’s only one click ) which included fixes. Till this day all ever affected cve’s should be fixed in esphome.
It’s actually awesome (and somewhat unique in this industry) that a manufacture (namely espressif) after soon 10 years still supports their oldest esp (8266) like it is the first day. Even more astonishing if you think of that a bare esp8266 module only costs $1-2
It’s this “platform stability” one might call it - or LTS in other words, that makes the esp ecosystem combined with a open source esphome a no brainer for me.
I remember, when I was at school to become an electrician, my teacher always said to us:
If you don’t want to be pushed going back to houses and redo installations because of shitty interference problems, never run a power line and a data line parallel closer together, than 20cm. If you maintain this spacing, everything will be alright…
Other vendors are not under Chinese jurisdiction. And thus are not required by law to give access or install backdoors if the government requires it. Something which seems to be a very common ocurance. The more popular the device, especially as exported good, the more likely this will be demanded. You may argue that other countries do similar things and I will agree to an extend. That’s why staying away from IoT wifi altogether is a good idea.
But if I have to choose whom I trust more between, say, Microchip (with their SAM-D lines) or ST Microelectronics (with their Cortex M7 line), both of which have very deep and extensive documentation of their chips and are subject to democratic laws and some shady Chinese company with a badly documented chip with lots of rumors about IP theft floating around (there’s a very persistent rumor about their IP stack being based on stolen IP from Atheros, of course there’s no proof of that) and subject to the laws of an uncontrollable totalitarian state, then guess.
Your point exactly ? Not as if that’s even remotely related to a wifi stack, but where are the Espressif binary blob certifications from multiple highly recognized international safety certification agencies ?
Eh, I’ll pass.
Not a fixed installation, not a high power installation. Electromagnetic Induction is dependent on current and length of parallel runs. A sonos speaker doesn’t pull 2kW. A space heater does. And it’s code.
Well, the big difference there is, that in the Sonos there we are talking about a very short distance. If you run 10m of cables parallel next to each other, things could get different
But, there are no hard borders. The only border is common sense
Electromagnetic induction on the same cable that carries power is not an issue (well, not in terms of safety concerns and cross interference at least). The problem comes from having multiple cables running in parallel with a very large difference in voltage.
Powerline Ethernet is still plagued with noise and is generally not very reliable, even though it’s specifically design for this purpose with special filters, interference rejection and whatnot.
Might be fine for that usage, but never got more than 10Mbps in my case, with base and receiver losing sync at least once a month.
Powerline is highly sensitive to the quality of your electrical installation, and if base and receiver are not on the same circuit, expect poor performances and issues.
Yeah HD camera footage doesn’t take a lot of bandwidth. Also if there are glitches and short outages on the transmission you probably won’t notice if a frame drops here and there. Things become more complicated if you need more bandwidth and more reliable low latency connections.
And as Chris said, really depends on your electrical installation. Especially when you’re trying to route the data over different circuits on different phases (you’ll need coupling capacitors then and those will typically introduce a lot of noise and signal degradation).
I typically see 60-90Mbps in mine and that is likely limited by the data stream of the camera it’s connected to. I’ve never tried to test the full speed I could get from them.
But I get what you are saying.
In my residential system they work fine (but most of us here fall into that category) but to use them on any large scale there are way better options.
I just use them in places I can’t run real ethernet cables so I can minimize traffic on my wifi.
If you use stock firmware in those TP-Link PLC boxes there must be connection breaks very often that may last a few minutes. For security system it maybe critical. I don’t know why TP-Link does not care about this issue. Also there are a few settings which can increase (shown) transfer speed.
I am not aware of one-fit-all firmware for all TP-Link products. As you did not mention exact type of your PLC, try to dig yourself some useful discussion for a solution.
Seriously? What devices are these on Wifi? I have some Tuya compatible devices and they are just driving me nuts. The last few HA versions have worked fine with these devices, on 12.10 now 2 of the Tuya devices don’t work - even after reset again. These devices really drive me nuts.
Never had such a problem on Zwave.