Skip to content
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

Services not working in current release (0.24.x) #159

Open
4homeassistant opened this issue Jun 2, 2024 · 7 comments
Open

Services not working in current release (0.24.x) #159

4homeassistant opened this issue Jun 2, 2024 · 7 comments

Comments

@4homeassistant
Copy link

4homeassistant commented Jun 2, 2024

For some reason the services in the current release seemed to stop working. I just went back to version 0.23 and it is working again but cannot say if it happend with 0.24 or 0.24.1 since I upgraded directly from 0.23 to 0.24.1.
Can someone confirm or refute this behaviour? Just saw that there has been a change in 0.24 #128 that may cause the issue but am no expert.
We've got two different go-e chargers: a Home Fix 11 kW from 2022 and a Gemini Fix 11 kW from 2023, are on the current HA release and had the issue on both chargers.

@syssi
Copy link
Owner

syssi commented Jun 6, 2024

Could you describe the issue in detail? Aren't the sensors updated anymore or are service calls broken?

@4homeassistant
Copy link
Author

Thank you @syssi, only the service calls are broken. Everything else is fine. I've got a couple of automations and templates based on services calls that didn't work anymore after updating and also doublechecked with the developer tools.

@4homeassistant
Copy link
Author

I also downgraded the chargers firmware to the last known working version (56.1). Can you see that behaviour in your environment?

@jusii
Copy link

jusii commented Jun 10, 2024

Same happaned to me, downgraded back to 0.23

Also have made load balancing like this, and it no longer works 0.24+

service: goecharger_mqtt.set_config_key
data:
  serial_number: xxxxxx
  key: amp
  value: "{{ (states.number.go_echarger_201199_amp.state |float|round(0) - 1)}}"

@syssi
Copy link
Owner

syssi commented Jun 10, 2024

Uh, may be I have an idea what's going on. The unique_id has changed probably and there is another go_echarger_201199_amp entity next to the initial one because of the changed ID. I will have a look!

@syssi
Copy link
Owner

syssi commented Jul 18, 2024

Please check the MQTT topics / the MQTT traffic of your charger. Does the topics start with or without a slash? How did you configure the integration? Does the integration configuration expect a slash or not?

@4homeassistant
Copy link
Author

I am not sure if I am on the right track. Just checked the MQTT output from both chargers with MQTT analyzer and they both start with a slash. Same in the debug Informations of the MQTT integration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants