New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT Client convert after Upgrade States from Number to String #289
Comments
How the values look like? |
Both states before the update (after update the type is changed to string)
Example 2:
Both states where created automatic by sending a value via mqtt to the broker |
I mean, what will be received via MQTT for these topics? |
@BernhardLinz Please let ne know what will be written into ioBroker client from MQTT Broker? The value conversion is now working in other way somehow and I must know what will be received via MQTT |
Öhm, könntest du das noch bitte auf Deutsch beschreiben, ich verstehe gerade nicht genau was du brauchst. |
Bitte ein Debug log posten. Am besten die Instanz Loglevel auf Debug stellen UND in der Instanz das erwiterte Debug aktivieren. Dann sehen wir weiter |
Danke,,das war hilfreich. Bitte Installier mal von GitHub und starte danach Adapter manuell neu ... geht es damit wieder wie vorher? |
Jupp, geht wieder wie vorher - er konvertiert beim Start die vorhandenen States nun nicht mehr und alles läuft wie gewohnt. Damit ich was lerne: An welcher der obigen Zeilen aus dem Log hast du denn das Problem einkreisen können? |
And diese hier: "233.57" war als string eingetragen |
I am using the MQTT-Adapter in Client-Mode with a existing mosquitto server on same host (127.0.0.1).
When i upgrade den MQTT-Adapter from 3.0.6 to 4.0.0 there will be many states converted from "number" to "string":
After that many of my Scripts are broken, also the SourceAnalytix-Adapter have Problems;
2022-05-13 09:00:41.240 - error: sourceanalytix.0 (1275363) Input value for mqtt.0.esp32.esp32gas.zaehlerstand, type = string but should be a number, cannot handle calculation
The text was updated successfully, but these errors were encountered: