jamesswift / localbytes-plug-pm Goto Github PK

Hi,

I am trying to "upgrade" some 2023-03 plugs flashed with tasmota to this esp firmware.
One worked fine. The second seems to be "bricked". I may have been a little impatient while going through the tasmota-minimum, localbytes-plug-pm cycle.

Whatever happened, the plug is now unresponsive. Button does nothing, led never lights up.
It does seem to appear on th previous configured network (unifi shows it is connected and it's IP). Browsing to that IP returns ERR_CONNECTION_REFUSED.

I have tried the tasmota power cycle, to no avail. I am assuming that the last firmware upload failed part way.

The question...
I am familiar with esp dev boards. Is there a way to get physically into these plugs so that I can flash it directly?
They appear to be glued closed. Is there a trick to opening them?

Cheers,

I'm very new to Github so not sure how to suggest an addition to the documentation so hope this is correct.

I found when trying to flash the localbytes plug with the minimal.bin file that it would always say the file was too big. Tried gzipping it but same issue.

After lots of research, I found that if you do an OTA upgrade to the minimal bin file using the following address http://ota.tasmota.com/tasmota/release/tasmota-minimal.bin.gz it would work perfectly. I could then upgrade using James's downloaded localbytes bin file with no issue.

Just thought that might be worth adding to the documentation to help others who might find the same issue.

Hi

I find that when rebuilding and uploading the firmware in ESPHome, it will turn off the output. Is this a software or hardware issue? ie, is it physically impossible given the hardware to not power cycle when reloading firmware?

Thanks

As the title says - disable LED doesn’t survive a power cut.

Plugs bought pre-flashed with 1.6.1 last week, then upgraded to 1.6.3 via web interface. HA reports 1.6.3 correctly.

Adding "default_state" to yaml does not work and causes the device to fail to connect to wifi.

substitutions:
  name: "localbytes-dishwasher"
  default_state: "ALWAYS_ON"
packages:
  localbytes.plug-pm: github://JamesSwift/localbytes-plug-pm/localbytes-plug-pm.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false


wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

Current solution is to remove the "default_state" and OTA update on the webui and use Home Assistant to turn on when connected to network.

Thanks!

I notice that when flashed with ESPHome the plug gets warm (not hot). I wondered whether there's any way to optimise that away a bit, even if it's at the expense of the monitoring being slightly less responsive?

Although I have converted some older plugs successfully, and the attributes such as power/energy etc are showing values in HA devices, the ESPHome webui itself is showing these as Offline.

If I click on logs, it all looks fine with logs of sensor data appearing as expected.

The only error message in these logs is as follows:

[15:37:48][D][sensor:093]: 'Power': Sending state 0.00000 W with 0 decimals of accuracy [15:37:48][D][sensor:093]: 'Daily Energy': Sending state 0.00005 kWh with 2 decimals of accuracy [15:37:48][E][json:041]: Could not allocate memory for JSON document! Requested 288 bytes, largest free heap block: 288 bytes [15:37:48][E][json:041]: Could not allocate memory for JSON document! Requested 184 bytes, largest free heap block: 184 bytes

Is this something that you are aware can happen and is there anything I can do about it?

Good evening,

I have been trying your firmware and have noticed when you calibrate the data through HA, the calibration data is lost when power cycling the plug

Thanks

Having updated to ESPhome 2023.7.0 I get the following error when trying to update my plugs:

"The restore_state option has been removed in 2023.7.0. Use the restore_mode option instead."

Thanks for your time and effort in maintaining this.

I have a new Tasmota plug v12.2.0

I want to flash with Esphome instead so am looking at using your project. However, to ensure I don't just end up "bricking" my plug, I need to ask a question raised by a contributor to the HA forum.

But tasmota starting v12 has different partition system that’s not compatible for esphome ota (indicated by safeboot partition in the settings).

There’s a workaround for that Read/Write bootloader, partition table and any partition via OTA by angelnu · Pull Request #5535 · esphome/esphome · GitHub

Is this likely to be an issue if installing your project onto a newer plug?

Can the WiFi SSID be changed after the initial config?
There is no WiFi config option in the WebUI

[EDIT] - Ignore this as I clearly needed to do more homework!

Hi,

I've noticed that whenever I update the firmware of my plugs, the LED turns back on. Not a huge deal, but can get annoying for plugs located in bedrooms.

I had a quick look through the YAML, and it seems the "Disable LED" switch has the restore_mode set to RESTORE_DEFAULT_OFF. My understanding is this should try to restore state to whatever it was previously. Why is the restore failing? The setting works for the relay.

Thanks in advance.