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

WiCAN stops mqtt sendings and needs re-plugging to send again #274

Closed
micha53 opened this issue Dec 6, 2024 · 15 comments
Closed

WiCAN stops mqtt sendings and needs re-plugging to send again #274

micha53 opened this issue Dec 6, 2024 · 15 comments

Comments

@micha53
Copy link

micha53 commented Dec 6, 2024

I got my WiCAN this week and it works in principle. I use it in a Renault Zoe Ph. 2.
But I have one Problem: If the car ist standing and not connected to a wallbox, it stops sending mqtt telegrams. For a while it sends an Error Information, later this also stops. This should not be a problem, when it would start sending per mqtt after starting to load the car. But the stick remains "Sleeping" when I start loading the car. (It is the same behavior with and without enabling sleep mode in the settings.) I think in this moment the stick should restart to send mqtt.
A Reboot of the stick makes no effect, only disconnecting and replugging brings success.
I do not understand why replugging (hard reset) works but a software reboot brings no effect. But in general the stick should restart to send mqtt, when the loading process starts. I can't imagine that replugging can start the CAN communication of the car, so why does the stick not listen to the CAN?
The ...can/status topic says "offline" and the ...can/rx is not present.
At least with enabled sleep mode the power led is blinking and I cannot access the stick until I replug it. Also turning on the ignition of the car brings no change.
I would like to have that the wican starts to send mqtt if I start to load the car, without replugging the stick.

@meatpiHQ
Copy link
Owner

meatpiHQ commented Dec 6, 2024

can you please share a screenshot for your device configuration page? And the status tab as well.

@micha53
Copy link
Author

micha53 commented Dec 6, 2024

Config and Status:
Screenshot_20241206_164859_Firefox
Screenshot_20241206_165009_Firefox
Screenshot_20241206_165034_Firefox

@meatpiHQ
Copy link
Owner

meatpiHQ commented Dec 6, 2024

It's normal to stop sending MQTT if the car is not connected to the charger, because the ecu goes in low power mode. But it sounds like there is a bug in the firmware, when it's connected but ecu is not responding it fails.

I will try to reproduce this issue here.

What happens if, when in this state you plug in the charger and then reboot?

@micha53
Copy link
Author

micha53 commented Dec 6, 2024

actually this happened:
i was coming home by car half an hour before. Just looked at the dongle: Blue and green LED' s were on, yellow one was flashing. I started the car and moved some meters. After that flashing the yellow LED stopped.
And now, additional 15 minutes later I opened the mqtt explorer and for some cycles I saw the right values and after some seconds they vanished and I see only this:
2024-12-06 17_38_35-Window
cfos_mqtt/set/M12 is the automate destination topic.

Your Question:
If I plug in the charger and reboot nothing changes in the mqtt explorer.

btw. using the monitor in this situation I do not see any can-message.

@micha53
Copy link
Author

micha53 commented Dec 17, 2024

I made another test today:
Wican is in sleep mode and sleeps, I open the door: Wican wakes up and publishes car data
I close the door: after one minute wican stops publishing and goes to sleep
I open the door again and open the charging connector and close the door again and plugin the charging cable: Wican wakes up and publishes car data

So the adapter works in a way like it should do, only I had done something that caused the error. But actually I cannot say what was the difference.

I will continue to observe the behavior and will give a feedback when I know more about it. So actually there's nothing to do for the developer.

@micha53
Copy link
Author

micha53 commented Dec 27, 2024

Actually it works fine, so I close this issue.

@micha53 micha53 closed this as completed Dec 27, 2024
@meatpiHQ
Copy link
Owner

@micha53 works fine on the latest firmware version or are you still on the old one?

@micha53
Copy link
Author

micha53 commented Dec 27, 2024

Ah, I see there is a new version from yesterday.. No I still have the old one.
But a question concerning the new one:
I had problems with the value for the 12VBatt Voltage. In home assistant this variable causes an error. Adding a letter bevore the 12 solved the problem, but does not read the value published by the wican. Maybe it is not good to begin a value used here with a number. Does it still have the name 12vBatt?

@meatpiHQ
Copy link
Owner

That's in the zoe vehicle profile right? I can change it in the profile, this is not hard coded in the firmware.

@micha53
Copy link
Author

micha53 commented Dec 27, 2024

yes in the zoe profile

@meatpiHQ
Copy link
Owner

Ok, it's fixed now. Resync the profile and give it a go.

@micha53
Copy link
Author

micha53 commented Dec 27, 2024

thank you
and.. can you tell me, or put into the doc, what is the payload of an Battery alert?

@meatpiHQ
Copy link
Owner

here you go

{"alert": "low_battery", "battery_voltage": 12.0}

@micha53
Copy link
Author

micha53 commented Dec 27, 2024

so, Christmas is over, I thank you for the presents and I wish you all the best and a happy new year!

@meatpiHQ
Copy link
Owner

Happy new year! Cheers!

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

2 participants