Closed mavo closed 6 months ago
Firmware update fixed it 🎉
HI mavo. Can you please share the firmware versions, you are on. I am on v3.0.8 (Master) and v1.0.9 (BMS). Thanks.
Hi @olomberg.
Me2, same version. Do you have issues?
I summarized the changes I did to make it work #192
HI @mavo. No. Works as expected so far. Only the official Zendure MQTT-API sucks. But I found a way to work around it.
Hallo mavo, gibt es schon eine Lösung um nach der Trennung vom Zendure Server die Daten des HUB-2000 per MQTT zB. im MQTT-Explorer zu empfangen ?
Bei mir hat zwar die Trennung geklappt, aber ich bekomme keine Daten ?
Siehe auch Issue im BT-Manager https://github.com/reinhard-brandstaedter/solarflow-bt-manager/issues/12
Ich nutze den Zendure HUB-2000 mit der letzte Firmware Version V3.0.10
Hi @Newbie-2, After I did the firmware update to 3.xx it just worked. Did you check if you have a queue named solarflow-hub in your mqtt explorer?
As said, after doing the update it just worked. I did nothing more to the queue config, only changing properties to use hub2 in the app.
MaVo
Hi @reinhard-brandstaedter,
today my hub2k did arrive, and ofc I installed it asap. So, its now running, I can see data in the sf-app on my smartphone and I disconnected it from the cloud using BT manager. I can see a small amount of messages in mqtt explorer, however, the control-app seems to have no idea.
I found how to set the product_id in the config file and did it. I also additionally had to modify the solarflow.py file in the container, as it contains the hard coded prod-id of the smaller hub.
However, I cannot see much more + the app is currently not working. What data can I provide you to help me find the mistake I made? 😇 This is what mqtt explorer puts out atm.
EDIT - output from bt-manager -i command:
MaVo