Possible to extend integration for the Automatic Watering System?

[auzroz]

Wondering if you're familiar with how much effort it would be to extend this integration to include the Automatic Watering System here: https://letpot.com/products/smart-drip-irrigation-kit

[jpelgrom]

I'm not familiar with it, but looking at the decompiled app code I have it looks similar from a technical point of view (see below).

Extending the integration (assuming you mean the Home Assistant integration this library was written for) is another question and one I'm less likely to tackle, because:

• I do not have the device to test with it or a similar device. There is one screenshot of the app in the manual but does that match what is currently in the app?
• It supports both Bluetooth and Wi-Fi, that's something else to check. Do both transports support the same features? What happens when switching it? If everything is the same Bluetooth should be preferred in my opinion as it is local, but that's new for this library.

Decompiled app code examples

It also needs to convert a hex message to get status information:

_setOverallState(e) {
    this.wifi.state = e[6], this.system.state = e[7], this.pump.on = 1 === e[8], this.pump.mode = e[9], this.pump.duration = 256 * e[10] + e[11], this.pump.countdown = yi(e.slice(12, 16)), this._startCountdownTimer(), this.pump.cycle.on = 1 === e[16], this.pump.cycle.duration = 256 * e[17] + e[18], this.pump.cycle.workingDuration = 256 * e[19] + e[20], this.pump.cycle.mode = e[21], this.pump.cycle.workingInInter = 256 * e[22] + e[23], this.pump.cycle.restInInter = 256 * e[24] + e[25];
    const t = -yi(e.slice(27, 31));
    this.pump.works.latest = {
        reason: e[26],
        time: t
    };
    const i = yi(e.slice(31, 35));
    n("log", "at libs/device/device-type/ise05-device.ts:120", "[device-ise05] nextTime", i, e.slice(31, 35)), this.pump.works.next = {
        reason: null,
        time: i
    }
}

It also toggles switches by writing the entire device state, replacing the switch value with the new state (it also fetches the device state here after writing, not sure if that is required or if the device does not push updates!):

async switchPump(e) {
    n("log", "at libs/device/device-type/ise05-device.ts:184", "[device-ise05] switch pump", e);
    const t = this._constructInstruction(),
        i = e ? 1 : 0;
    t[2] = i;
    const s = 1 === (await this._request(t))[6];
    return s && (this.pump.mode = i), setTimeout((() => {
        this.getOverallState()
    }), 1e3), s
}

[PaleoW]

I'd really appreciate support for the watering system as well. Is there anything a device owner could do to help ?

[DrMurx]

@jpelgrom I agree that local Bluetooth support would be nice, but I'd argue a simple support (turning pump on and off) via Wifi and LetPot's cloud service would already help most of the owners of this device.

I'll try to help and experiment with the API, since I've just acquired one. However, mine shows up as "ISE06". So if you could check the app sources for references to ise06-device.ts to understand whether its data field has different content than the ISE05.

The app has a massive delay (3-4 seconds) after turning on and off the pump before the UI is eventually updated, so this aligns with the observation in switchPump that there is no push, but the app has to fetch the state in the setTimeout.

[jpelgrom]

So if you could check the app sources for references to ise06-device.ts to understand whether its data field has different content than the ISE05.

After decompiling unfortunately I only get one giant JS file with ~60k lines after applying some basic formatting. However text search helps and I know where to look by now :) The major difference with ISE05 seems to be that the state also includes this.pump.cycle.skipWater = Math.floor((256 * e[35] + e[36]) / 60);, otherwise it matches.

Are you familiar with how to run Python code? I could quickly throw the state parsing/pump switch into a converter and provide you with code to test if it works at all.

[DrMurx]

After decompiling unfortunately I only get one giant JS file with

That's clear, and it's minified, at least partially. But they've kept the logging information including the original TypeScript, so you'd still get some references.

Are you familiar with how to run Python code?

I am. Although I still need to setup my LetPot - I just went down the rabbit hole of connecting it to my home automation before I even connected all my plant pots...

I could quickly throw the state parsing/pump switch into a converter and provide you with code to test if it works at all.

That would be much appreciated.

[jpelgrom]

Could you run the Python code from the following branch and see if you can 1) manually get a status update from the device and 2) if the device pushes new statuses when something changes by pushing buttons on the device or in the app? You can use the example code from the readme. https://github.com/jpelgrom/python-letpot/tree/ise0x-device-support

Sorry for the delay.

[DrMurx]

@jpelgrom No worries about the delay. I much appreciate your work here and don't take it for granted.

This looks quite promising. I've successfully tested:

1. There is no push from the server. subscribe(lambda status: print(status)) doesn't do anything unless a status is actively requested with get_current_status() or as a response to other commands.
2. Retrieving the current status with get_current_status() works. It aligns with the settings and status values in the app.
3. Changing settings and controls in the app works, as the changes are reflected in the results of get_current_status() with a delay of 0.5 to 1 seconds.
4. Turning the pump on and off using set_pump_mode(...) works as expected. In get_current_status(), both the pump_mode control and the pump_on status flag are changing accordingly with a delay of 0.5 to 1 seconds.
5. To test whether the other controls work, I've added device_client.set_pump_cycle_on() which sets pump_cycle_on. The new settings is correctly reflected in the app and the device behaves accordingly.

It's worth noting that changing the pump_cycle_on value will also start the pump cycle immediately. This is consistent with the behavior in the app and seems to be intended behavior.

Let me know if I should test something else, but so far it LGTM.

[jpelgrom]

Thanks for testing, that sounds promising. I'll start making the code a bit more polished then and hopefully merge it soon.

If I understand correctly, the device can also be controlled via Bluetooth. If you 'switch' it to Bluetooth, does control via the server continue working or does it break?

1. There is no push from the server. subscribe(lambda status: print(status)) doesn't do anything unless a status is actively requested with get_current_status() or as a response to other commands.

or as a response to other commands: which commands do you mean? Does it respond with/push the updated status after sending a command for changing settings?

[DrMurx]

If I understand correctly, the device can also be controlled via Bluetooth. If you 'switch' it to Bluetooth, does control via the server continue working or does it break?

If the device is switched to "Bluetooth" in the app, it seems to disconnect from the server.

The server will still enumerate it, but it's shown as offline (LetPotDevice(serial_number='ISE06XXXX', name='ISE06 XXXX', device_type='ISE06', is_online=False, is_remote=False)). Also, a call to get_current_status() stalls.

which commands do you mean? Does it respond with/push the updated status after sending a command for changing settings?

I was making wrong conclusions here, so ignore what I wrote before.

The server does actively push MQTT messages after a status change. I can confirm this happens regardless whether a status change is done in the app or via Python code. It just takes approx. 0.5 to 1 seconds before the server messages arrive.

This code turns on the pump for 5 seconds and prints 3 status updates. The initial asyncio.sleep(1) is required to wait for a status update from the server, as triggered by await device_client.request_status_update().

async def main():
    async with aiohttp.ClientSession() as session:
        client = LetPotClient(session)

        auth = await client.login("email@example.com", "password")
        # store auth for future use, and use in constructor

        devices = await client.get_devices()
        print(devices)

        device_client = LetPotDeviceClient(auth, devices[0].serial_number)
        await device_client.subscribe(lambda status: print(status))
        await device_client.request_status_update()

        # this sleep is mandatory, otherwise _get_publish_status doesn't have a status and throws.
        await asyncio.sleep(1)

        await device_client.set_pump_mode(True)
        await asyncio.sleep(5)

        await device_client.set_pump_mode(False)
        await asyncio.sleep(1)

        print("Disconnect")
        device_client.disconnect()

The request_status_update and the subsequent asyncio.sleep(1) can be replaced by a call to await device_client.get_current_status(). There (and only there) you've added extra logic with the self._status_event to allow the method to wait for the asynchronous server response. I wonder a similar logic could be beneficial for set_pump_mode() as well. With its async nature it would make sense that its future only resolves once a successful update to the status has been received.

[gule002]

Tried a few variations to no avail based on the code in the PR.

2025-06-18T00:50:36.892-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] ---> POST https://api.letpot.net/app/devices/ISE06B4BD HTTP/1.1
2025-06-18T00:50:36.892-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] Accept: application/json
2025-06-18T00:50:36.892-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] Accept-Language: en-US
2025-06-18T00:50:36.892-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] app-version: 3.5.0
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] Authorization: xxxxx
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] client_id: letpot-app
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] Connection: keep-alive
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] Content-Length: 73
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] Content-Type: application/json
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] dev_channel: tuya
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] dev_lang: en
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] uid: 684de4b55278293fcfb52ef4
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] User-Agent: LetPot/3.5.0 (iPhone; iOS 17.0.0; Scale/3.00)
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] x-app-id: letpot_ios
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] x-app-version: 3.5.0
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand]
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] {"duration":5,"dps":[65,2,1,0,0,5,0,0,0,0,0,0,0,0,0],"command":"turn_on"}
2025-06-18T00:50:36.893-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] ---> END HTTP (73-byte body)
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] <--- HTTP/1.1 409 Conflict (43ms)
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] access-control-allow-origin: *
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] connection: keep-alive
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] content-length: 82
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] content-type: application/json
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] date: Wed, 18 Jun 2025 04:50:36 GMT
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand]
2025-06-18T00:50:36.936-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] {"ok":false,"status":409,"message":"Please update the App to the latest version."}
2025-06-18T00:50:36.937-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendCommand] <--- END HTTP (82-byte body)
2025-06-18T00:50:36.937-04:00 ERROR 52175 --- [io-8080-exec-10] c.deeralarm.client.LetPotErrorDecoder : LetPot API error - Method: LetPotApiClient#sendCommand(String,String,String,Map), Status: 409, Headers: {access-control-allow-origin=[], connection=[keep-alive], content-length=[82], content-type=[application/json], date=[Wed, 18 Jun 2025 04:50:36 GMT]}, Body: {"ok":false,"status":409,"message":"Please update the App to the latest version."}
2025-06-18T00:50:36.937-04:00 ERROR 52175 --- [io-8080-exec-10] c.deeralarm.client.LetPotErrorDecoder : LetPot API returned conflict error. This may indicate a version mismatch or incompatible request format.
2025-06-18T00:50:36.937-04:00 WARN 52175 --- [io-8080-exec-10] com.deeralarm.service.LetPotService : Failed to send command using primary endpoint: LetPot API returned conflict error: {"ok":false,"status":409,"message":"Please update the App to the latest version."}
2025-06-18T00:50:36.937-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] ---> POST https://api.letpot.net/app/devices/ISE06B4BD/control HTTP/1.1
2025-06-18T00:50:36.937-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] Accept: application/json
2025-06-18T00:50:36.937-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] Accept-Language: en-US
2025-06-18T00:50:36.937-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] app-version: 3.5.0
2025-06-18T00:50:36.937-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] Authorization: xxxx
2025-06-18T00:50:36.937-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] client_id: letpot-app
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] Connection: keep-alive
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] Content-Length: 73
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] Content-Type: application/json
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] dev_channel: tuya
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] dev_lang: en
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] uid: 684de4b55278293fcfb52ef4
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] User-Agent: LetPot/3.5.0 (iPhone; iOS 17.0.0; Scale/3.00)
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] x-app-id: letpot_ios
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] x-app-version: 3.5.0
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand]
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] {"duration":5,"dps":[65,2,1,0,0,5,0,0,0,0,0,0,0,0,0],"command":"turn_on"}
2025-06-18T00:50:36.938-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] ---> END HTTP (73-byte body)
2025-06-18T00:50:36.956-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] <--- HTTP/1.1 404 Cannot find any route matching /app/devices/ISE06B4BD/control. (18ms)
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] access-control-allow-origin: *
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] connection: keep-alive
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] content-length: 87
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] content-type: application/json
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] date: Wed, 18 Jun 2025 04:50:36 GMT
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] x-is-custom-error: Yeah
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand]
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] {"ok":false,"message":"Cannot find any route matching /app/devices/ISE06B4BD/control."}
2025-06-18T00:50:36.957-04:00 DEBUG 52175 --- [io-8080-exec-10] com.deeralarm.client.LetPotApiClient : [LetPotApiClient#sendControlCommand] <--- END HTTP (87-byte body)
2025-06-18T00:50:36.957-04:00 ERROR 52175 --- [io-8080-exec-10] c.deeralarm.client.LetPotErrorDecoder : LetPot API error - Method: LetPotApiClient#sendControlCommand(String,String,String,Map), Status: 404, Headers: {access-control-allow-origin=[], connection=[keep-alive], content-length=[87], content-type=[application/json], date=[Wed, 18 Jun 2025 04:50:36 GMT], x-is-custom-error=[Yeah]}, Body: {"ok":false,"message":"Cannot find any route matching /app/devices/ISE06B4BD/control."}
2025-06-18T00:50:36.960-04:00 ERROR 52175 --- [io-8080-exec-10] o.a.c.c.C.[.[.[.[dispatcherServlet] : Servlet.service() for servlet [dispatcherServlet] in context with path [/api] threw exception [Request processing failed: feign.FeignException$NotFound: [404 Cannot find any route matching /app/devices/ISE06B4BD/control.] during [POST] to [https://api.letpot.net/app/devices/ISE06B4BD/control] [LetPotApiClient#sendControlCommand(String,String,String,Map)]: [{"ok":false,"message":"Cannot find any route matching /app/devices/ISE06B4BD/control."}]] with root cause

[jpelgrom]

Tried a few variations to no avail based on the code in the PR.

Not sure what you're doing, but that is not this library's code, the PR code, and also doesn't resemble how it works.

[gule002]

The logs show captured traffic using some Java translation of the code you have here.

It would be good if we can get some traffic logs or protocol details (API docs) so we an build integrations into LetPot.

[jpelgrom]

I cannot support translations/other libraries - and it also looks incorrect (there is no REST API for control as far as I know, definitely nothing like it in this library). Documentation would be nice but I don't have it, this is reverse engineering for a reason. Let's keep this issue focused on the original subject.

[DrMurx]

@jpelgrom Anything more I can do to support you moving forward? More tests to be done?

[jpelgrom]

Anything more I can do to support you moving forward? More tests to be done?

Hey, just that comment to know someone is waiting for it is enough for now :) I wanted/needed to make other changes because of performance concerns and then got distracted by other things, so this is a good reminder to pick it up again. I'll come back with more questions and testing soon.