Closed ACrazyConcept closed 1 year ago
Thank you for your thorough bug report. However, I see nothing wrong in what you're sending. Can you elaborate on what kind of bad data you receive on MQTT?
Your difficulties to connect indicates a potential issue in your Wifi network? I always recommend to set a static IP address, could you try that and see if things improve?
Regarding:
Your HAN port is encrypted, so to receive data at all you should have entered encryption keys that you received when activating the HAN port. I assume you remember this now. :wink:
There has been some reports on difficulties in upgrading from v2.1.x to v2.2.x, it was a quite substantial upgrade.
Try the following:
Thanks for the swift feedback.
Regarding the bad data I posted a screenshot. But should of course also have included how it looks usually.
As can be seen below there are many more attributes.
As for wifi the connection was rock solid on 2.1.17. I am using ip reservation. Just tried set a static ip now but with no improvement.
Yes (of course :)) I have encryption key and authentication key.
So I will attempt a reset as per your suggestion.
Hm... OK, a lot of sensors missing. It could look as if the MQTT payload setting is incorrect (did not get transferred correctly from v2.1.x)? Awaiting to see if a Factory Reset sorts this out.
I did the reset and after uploading the saved config and rebooting it still behaves the same. Could it be some issue with mqtt?
I see this in the mosquitto log.
1680787925: New connection from 10.0.0.238:61409 on port 1883.
1680787925: New client connected from 10.0.0.238:61409 as 29880569 (p2, c1, k10, u'hass').
1680788248: Client 29880569 has exceeded timeout, disconnecting.
1680788723: New connection from 10.0.0.238:58119 on port 1883.
1680788723: New client connected from 10.0.0.238:58119 as 29880569 (p2, c1, k10, u'hass').
Can you show me a screendump of your config page?
Sure. I am not very good with mqtt to be honest. It was just working for such a long period I am not sure it is setup properly. There could easily be some weird stuff.
Yes, might be something related to MQTT - but I think there should be a GUI warning if there are MQTT issues (like connection problems). I see some points you might consider adjusting:
Select Price region and currency, and enable price fetch
You use local DNS, are you sure 10.0.0.20 is a good choice here? I usually specify a public DNS, and 1.1.1.1 works fine:
MQTT 1: This could be the reason for the missing sensors: I think you want to select Home Assistant payload here?
MQTT 2: Do you have spaces or special characters in MQTT username and/or password? I believe there has been some issues there. You might want to try to change your Mosquitto to no user/password and try without - just to see if that sorts things out.
I still don't understand the issues you have regarding connection / UI reactivity, but try these adjustments first and see what it gives.
Thanks! I just tried the HomeAssistant payload type. It seems to be working without any issues. Will let it run for a while.
I think I am good with using the HomeAssistant payload type. Thanks again 👌
Describe the bug After I upgraded to 2.2.12 it did seem to work for a few minutes. Then it started getting "bad" data and the web interface is sometimes not responsive. I then tried to unplug and plug it in again and it did not get connected at all for a while. I have now managed to get response and retrieve some debugging data.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Hardware information:
Relevant firmware information:
Additional context Add any other context about the problem here.