Nouveau : le pare-feu IA surveille toute la plateforme et explique chaque incident en termes simples. Découvrez comment ça marche

David Patel

davidp11

@david-patel · Membre depuis mars 2025

Nouveau

Facility manager · hospitality · new to IoT

Sujets
8
Réponses
62
Points
0
Nouveau10 points pour Membre

Toutes mes réponses sur les forums

15 sujets de 46 à 60 (sur un total de 62)

Traduit de English par IA ·

C’est peut-être une question bête, mais pourquoi ne pas simplement mettre le Wi-Fi une seule fois dans le code, si c’est le même campus ?

♥ 0

I did a lot of lighting retrofits at the hotels before I touched any IoT, so this one I know.

Get a constant current buck module with a dim input. The cheap ones built around a PT4115 cost a couple of dollars, come in 700 mA versions (or set by a sense resistor), take 12 to 24 V and have a DIM pin. A Mean Well LDD-700H is the nicer branded one. Feed it 12 V, LED on the output, and your ESP8266 PWM pin straight into DIM. 3.3 V PWM is enough for both of those. Around 1 kHz PWM, no flicker you can see, the driver keeps the current flat as the LED heats up.

On the Hermetry side: add a command like light.set with a number parameter to the profile’s catalog as a Basic command, then a Slider control card that runs it. The slider sends once when you let go, not while dragging. For a light I switch off Ask before running, otherwise the shift lead gets a confirm box every time. Bind the current value to what the ESP reports back (I send light.level after each change), so the slider shows what the light is really doing. Control cards walks through it.

Solution acceptée♥ 7

I’m still learning this stuff, but I set up the same kind of alarm for the pool chemistry at our hotel, so I can do the second half.

There’s no « between » in alarm conditions, you write it as a group. The form does one comparison per severity, so switch the rule to JSON mode:

"severities": [
{ "severity": "MAJOR",
"condition": { "any": [
{ "key": "ph", "op": "<", "value": 5.5 },
{ "key": "ph", "op": ">", "value": 6.5 } ] } }
],
"debounce": { "mode": "duration", "raise": 300, "clear": 60 },
"hysteresis": 0.1

The duration debounce is what stops the dosing dip. The condition has to be true for 300 seconds by the device’s own timestamps before the alarm opens. Our chlorine dose dip lasts about two minutes, so 5 minutes was safe. Since you report every 30 s that’s ten readings in a row, plenty.

Hysteresis 0.1 means it clears at 5.6 or above on the low side, 6.4 or below on the high side, so it doesn’t flap at the edge.

All of this is on Alarm conditions reference, and the debounce part on the page next to it.

Solution acceptée♥ 4

Traduit de English par IA ·

Le chiffrement du fournisseur de la carte SIM ne couvrirait-il pas cela ? Je pensais que les réseaux mobiles chiffraient de toute façon tout ce qui transite par l’air.

♥ 2

Running on 2 robots since last week. The 6 dB rule was necessary, without it the zone flickered every few seconds in the lift lobby. The kitchen alarm fired once already, a cleaner took a wrong turn after a map update on the robot, and housekeeping caught it in a minute. Still would like the request though, doing it in every robot’s firmware is work.

♥ 0

Traduit de English par IA ·

Tyler, c’est parfait. Je lui ai montré la page Residency (nous sommes aux États-Unis, aucune exigence de résidence n’est définie) et il s’est beaucoup calmé quand il a vu l’export ainsi que la route API d’historique. Il veut que ton idée de CSV mensuel devienne une tâche récurrente, donc je suppose que c’est mon prochain projet. Je ne reparle plus de l’histoire de Docker, mdr.

♥ 0

Traduit de English par IA ·

Une image Docker le rendrait très heureux. Où pourrais-je la trouver ? J’ai regardé sous Paramètres et je ne vois que Residency, Data Export et le reste habituel.

♥ 0
15 sujets de 46 à 60 (sur un total de 62)