I’ve just bought and connected to it a JetKVM, when I saw an RJ11 port, I thought that it could have been used to “push” those buttons, but instead it’s a serial port ☹️
Sorry, I’ve missed your reply.
No, I haven’t integrated any of them into HA; what is your need for such integration?
I’ve only exposed a Node Red webook: Node Red receives coordinates from my car/smartphone/something else and distributes them to Traccar and Dawarich.
I think that I"lol go this way, thanks.
I don’t have transistors, but I have a 2 relay Ethernet board.
It depends, usually just some minutes, but during the summer it could be more.
I’d like (the ideal result) to find a way that just works in any case.
Totally agree.
They could be the stars of their repository
Modbus problem - Lemmy.World
In the office we have an automation system that talks in modbus. Right now I
have Node Red that receives data from modbus (via IP), sends it to MQTT and send
messages from MQTT to modbus. In HA I have 15 MQTT climates that works. I want
to bypass Node Red; I’ve added an automation that gets triggered when a MQTT
values arrives and sends the new value to mobus: alias:
Climate_update_modbus_setpoint_studio1 description: "" triggers: - trigger: mqtt
topic: home_assistant/thermostat/setpoint/Studio1 actions: - data: hub: picnet
address: 1099 value: "{{ (trigger.payload | float * 10) | int }}" action:
modbus.write_register mode: queued The problem is that the modbus change takes a
lot. - I change the climate setpoint, after about 0.5 seconds the MQTT value
changes and the automation gets triggered - the modbus register changes in a
range of about 0.5-3 seconds - sometimes the automation gets triggered and I see
the trigger bar yellow instead of blue and the modbus register changes after
longer With Node Red I have no problem with modbus. What can I check to try to
find the source of the problem?
Negative, it’s “just” an HP Elitebook with a PCIe SFP+ board.
Only through SFP+
I think that the only option would be to add a second NiC.
Thanks!
I did think about that option, but the onboard NIC is connected to the ONT (fiber connection) and the SFP+ is off when the server is off so it can’t receive WOL packets.
By the way, thanks.
UPS: how to turn the server back on?
https://lemmy.world/post/33100642
UPS: how to turn the server back on? - Lemmy.World
I’ve installed an APC BX950MI-GR and connected it to my Proxmox server via USB.
It works: it turns off the server after x minutes after the power loss and it
turns itself off after other x minutes, when the powers come back on, the UPS
turns on and so does the server. The problem is if the power comes back after
the server receive the power off signal and before the UPS powers off, in this
case the UPS simply goes back in the normal state and the server…stays off. How
can I turn it back on? Thanks!
