Closed Snuffy2 closed 1 year ago
I turned on the Display to see if that had any effect and it didn't seem to change anything. The error is still appearing. Another thing I noticed is that displayMetric is not listed as an item in the SSD1306toMQTT JSON when looking with MQTT Explorer. It is listed under WebUItoMQTT and changes when I check/uncheck the Display Metric box in the WebUI.
This looks like a legacy discovery for displaymetric for SSD1306, from before it was moved to the WebUI. Needs to be removed for SSD1306/moved to WebUI.
Hi @Snuffy2
would you be able to verify with a test build?
@Snuffy2
A test build which should fix the warning messages can be installed at
https://docs.openmqttgateway.com/dev/upload/web-install.html
If you could also check the correct switching between metric and imperial units, that would be great.
I installed version 9d8a96 this evening.
Thanks for testing @Snuffy2
The displayMetric setting only applies to the alternating device property unit display on the WebUI main page and on the Heltec/LilyGo internal OLED display.
The rtl_433 published MQTT messages will always have temperature_C, which can/should be auto converted to Fahrenheit if so defined in HA.
I was more curious as to whether the switching also works now in the HomeAssistant Gateway Control for the different display on the Heltec and WebUI.
Gotcha. The temperature does show correctly in °F in the WebUI when I uncheck Display Metric.
Thanks for the confirmations.
Closing
Describe the bug Since upgrading to v1.6.0, I've been getting a lot of these errors in my Home Assistant logs.
I believe it is coming from OMG and may be related to #1504 although I believe that was added in v1.5.0 and seems to be this line
I'm running a Heltec WiFi LoRa 32 (V2.1) running RTL_433 which I believe uses the SSD1306 Display. I do have the display turned off.
I do not recall seeing these errors in Home Assistant with OMG v1.5.1
Environment (please complete the following information):