CampusWi-fi's got speed limits. We can't get word out. We've got a net。
No cell phones, no internet, three esps, 8266s in the corner of the lab, two sounds, and we're talking。
It's not really blowing. I burned my hands on the first tablet, and the second the screen turned on, the roommate was “hungry” with andromeda app, and i pressed two confirmation keys, and old jumped out of “the downstairs cafeteria is still open”. Not schoolServersIf we don't go on the internet, the data will be in our own berry pie。
The teacher said that the school network strategy was mandatory, that it could not open hot spots and that it could not be installed as a third party ap. We tried bluetooth, a lock on the phone, and we couldn't get a reply. Micro-trust lan applets have also been tried, resulting in the direct killing of process backstage after android 12. Turning to the open-source file of quickchatbox, it was discovered that it did not even want to go to the internet — the device itself as a hot spot, someone else came in, the message went to http, the server ran on the second-hand berry pie in the dormitory。
The board chose esp8266ex, not a big one. It's cheap, it's much more informative, and arduino ide can run once recorded. Someone has to use esp32 to say we're good, but we really don't need voice recognition or cameras. One old, three keys, one small battery, enough. The charging circuit uses tc4056a with 3k resistance, 400ma is measured to be unheated, and larger, the charge chip is gas-breathed, automatic down-frequency。
It's kind of rough, but it works. Without mqtt, broker alone was stuck for three days. It was then replaced by a long connection to http, with a few lines of `wificlent ' code on the end of the device, and the server used python to write a light-size interface to connect uwsgi to the back of nginx, which was smoother than the cell phone tweet. The status machine has four phases: networking, network servers, etc., news processing. Each stage is covered by a guard dog, which is automatically reconnected when broken。
The server installed the pagoda, not a good picture, but instead changed the nginx configuration without restarting the service. When we upgrade the solids of the ota, if the HTML page breaks down for one second, the device cannot find an updated address. The database forms were also cut and deleted by the user, and the device keys and chat records were cleared and left intact. The message sheet says, "read or not, don't remember the time, find out fast, rotate for three seconds, have little pressure。
Android app, i wrote it. It didn't work with flutter. It was original java. Dkey did not just uud, but added the esp 8266 mac address to the server time stamp, mixed another salt value, and came out together with hashi. Old key will never count after reseting the solid. The shortcut response list is in redis with an etag version number. The equipment isn't connected to the server? Then use the three old local returns, no screens。
A friend's application isn't a single order. Both operations became incidents, the server slowly entered the library and the client pulled its own incident stream. So that both of them would “consent” at the same time, without a ghost agreeing to a refusal。
There's something else on this board. Oled is connected to dht22, which changes the temperature and humidity screen; gpio13 is connected to a relay, which can turn off a switchlight; and `/api/v1/device/control ' is added to the agreement, where a json can turn the rudder angle. It's not expansive, it's true that someone did it, and last year, next door to the electronics, they ran a thermo-controlled fan, and the code copied our http structure。
It's not high-tech, no al, no cloud synchronous, no push. But it made me understand for the first time:NetworkIt's not from the operator, it's from the equipment. Wi-fi signals are floating in the air, anyone can deliver a package, anyone can receive it, as long as you have an agreement on how to listen to the frequency and how to understand the bytes -- that's all done。
My computer fan sounded like a tractor that night. After writing the last line of server codes, running the call, the app pops up "connect successful" and the board jumps "hello, i'm node-007"。
I drank cold iced tea。
No screenshot, no circle。
