CondorWonder @ CondorWonder @lemmy.ca

Posts

0

Comments

74

Joined

2 yr. ago

Yes, the packet passes through routers at each stage and they direct the packet to the ‘closest’ path based on its destination, until the final router has the destination on its network. This can happen a few times (for something in your ISP network), or 10-30+ times for something further away.

I'm using project boxes from Amazon, like these: https://a.co/d/4R4Dtv5 before I had a 3d printer to make something bespoke. Some of the boxes have the ESP board glued down, some it’s loose. It works well enough and doesn’t look too bad. I still use them now as it’s easier to throw everything into a box instead of designing something specific to the project.

Then to link the entities together into a device you need to mimic the auto discovery, or you just have two split entities.

I suppose you could create a template entity with the battery as an attribute to see it in the details view, but you still need the entities with the raw data. I’d be more inclined to create the device with auto discovery, seems like a cleaner way to go.

Zigbee2mqtt should do device auto discovery by default (it did for me and I didn’t have to do anything). Maybe you’ve turned something off? The alternative I can think of is to manually create and maintain device auto discovery records like https://stevessmarthomeguide.com/adding-an-mqtt-device-to-home-assistant/ shows (for example).

Try searching for your automation.entity_id - like in my case it’s something like automation.notify_washer_done (the original entity id of my automation, found via the developer - states tab). Then if I search using that in my YAML I’d see entity_id: automation.notify_washer_done, and add the context to see the full service call:

        service: automation.turn_on
    target:
      entity_id: automation.notify_washer_done
    data: {}


  

Assuming it’s an automation or script your should find it in the related .yaml file and can scroll up to see the actual automation or script source.

Turned off or Turned on is the disable or enable action. If it’s changed by something in HA it should show what the trigger was too (like a user or other automation).

Here’s an example - it shows the automations that enabled our disabled this automation, and their trigger.

To prevent the automation from being changed you can rename it, that should break anything automatic that’s changing it. You can also try to chase down what’s changing it from logs (once renamed you should start seeing errors in your HA log file), or by searching for the entity_id in your yaml configuration files.

I use an Emporia Vue device, it uses an ESP32 internally and you can find instructions on how to flash it with esphome code onto it. No cloud dependency, just wifi.

You can get various kits for one/two/three phase mains, and monitor up to 16 individual circuits via passive current clamps.

I have actionable notifications with notify.notify service working so I’m not sure there - something sounds off.

I don’t think there’s issues with long timeouts, but realize that they won’t persist through restarts of Home Assistant, and depending on your automation settings you can control the number of instances. To disconnect the action from the running automation I often add the event as another trigger to the automation and then add logic to handle the normal trigger and the notification trigger separately. No wait needed in the automation then, just fire the notification and another instance of the automation handles the action.

If you set the wait to 0, it will not wait at all and will proceed immediately (or stop the automation if continue is not set). It might be counter intuitive, in some systems a 0 wait means wait forever.

Set the wait to have a timeout and it will work.

Your wait needs to wait for a time, and decide if you want to proceed if you don’t get a response. Right now the wait for a trigger is expecting the event to be ready when it starts (before you’ve even seen the notification), and when it’s not the automation is stopping because continue on timeout is false. A wait for a trigger without a timeout doesn’t wait forever.

You don’t say if you have any IoT networks yet, like zwave or zigbee, or if you’re looking for wifi. All have advantages / disadvantages, wifi is cheap and doesn’t use a separate dongle, zigbee devices tend to be cheaper, and a good variety available, Zwave is solid and doesn’t conflict with wifi or zigbee networks.

For the Hue bulbs you want a switch that lets you disconnect the relays from the physical switch. I don’t know what devices to suggest for EU, but my preference is to make the switches smart so they continue to do switch-like-things instead of having to retrain people.

I second the packet capture idea. Did you remove the virtual nic in the vm or just disconnect it? I’d you just disconnected it the packets were likely still directed to it as it’s the first network device.

I suspect you’re going to need to use a command line service to do a wol command as the integration doesn’t work let you pick a nic.

This is a great case for templates. Templates are Home Assistant's way of doing dynamic actions or data.

When: whatever triggers you need for the lights - can be multiple triggers or one trigger with every light/switch listed, with a For clause. The list is "OR"ed so do however you want. You could use a group but then all devices would be changed together - which doesn't sound like is what you want.

And if: Whatever conditions you want, time, day of week, etc.

Then do: The action is where it gets interesting add an action to execute "Generic turn off", select any device (we'll change that in a moment). The reason for the "Generic turn off" is that it works with devices in any domain (light or switch). Then drop into the YAML view and chcange the entity_id value to this template: '{{ trigger.from_state.entity_id }}'. The trigger is a variable that's available inside the automation and can be used instead of specifying a static value somewhere. https://www.home-assistant.io/docs/automation/trigger/ for details on triggers.

Here's the complete automation, you could create a new empty automation, then copy and paste this in place and just change the trigger and conditions as you want.

 yaml

    
alias: Action - Turn off lights 15min after turned on during day
description: ""
trigger:
  - platform: state
    entity_id:
      - switch.porch_light
    for:
      hours: 0
      minutes: 15
      seconds: 0
    enabled: true
    to: "on"
    from: "off"
condition:
  - condition: sun
    after: sunrise
    after_offset: "30"
  - condition: time
    after: "01:00:00"
    before: "23:00:00"
    weekday:
      - sun
      - mon
      - tue
      - wed
      - thu
      - fri
      - sat
action:
  - service: homeassistant.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: "{{ trigger.from_state.entity_id }}"
mode: queued
max: 10


  

Make sure you’re not using any of the strapping pins for the interface with the AHT22 - take a look at https://esp32.com/viewtopic.php?t=5970 for a read. It basically means leaving GPIOs 12, 0, 2, 4, 15, 5 floating during boot or the esp will not boot correctly.

These pins control the boot process (like going to the boot loader instead of your code).

I made my own that used irrigation valves with a Zooz Zwave dry relay, with Home Assistant to control it. It was a giant pain to find and get everything hooked up right but afterwards it works well.

I’ve since found some zigbee-based irrigation valves in AliExpress that I’ll try out this summer. I think they’re about the same price as what I built per valve (considering all the parts and the time needed). I haven’t had a chance to try them yet as I got them at the end of last summer but they worked well in testing.

Yes. There’s no support (hopefully just yet) for multiple Home Assistant instances with the same account.

Recorder integration: https://www.home-assistant.io/integrations/recorder/

The simplest way in configuration.yaml is something like:

    
recorder:
  exclude:
    entities:
      - sensor.chatty1
      - sensor.chatty2

  

For those devices that are very chatty you can specifically exclude them from being stored in the database. I then created template sensors that let me filter the results so I’m not spamming the database, only storing data I want. I do find the mm-wave sensors to be particularly bad, but I’ve also found Tuya-based air quality sensors to spam the logs too.

The only way I can think of is to disable the built-in updates, and set up time based shortcuts and have them do an if on wifi then trigger home assistant app sensor updates.

The way I’d structure it is a normal shortcut that you run from as many time-based shortcuts as you want to create (so you can reuse it easily). You can check the network name you’re connected to and only run if it matches your home network.

Create your own automation instead of using the blueprint. The blueprint doesn’t expose the location so it won’t work.

You might be able to look at the full yaml from the trace and copy it into a new automation (replace everything, then update the name). Once you’ve done that you should be able to use the visual editor and make whatever changes you need.