-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beginner's guide - Appreciate some help #48
Comments
Found some information now how !secret refers a variable to the secrets file. That helps. |
Sorry for posting my comment under "Set the MCU to UART boot mode (pull TX pin low during boot)", I thought it would make sense to keep my expererience with the same issues at the same topic. So I am in the next phase of flashing the datalogger. Now I need to buy a usb to serial adapter.
Thanks. |
1./2. The serial adapter you pasted looks good. One never can say for sure if it will work. Some serial adapters do not supply enough power for the MCU -- but you can not "see" that in advance. Also put some male-female Dupont wires in your shopping cart. If you document everything you do here with pictures, links, screenshots so others can learn from it, I'll help you if there are problems. |
Set your USB serial adapter to 3.3V (not 5V).
secrets.yaml: All the above values are hardcoded into the UF2 file. Do not give the UF2 files to untrusted persons as they contain you WiFi password. The screenshot you pasted ("LDO Mode BD_Info") is the boot log of the original vendor firmware. |
THe only thing I get is "Connecting to chip", Hardware reset, Software reset and this looping. How can I tell the 'pull' worked? I also found that using the Dupont pin on the other side of the stick might be too short to connect a female to it. It really is very lose. So if that does not connect the pull will fail as well. |
Yep, that was the problem. I just kept two males against txd/gnd and pulled those. That worked. |
Yes, just use two different yaml files. People tend to give them descriptive names like Just check if flashing suceeded by powering the stick without TX pulled low. If everything went ok, you should see the ESPHome boot log in terminal. If not, try to flash again. |
Looks good. Now you never should need to connect the serial adapter again. You can update via ESPHome OTA. Press the LOGS button to see the device logs. Your terminal uses the wrong baud rate (should be 115200). |
The logs look good. Should I already see any values for the entities? It is still just connected to the adapter. |
Thanks for all your help BTW! |
You'll not see any values unless the stick receives values via ModBus from a powered-on inverter (usually they power down at night). Go to HomeAssistant->Settings->Integrations->ESPHome to see the details then. Consider to star this project if you like it. |
You need to add the device on the HomeAssistant->Integrations page, see my last post. |
@JGeeforce Yes, that is the USB stick I used. |
Baud rate tip! As I had issues with backing up the original firmware I had to set the baud rate in the Windows version to auto! I had it set to 112500, but then I only got read time out. With auto it took 6 minutes and with success. |
I have 2 x Solis 10.0 kW Dual MPPT (3F) . Their dataloggers (LAN) dont work. Now I am planning to buy two S3-WIFI-ST dataloggers.
And hopefully they will let me integrate the inverters into HA. So I am going through the installations of the ESPHome and Solis Add-ons. Probably for lots of HA people easy to do, but I got lost in the amount of documentation in specially for ESPHome. So I hope someone is willing to help me out here.
I installed ESPHome and started it.
I added the two yaml files to the ESPHome directory (1 in subdir 'common')
Then I need to modify the configuration:
The api encryption key, I can just paste any Encryption key there?
The wifi ssid and pwd, I assume is off the wifi near the inverters.
and the ap wifi ssid and pwd, where to they come from, do they come with the wifi dataloggers?
And is it straight in like 'key': 'value' ?
and I see this:
Do I need to add these to the secrets.yaml as well? any ota_password will do?
And in the ESPHome documentation, I see this:
but it does not mention what configuration file, is that the secrets.yaml?
Probably more questions later. Any help appreciated.
The text was updated successfully, but these errors were encountered: