spacehuhntech / huhnitor Goto Github PK

This is how I imagine it:

0. Application starts
1. Lists all available ports (line by line) with some sort if ID/numerbing
2. User either types in the port name, the ID/number or plugs in a new device
3. When a new serial device was detected or the manual port selection was successful, print the connected message and continue the program.

A parameter, maybe --no-auto disables to auto connect feature. So that if a new port was detected, it just gets added/printed to the previous port selection list.

While concatenating two commands with ;; sequence, the huhn read command isnt working.

On startup, the Huhnitor should say something like

Having problems connecting? Try installing drivers from:
https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers

And running huhnitor --driver could automatically open that URL for you in the default browser.

This feature is especially important for those "poor" Apple users that don't get an OS equipped with common drivers. To be fair, older versions of windows or some linus distributions probably have the same problem though.

When the huhnitor connected to a deauther, it could send a command like welcome automatically.
That would have the advantage, that the user directly sees if the connected deauther is flashed with the latest version and functioning correctly.
But we'd also need a --no-welcome argument to disable this feature.

I was wondering if huhnitor can be installed on phone or do you have a huhnitor version that supports android phones

This could be useful as some people does not have a laptop to work with.

Looking forward to your response.

We need a chicken as icon for the compiled binaries 🐔

As discussed in rC3 Talk here is the problem description.

Describe the error
I often get the error message ,, Error Device not configured (os error 6)" after executing commands.
I have not yet been able to see a pattern of when the message appears. However, Hunitor then exits automatically.
Often, when restarting, it then seems as if the previous input arrives delayed.
I have set up the controller with the epsTool, as described in your udemy course.

The strange thing is that the scan command works, for example, but then the program suddenly terminates without further input.

Screenshots

**Environment **
ESP8266 D1Mini NodeMcu
MacBook Pro
MacOS Big Sur

If there is anything I can do to help, I'll be glad.
:)

Sometimes it can happen that you type out a command while the Deauther is still printing output.
Here you can see the user typed stop and it got merged with the output, breaking the formatting of the table.

It's not a huge deal, but it would be really nice to have a seperate input field for typing commands and a window only for the output. Kinda like the Arduino serial monitor.
I would imagine it like this:

On a quick search I found this crate: https://github.com/fdehau/tui-rs. But not sure if there are better/easier ones out there.

A way of flashing bin files through the huhnitor.
This could be achieved by either implementing the necesary protocol ourselfs, or by packaging the esptool as part of the huhnitor.
One step further, I can imagine the huhnitor auto recognizing the deauther version that is flashed and offering an autoamted update process.

Not sure if and how possible, but instead of CTRL+C resulting in

error: process didn't exit successfully: `target\debug\huhnitor.exe` (exit code: 0xc000013a, STATUS_CONTROL_C_EXIT)

we should think about a proper goodbye message. Maybe also a proper way to exit without CTRL+C.

DE:
Wenn ich einen Befehl ausführe, der mit einer gefärbten Ausgabe arbeitet, dann wird meine Eingabe mit der selben Farbe angezeigt.
Könnt ihr es bitte fixen? Es ist eigentlich einfach, aber mit Rust kenne ich mich leider zu schlecht aus.
EN:
When I run a command that works with colored output, my input is displayed with the same color.
Can you please fix it? It's actually easy, but unfortunately I don't know enough about Rust.

Hello, I'm currently using Windows 11 22H2 (OS Build 22621.1848).

Huhnitor version: 2.0.0_windows.exe

The CLI Ascii Display seems to be not really working with the new Terminal. I got it working with manually changing back to the WIndows Console Host (old cmd).

If anyone else has this bug, here's the fix.

Hey. When i plug in my board i get this error

Please forgive the ignorance.

After #2 and #3 it makes sense to add a help argument.

Running huhnitor --help should print all parameters and what they do, like you'd expect form any other terminal application.

But running huhnitor with a unsupported argument for example huhnitor make me a sandwich should tell you something like
Parameter "make me a sandwich" not found. or Parameter "make" not found. depending on how the argument parsing works.
and then continue printing the help page.

Once you use "start" and try an "alias"
Following "start" steps lead to incorrect order of parameters

Just switching the order of "-name xxxx" "-mac xx:xxx:xxxxxx" solve it

Sory for bady engilish~

can Huhnitor run without PC?
like when we program the command through pc and it run automatically after we unplug it from pc and just powering it with battery

The huhnitor could save all sent commands by the user into a history list.
When the user presses arrow up or down, it would scroll through the command history.
Just like you know it from a OS terminal.

Apk?

Would be very convinient to chose the serial port over the command line directly like
huhnitor -p COM3

Automatically close the huhnitor if the user presses CTRL+C (and only that) 3 times in a row.
Thtat way it's more idiot safe but also convinient.