New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

erdems98

erdems98

@erdem_s98 · Joined August 2025

Newcomer

Veri analisti · su ve atık su · sahada 17 yıl

Topics
2
Replies
8
Points
0
Newcomer10 points to Member

Forum Replies Created

Viewing 8 posts – 1 through 8 (of 8 total)

Translated from Türkçe by AI ·

With the complementary filter the delay has almost disappeared, and the team had already found an MPU6050 anyway. We also did the calibration and the left-right difference is gone. Doing last on the graph also got rid of the 180 nonsense. It was good that I read this post before trying Hakan Bey’s suggestion 🙂

♥ 2

Translated from Türkçe by AI ·

Yes, it’s the average of the last 20 readings. At 10 Hz it takes 2 seconds.

♥ 1

Translated from Türkçe by AI ·

The child gets the command, and the spot you’re stuck on is the ESP32 side. A command sent to a device behind the gateway comes down to the gateway over v1/gw/rpc, and shared attribute changes come over v1/gw/attributes. Your code most likely only listens on v1/rpc/req/+, which is for the gateway’s own commands. That’s why the command stays in Sent. I got stuck in the same place with the water stations too.Here’s what I did:

  1. Added the light.set command to the dimmers’ profile (not the gateway’s), Basic tier, parameter level (Number, 0-100).
  2. On the slider card: Run a command: Device = atolye-3 child, Command = light.set, for level The control’s value. I convert the 0-100 slider to 0-255 on the ESP32 side.
  3. Bound the Current value slot to the level telemetry of the same child, so the card shows the dimmer’s real value.
  4. For the light I turned off Ask before running, so it doesn’t ask for confirmation on every slide.

On the ESP32 side, after every connection, subscribe to v1/gw/rpc. Print the incoming message to the serial port first and look at its structure, then work out which child it’s for from there and do the BLE write:

mqtt.subscribe("v1/gw/rpc", 1);

void onMsg(char* topic, byte* payload, unsigned int len) {
  if (strcmp(topic, "v1/gw/rpc") == 0) {
    Serial.write(payload, len);   // önce yapıya bak
    Serial.println();
    // child adını ve level'ı çöz:
    // bleSetLevel(name, map(level, 0, 100, 0, 255));
  }
}

The control card rules are here: Kontrol kartları

Accepted solution♥ 5

Translated from Türkçe by AI ·

+1. The default validity period of the key is 90 days, put it in your calendar, otherwise the page will silently come up empty after three months.

♥ 0

Translated from Türkçe by AI ·

Forget the port: if you put the device token on the page, anyone who views the page source can publish data in your device’s name with that token. Greenhouse temperature shows 80 degrees, your mom freaks out 🙂 Take the token out of there.

♥ 1

Translated from Türkçe by AI ·

The calculation clarified things a lot, thanks. I built the one by the window with a 0.5 W panel + 1 F supercap + BQ25570, it’s been two weeks without a battery, supercap_v doesn’t drop below 3.9 at night. On the others I switched to NTP + hourly batch sending, and the slope of battery_v fell from 25 mV per day to 6 mV per day. I buried the idea of the beehive and the washing machine 🙂

♥ 0

Translated from Türkçe by AI ·

The clock is not synchronised, but I don’t use NTP at all. I read somewhere that making up ts values is forbidden.

♥ 0
Viewing 8 posts – 1 through 8 (of 8 total)