Closed haselchen closed 1 year ago
@haselchen bitte nochmal mit der aktuellen Developmentversion 0.5.32
testen
@lumapu
@haselchen bitte nochmal mit der aktuellen Developmentversion
0.5.32
testen
a) Wo finde ich diese Version? b) kann ich die OTA einspielen?
Wäre ein Riesenaufwand , das Konstrukt abzubauen zum Flashen.
ok, das ist den Aufwand aktuell nicht wert. Warte besser auf das nächste Release, ich hoffe ich kann es bald veröffentlichen.
Um deine Fragen zu beantworten:
Discrepancy still exists in 0.5.32, GUI status is correct:
GUI: ... is available and is producing MQTT: available_text, ... (27 bytes): available and not producing available, ... (1 bytes): 2
available showing value 2 obviously reflects the constant MQTT_STATUS_AVAIL_PROD and is therefore correct.
Further conditions in addition to my comment above:
Case 2 GUI: ... is available and is not producing MQTT: available_text, ... (27 bytes): available and not producing available, ... (1 bytes): 1 --> ok
Case 3 GUI: ... is not yet available MQTT: no information except uptime --> available_text, available intentionally skipped?
@lumapu we are building the UI answer using several String concatenations and a complex conditional structure.
Wouldn't it be easier to simply declare the Strings for MQTT_STATUS_AVAIL_PROD
, etc. as an const enum char[]
/ String
in Flashmem and use the index from available
to translate all responses available_text
and UI ?
That could go into a common outputLibrary which can be called by both outputMQTT and outputJSON by he REST API.
maybe that's a good approach to share strings between MQTT and JSON.
Inconsistency between GUI and MQTT now fixed in 0.5.35, no MQTT messages during unavailability of inverter, already addressed in #416.
@haselchen would you mind to close the issue or does @lumapu want to reference and close this with the (hopefully) next release ?
I will close it with the next release, otherwise we will have duplicates here
@haselchen would you mind to close the issue or does @lumapu want to reference and close this with the (hopefully) next release ?
Ich warte auf das nächste stable Release und , wenn ok, dann kann hier zu.
Platform
ESP8266
Model name
Wemos D1 mini
nRF24L01+ Module
nRF24L01+ plus
Antenna
circuit board
Power Stabilization
board
Connection diagram
Connection diagram I used:
Note: [] GND Pin 1 has a square mark on the nRF24L01+ module
Connection picture
Version
0.5.28
Github Hash
2e08ee0
Build & Flash Method
ESP Tools (flash)
Desktop
Windows
Setup
Device Host Name
WiFi
Inverter
Inverter 0
General
NTP Server
MQTT
System Config
Pinout (Wemos)
Radio (NRF24L01+)
Serial Console
Debug Serial Log output
No response
Error description
This information is displayed in the Ahoy GUI:
Inverter #0: HM-600 (v10010) is available and is producing
In MQTT in Iobroker is displayed this: