Novedad: el cortafuegos de IA supervisa toda la plataforma y explica cada incidente con palabras sencillas. Vea cómo funciona

David Patel

davidp11

@david-patel · Se unió el marzo 2025

Recién llegado

Facility manager · hospitality · new to IoT

Temas
8
Respuestas
62
Puntos
0
Recién llegado10 puntos para Miembro

Respuestas de foro creadas

Viendo 15 entradas – de la 46 a la 60 (de un total de 62)

Traducido del English por IA ·

Quizás sea una pregunta tonta, pero ¿por qué no poner el Wi-Fi en el código una sola vez, si todo está en el mismo 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.

Solución aceptada♥ 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.

Solución aceptada♥ 4

Traducido del English por IA ·

¿No cubriría eso el cifrado del proveedor de la SIM? Pensaba que las redes móviles cifran todo por el aire de todos modos.

♥ 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

Traducido del English por IA ·

Tyler, esto es perfecto. Le enseñé la página de Residency (somos de EE. UU., no hay ningún requisito de residencia establecido) y se tranquilizó mucho al ver la exportación y la ruta de la API de historial. Quiere que tu idea del CSV mensual sea una tarea fija, así que supongo que ese es mi próximo proyecto. No volveré a mencionar lo de Docker, jaja.

♥ 0

Traducido del English por IA ·

Una imagen de Docker lo haría muy feliz. ¿Dónde la encontraría? Miré en Configuración y solo veo Residency, Data Export y lo de siempre.

♥ 0
Viendo 15 entradas – de la 46 a la 60 (de un total de 62)