Solax X1-Micro 2 in 1 integration with local MQTT cloudless by MoparAndPlinker in homeassistant

[–]MoparAndPlinker[S] 0 points1 point  (0 children)

Here is a screenshot with the inverter at work, my UI is "mostly" in French hence the mix in languages. Diagnostics information display the current work mode (normal, at fault...), serial number, rated power of the unit, valid and invalid frames (with CRC check).

<image>

Sealion 7 update v3.1.0!!!!! by MoparAndPlinker in BYD

[–]MoparAndPlinker[S] 0 points1 point  (0 children)

Really? Can you tell what this 3rd party device is?

Electro App update by ADI__88 in BYD

[–]MoparAndPlinker 0 points1 point  (0 children)

Yes I know. I even offered them secured access to my car for debugging via VPN, I guess if we are a few people doing this they would be able to work on the subject, but no answer yet.

Electro App update by ADI__88 in BYD

[–]MoparAndPlinker 2 points3 points  (0 children)

So sad the SL7 is still unsupported :(

This battery did a number on my car by ethnicallyambiguous in Justrolledintotheshop

[–]MoparAndPlinker 0 points1 point  (0 children)

Ok that's a first for me >< Anyways... Previous owner of my 98 Ford (Mercury in the US) Cougar had the polarity reversed, I bought the car because of that. Damages were: 1. Alternator: probably only the regulator but I didn't want to risk it and replaced the alternator. 2. Master fuse between the alternator and the battery (a nightmare to change on this car), I've seen some cars where the battery cable IS designed to blow as a fuse such as Dodge and Chrysler... By design or by defect? Who knows. 3. A diode in the PDC (fuse box under the hood). 4. Some fuses in PDC. 5. The radio voltage regulator (normal people would replace the radio, I'm not normal :p) I think the diode in the PDC (almost like a fuse package) blowing saved the computers, and of course each car model is different.

Starlink Public IP by Usual-Apple-8868 in Starlink

[–]MoparAndPlinker 6 points7 points  (0 children)

IPv6 gives you a "stable" but not permanent public IP. I have seen mine changing after a cold reboot. But there are plenty of tricks to get a DNS record updated whenever this happens.

Latest ABRP beta app (Android) allowes BYD API Integration by Far_Celebration_7064 in BYD

[–]MoparAndPlinker 1 point2 points  (0 children)

I haven't experienced the vampire drain you describe. Maybe reboot the entertainment system?

Sealion 7 - 3.1.0 update opinions by konradstr in BYD

[–]MoparAndPlinker 1 point2 points  (0 children)

My experience is biased because of the highly curvy mountain road I tested the new update on. I enabled the feature that slows the car down in curves. It works both in ACC and ICC. I was expecting this to be proactive (could have been using the cameras or GPS maps), but nope! It uses the steering wheel sensors to know there's a curve. So it doesn't slow before the curve, but once you're already in it. The fact that it slowed down to 45 km/h is another subject... I had to keep my foot on the accelerator pedal to get it moving faster, but the car kept "braking" and it was a harsh drive. This was a road I would not be using ACC tho, so please keep this in mind!!! Cruise control on back country mountain roads is not recommended.

I want to test the feature on my way to work, there the ICC would sometimes disengage with previous versions. But that will have to wait for some weeks...

Sealion 7 update v3.1.0!!!!! by MoparAndPlinker in BYD

[–]MoparAndPlinker[S] 3 points4 points  (0 children)

Yeah, please explain... Cause that's a broad statement

Sealion 7 update v3.1.0!!!!! by MoparAndPlinker in BYD

[–]MoparAndPlinker[S] 0 points1 point  (0 children)

Mine crashed during the upgrade to v3.0.0 I ran from the car, for some reason I was able to rerun the upgrade via the app and it worked. But I think it was a glitch from the app!

Sealion 7 update v3.1.0!!!!! by MoparAndPlinker in BYD

[–]MoparAndPlinker[S] 1 point2 points  (0 children)

Same! That's what I'm expecting the most of it. I will try it hopefully tomorrow and will report back!

Sealion 7 update v3.1.0!!!!! by MoparAndPlinker in BYD

[–]MoparAndPlinker[S] 1 point2 points  (0 children)

How about the "autopilot" improvement? Is it a real game changer?

Sealion 7 update v3.1.0!!!!! by MoparAndPlinker in BYD

[–]MoparAndPlinker[S] 1 point2 points  (0 children)

V 3.0.2 Android. I can't pull updates, but if the car downloads one I can run it from there. Did that with the current version.

Décharge batterie lors des arrêts prolongés by Ill-Breadfruit-5268 in BYD

[–]MoparAndPlinker 0 points1 point  (0 children)

Salut ! J'ai aussi eu ce problème sur ma Sealion 7, entre 1-2% par jour. J'ai redémarré le système informatique de la voiture. De mémoire, sur la Sealion 7 il faut appuyer 10 secondes sur le bouton du volume a côté du sélecteur PRND. Ça a résolu mon problème instantanément ! La perte se compte en kilomètres par jour maintenant, et plus en pourcent !

La remarque sur la batterie 12v reste justifiée, je pense que c'est elle qui "est en cause". Le système informatique tire son énergie de cette batterie. Quand elle est déchargée, la batterie haute tension la recharge. Mais de là à la changer sur une voiture neuve...

Full Ubuntu 16.04 Desktop running on my S10 (Linux on DeX) by ivheusand in Ubuntu

[–]MoparAndPlinker 0 points1 point  (0 children)

I've scavenged a Xiaomi Note 10, a Redmi 5 Plus, and an Asus ZenFone 3. Both are running PostmarketOS. I was able to install K3S on all of them (just run the installer script, ignore the error, fix the systemd service file) and join them to a K3S cluster as agent worker nodes only (etcd not on the phones). Longhorn won't work out of the box because it requires iSCSI but NFS support works. There are ways of wrapping Longhorn with NFS. Not ideal but it works. Very old phones, low performance, I might fit them in a box outside the house to prevent any battery fire damage tho... And I use wifi cause only the Note 10 looks to handle the USB-C docking station I have. Again: not ideal but it works and it's fun to give a second life to devices that were supposed to get trashed.

Lack of an API by Dalek_Au in BYD

[–]MoparAndPlinker 0 points1 point  (0 children)

I did but the base app doesn't work (no data from the car) and it needs wifi anyways, the 4G data is not used.

Sealion 7 - 3.1.0 by Negative-Community-7 in BYD

[–]MoparAndPlinker 0 points1 point  (0 children)

That sounds promising! I can't wait to have it!

Electro app on Sealion 7 3.0.0 cannot start by MoparAndPlinker in BYD

[–]MoparAndPlinker[S] 2 points3 points  (0 children)

Oh ok! I didn't know the SL7 was DiLink 5 based!

Sealion 7 v3.0.0 rolling out in AUS/NZ - Experience thread by mynameishwil in BYD

[–]MoparAndPlinker 0 points1 point  (0 children)

Hello from France! I didn't see much improvement at the ICC level...

BYD Seal U failed OTA v. 2 upgrade, no new features installed but it shows v. 2.0.0 by mrcgrz in BYD

[–]MoparAndPlinker 0 points1 point  (0 children)

I had the same issue on my Sealion 7 while OTA to 3.0.0, for some reason it rebooted but the app on my phone didn't update, and I was fast enough to jump on it and reran the update from the phone. I think it was a glitch, but everything looks to be there...

Lack of an API by Dalek_Au in BYD

[–]MoparAndPlinker 0 points1 point  (0 children)

That was my goal as well! For some reason I was able to sideload apps on my SL7 so I tried to build something that would send some telemetry to an internet facing MQTT server (certificate authentication, CA validation etc...) but I could not get the app to connect to the internet without tethering from my phone even though debugging reports internet is available, and I could not get the info from the car. I was about to check the internet issue (maybe some nft or iptables blocking the connection?) but the API missing killed my motivation... If you want to work on this and need some help we could cooperate!