2.8.0-BETA4

[sijones]

Full Changelog: 2.7.1...2.8.0-BETA1

More Inverter protocols support, not just Pylontech anymore, these are untested as i don't have the hardware to test.

Information added to dashboard UI, if your inverter sends the heartbeat CAN ID then you'll see Inverter Connected on dashboard.

General bug fixes and move the CAN sending to Core 1, this stops the timeout error happening on the CAN TX packets, also added a dynamic timeout increase if they do timeout so it self adjusts if the inverter is slow or hardware.

BETA2 Fixes missing 16Mhz option
BETA3 Fixes HA Max Charge Current hardcoded to 100A, now uses Max set in Web UI.
BETA4 Fixes issue with autocharge not being in the real time HA feed.

---

This discussion was created from the release 2.8.0-BETA4.

[kommando828]

Wifi Scan only shows AP's starting with a letter, AP's starting with a number are not in the list.

[sijones]

interesting, don't think there is anything in my code that should filter that out, but will check it out, thanks.

[kommando828]

I picked one of the AP's which it connected to, exported settings and edited the wifi to the AP starting 2, imported the edited settings which then showed in the AP list but on selection the Lilycan dropped off the network. Tomorrow I will reload the files and then connect to the AP diy-battery and before scanning load the edited settings reboot and see if it connects.

[kommando828]

Overnight HA lost all the sensors that use that same AP, so I went back to the beginning and as well as a hard reboot on the AP, which I had done yesterday when the issue first appeared, I also hard rebooted the network switch its connected to. Then after two full reloads onto the Lilycan the AP starting 2 appeared. So looks like some combination of AP routing issue and possible loading the firmware into the Lilycan some corruption made the AP unreachable. Also on the last two reloads the Canbus protocol selection appeared when it had not been there on the first 2 firmware loads.

Will test the SMA protocol later this week.

[sooty66]

I'm running 2.8.0 on an ESP32 Plus with Waveshare 2CH isolated CAN adapter.
The Waveshare has a 16Mhz crystal but even if I set #define initCAN16Mhz to true in config.h it still initializes the adapter at 8Mhz.

if ((!_CAN16Mhz) && (CAN->begin(MCP_ANY, CAN_500KBPS, MCP_16MHZ) == CAN_OK))

Line 253 in CANBUS.cpp seems to suggest that if _CAN16Mhz were true then it should initialize at 16Mhz.
I'm not a code expert by any means but I can't see where _CAN16Mhz is set to the value of initCAN16Mhz

[sijones]

It's passed in to the CANBUS::Begin() function

Main start up reads the value from nvs and passes it in.

[sijones]

Don't know what you're trying to do, but running the MCP builds, the UI exposes a Force 16Mhz switch that means that it sets this to true and then makes sure the Waveshare is put in to 16MHz.

[sooty66]

I’m running the ESP32 Plus build of 2.8.0
Maybe I’m blind or stupid or both but I don’t see a force 16Mhz switch anywhere in the UI

Could you please show me where it is?

[sijones]

it's missing, looks like it's dropped during a refactor of the UI. will release a new build soon.

[sijones]

Beta 2 is now released.

[sooty66]

Force 16Mhz switch is working now with Beta 2 :-)

Another Observation:
It would appear that the below entity in Home Assistant is representing the Requested Charge Current as it starts adjusting down from the Charge Current Limit value when Smart Charge kicks in.

The issue I see is that this entity is created with Min 0 and Max 100 values in HA so if you have a Charge Current Limit > 100 then it fills the HA log with errors because its trying to set the value to something > 100 when Smart Charge isn't active.

[sijones]

fixed in Beta3, the max will now reflect what is set as Max in the UI.

[sooty66]

Charge current entity is now behaving with Beta 3 👍

One further observation:
I have a lot of the below error messages in HA which I think are somehow related to the MQTT data for Smart Charge Status.

Template variable warning: 'dict object' has no attribute 'autocharge' when rendering '{% if value_json.autocharge %}ON{% else %}OFF{% endif %}'

[sijones]

Beta4, fixed the issue.

[sooty66]

All seems to be working fine now 🥇
Hopefully I won't be bothering you with any more bugs in the near future.

I did make a small donation to the cause and I would just like to thank you for what has obviously been a lot of work getting the project to where it is today and of course your prompt response to the issues I raised 👍