NEXA 2000 Connection Problems and Slot Configuration

[d3rby91]

Hi everyone,
I'm a NEXA 2000 owner since today and after a lot of tinkering I finally got GroBro up and running.
My issues now are:

Cannot control anything via MQTT in Home Assistant — all controls (sliders, toggles) just revert back without applying.
"Read All Values" doesn't seem to do anything — no response from the device.
Cloud-initiated changes also fail frequently — setting parameters via the ShinePhone app often results in "setting failed" as well.

What am I doing wrong? Is this a known limitation with the NEXA 2000?
Could this be related to an older firmware version? The device indicated it wants to perform a firmware update, but since I've changed the MQTT server in the ShinePhone app to a local broker, I'm wondering — will it still be able to find and download firmware updates?
Setup:

NEXA 2000 connected to local Mosquitto broker via TLS on port 8883
GroBro running as HA add-on, SOURCE on port 8883 (TLS), TARGET on port 1883
GROWATT_CLOUD enabled for optional cloud forwarding

Thanks in advance!

[super-sonic-zero]

What firmware version are you on? I am using GroBro with a Nexa 2000 just fine. I let the device perform it's firmware update before setting up GroBro, though. If you are able to see the Nexa in the ShinePhone app, the update should still work.

[d3rby91]

FW Version is 14.12.14.11.9000.4019.

Yes the Nexa is still visible over the shine ap

edit : looks like its now the new firmware , but i have still problems.
Cant really Controll anything over the ShineApp, sometimes i need to restart grobro and then i can control for a few moments some stuff... make no fun really ^^

[d3rby91]

Found the problem — it was the oh-so-great WiFi antenna on the Nexa 2000... the thing just doesn't really pick up my WiFi properly, and because of that the updates were basically useless.
I've now got a separate AP with a dedicated IoT WiFi hanging right by the balcony window, and with that everything runs smoothly!
The only issue I've still got now is slot1 — I'm interpreting that as schedule 1, right? But when I create a second schedule in the cloud, no slot2 shows up... or am I completely on the wrong track here?

[robertzaage]

@d3rby91 Did you already tried setting the MAX_SLOTS variable?