<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[New Adapter] Omoda&#x2F;Jaecoo Vehicles]]></title><description><![CDATA[<p dir="auto">Hi all,</p>
<p dir="auto">I'd like to introduce a new adapter I've been working on: ioBroker.omoda – it brings Omoda / Jaecoo (Chery) cars into ioBroker, using the same cloud backend as the official Omoda / Jaecoo smartphone app.</p>
<p dir="auto">What it does</p>
<p dir="auto">Status – doors, windows, sunroof, central lock, engine, climate running, tyre pressures &amp; temperatures<br />
Location – GPS latitude/longitude, speed, heading<br />
Battery &amp; charging – state of charge, electric/total range, charge state, charging power, plug connected, remaining charge time<br />
Odometer<br />
Remote commands – lock / unlock, climate on/off with a settable target temperature, request GPS location, and "wake &amp; refresh full status"<br />
Each vehicle on the account (owner or delegated) is created as its own device (omoda.0.&lt;VIN&gt;.*).</p>
<p dir="auto">Requirements</p>
<p dir="auto">An Omoda / Jaecoo account that has the vehicle associated, plus the account email and command PIN<br />
Login is via a one-time code (OTP) emailed to you, handled in the adapter's admin settings<br />
Defaults target Europe; other regions are configurable<br />
Tip: consider using a delegated second account for the adapter – logging in with the same account here and in the official app makes the two repeatedly log each other out.</p>
<p dir="auto">Known limitations / planned<br />
Individual seat heating/ventilation, defrosters, EV charge start/stop and scheduled charging, windows/sunroof/trunk control, and the theft alarm are not wired up yet – they're planned for a later version. Many values read empty while the car is in standby and update while driving, charging, or after a manual "refresh".</p>
<p dir="auto">Important notes<br />
This adapter is unofficial and reverse-engineered – it is not affiliated with, endorsed by, or connected to Omoda, Jaecoo or Chery. Use it at your own risk and only on your own vehicle. A wrong command PIN entered repeatedly can lock the account, so the adapter deliberately stops after a couple of failed attempts.</p>
<p dir="auto">It is a port of the excellent Home Assistant integration omoda-jaecoo-ha by Caslinovich and JackRonan – all the hard reverse-engineering is theirs, and they're credited in the README and LICENSE. Please support the upstream project too.</p>
<p dir="auto">Links</p>
<p dir="auto">GitHub: <a href="https://github.com/AlanSRU/ioBroker.omoda" rel="nofollow ugc">https://github.com/AlanSRU/ioBroker.omoda</a><br />
npm: <a href="https://www.npmjs.com/package/iobroker.omoda" rel="nofollow ugc">https://www.npmjs.com/package/iobroker.omoda</a><br />
Install for testing via the admin "install from URL/npm" (iobroker.omoda). A PR to add it to the latest repository is open.</p>
<p dir="auto">I'd be very grateful for testers – especially anyone with a different model or in a non-UK region – and any feedback or issue reports. Thanks!</p>
]]></description><link>https://forum.iobroker.net/topic/85006/new-adapter-omoda-jaecoo-vehicles</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Jul 2026 22:40:57 GMT</lastBuildDate><atom:link href="https://forum.iobroker.net/topic/85006.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 18 Jul 2026 10:43:42 GMT</pubDate><ttl>60</ttl></channel></rss>