Roman Priesol

Results 115 comments of Roman Priesol

I am using https://github.com/sairon/esphome-nspanel-lovelace-ui and no issues with tft upload. Have to mentioned that I never had such problem with our "default" nspanel component.

nextion will raise an error if is updated with a tft file for a different type ![image](https://user-images.githubusercontent.com/206765/199056891-b9f9f4d5-034e-448a-af59-e14e8a4f348c.png)

you have to download it from their web and it is only in chinese https://community.home-assistant.io/t/mmwave-wars-one-sensor-module-to-rule-them-all/453260/40

Is the chipset definition needed? Because 1wire 64-bit ID contains a 8-bit family code, so it can be always autodiscovered https://www.analog.com/en/technical-articles/1wire-software-resource-guide-device-description.html (Maxim 1-Wire device types are missing in this list).

The dallas component is really old and it was never meant to be universal, so it is supporting only DS18B20 sensors. Probably a major rewrite would be needed to support...

And ideally when it could be used for i2c 1-wire masters like is mentioned here https://github.com/esphome/feature-requests/issues/621

Can you get log from that device? Because this is not very helpful. I have only olimex esp32-poe-iso with the same eth phy and it works just fine with ble...

Can you get logs from uart? If everything is on the same network, then `use_address:` (the dashboard uses it as the device address when mDNS is not available) is not...

"Brownout detector was triggered" => system voltage is below threshold, so your PSU is not providing enough power.

Hm, I have missed that. Wondering why it is acting co strange - when ble is enabled why "via the network" changes to "wirelessly". Since it ends with some weird...