sorted by: new top controversial old
Do I need https on everything in c/selfhosted@lemmy.world
Help an idiot protect his homelab and few services exposed to the internet. in c/selfhosted@lemmy.world
Alltrails alternative in c/opensource@lemmy.ml
Creator of free Adobe clones unveils open-source Microsoft Office Excel, PowerPoint, and Word replications — Autodesk tools and other subscription-based services may come next in c/opensource@lemmy.ml
Alltrails alternative in c/opensource@lemmy.ml
ha-iroh: p2p Android app for Home Assistant, garage door from the power menu, no port forward / VPN / cloud in c/homeassistant@lemmy.world
[–] 2 points 4 weeks ago

Cool! I'll try this. bout the garage door, I'd like to tell you how I do it: a car tracker (Teltonika FMB120 for about 45€), a small push button under the steering wheel, when I push it, it does a curl request to my Node Red instance that, based on the car location, opens the gate of my home, or office or parents. Bonus: the FMB120 can connect to the CAN bus and you can get some telemetry and you can also always locate your car (I use Traccar). It does need a data SIM card, but with 1NCE, you can get one that lasts 10 years and it only costs 10€ (not per month, not per year, for the whole 10 years.)

  • permalink
  • fedilink
  • source
    •
    Creator of free Adobe clones unveils open-source Microsoft Office Excel, PowerPoint, and Word replications — Autodesk tools and other subscription-based services may come next in c/opensource@lemmy.ml
    Would love to find some kind of rating in Fdroid in c/opensource@lemmy.ml
    6
    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?

    1
    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 gets turned off by the command upsdrvctl shutdown, 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!