I am trying to immediately send a notification when a person is detected by frigate and then update the notification when AI provides a summary. I have a rate limit of one notification per minute per camera

Currently I have:

  alias: New AI
  trigger:
  - topic: frigate/reviews
    trigger: mqtt
  conditions:
  - condition: template
    value_template: '{{ trigger.payload_json[''type''] == ''end'' }}'
  - condition: template
    value_template: '{{ trigger.payload_json[''after''][''severity''] == ''alert''
      }}'
  - condition: template
    value_template: "{% set camera = trigger.payload_json['after']['camera'] %} {%
      set entity_id = 'input_datetime.frigate_last_alert_' + camera %} {% if states(entity_id)
      is not none %}\n  {% set last_run = states(entity_id) | as_timestamp(0) %}\n
      \ {% set now = now().timestamp() %}\n  {{ (now - last_run) > 60 }}\n{% else
      %}\n  true\n{% endif %}\n"
  actions:
  - variables:
      event_id: '{{ trigger.payload_json[''after''][''id''] }}'
      camera: '{{ trigger.payload_json[''after''][''camera''] }}'
      label: '{{ trigger.payload_json[''after''][''data''][''objects''][0] }}'
      thumb: '{{ trigger.payload_json[''after''][''thumb_path''] }}'
  - target:
      entity_id: '{{ ''input_datetime.frigate_last_alert_'' + camera }}'
    data:
      timestamp: '{{ now().timestamp() }}'
    action: input_datetime.set_datetime
  - data:
      title: '{{ camera }} Camera'
      message: A {{ label }} was detected on the {{ camera }} camera. Tap for details.
      data:
        push:
          sound: default
          interruption-level: time-sensitive
        entity_id: camera.{{ camera | lower }}
        tag: '{{ event_id }}'
    action: notify.notify
  - wait_for_trigger:
    - topic: frigate/tracked_object_update
      trigger: mqtt
    timeout:
      hours: 0
      minutes: 0
      seconds: 15
      milliseconds: 0
    continue_on_timeout: true
  - data:
      title: '{{ camera }} Camera1'
      message: '{{ wait.trigger.payload_json[''description''] }} Tap for details.'
      data:
        push:
          sound: default
          interruption-level: time-sensitive
        entity_id: camera.{{ camera | lower }}
        tag: '{{ event_id }}'
    action: notify.notify
  mode: queued
  max: 25

The automation triggers on the first trigger, then timeouts on the second. I know frigate is sending the tracked_object_update topic because I setup another automation just looking for that and it fires within seconds.

So, I have two issues. The second wait_for_trigger never fires, it just timeouts. Second is that the first action only fires after the 15 second timeout on the wait_for_trigger.

Any ideas would be appreciated. Thanks.

1 post - 1 participant

Read full topic

I have the .js file here (I have a bunch of other lovelace things in the community folder with no issues):

/config/www/community/lovelace-paper-buttons-row/paper-buttons-row.js

and here’s the entry in my configuration.yaml:

lovelace:
mode: yaml
resources:
- url: /hacsfiles/lovelace-paper-buttons-row/paper-buttons-row.js
type: module

any ideas? as i mentioned i have other stuff, button card, card mod, mushroom, all work just fine, it’s just this one that has been refusing to work…

2 posts - 2 participants

Read full topic

Hi all. I am new to HA (moved from Homeseer about 2 months ago). I use an Intel NUC with a basic install of HAOS. I have ~ 66 Z-Wave devices and use a Z-Net G8 (800 chipset) for the controller, with 7.22.2 SDK. I use the Z-Wave JS UI add-in. My Z-Net is hardwired to the LAN. Loving HA as it is so much more capable, but feeling so lost in this area. Homeseer seemed to be pretty rock solid when it comes to Z-Wave, but that could just be my flawed perception.

I have noticed very off things on my network such as automations triggering when they should not (like triggered by a switch turning off that was off the whole time). Plus a whole bunch of other things like lag, zwave command failures that were prematurely termination automations, etc. I have done a few things to work around some of the symptoms, but the root cause is still there and I have no idea how to further troubleshoot or solve it. I am looking for some advice / guidance.

I am noticing in the logs that there are many controller errors / resets as well as what seems to be an incredibly chatty network (but I do not know what a normal z-wave network should look like).

Please let me know what steps might be taken next (or other info I can post here) to figure this out, as I am guessing this is abnormal.

Things like this occur randomly between every 3 minutes to 3 hours (from the zwavejs_current.log file):

2025-02-12T14:16:00.857Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-02-12T14:16:00.857Z DRIVER version 14.3.8
2025-02-12T14:16:00.857Z DRIVER
2025-02-12T14:16:00.965Z DRIVER Serial port errored: The socket closed unexpectedly! (ZW0100)
2025-02-12T14:16:02.968Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-02-12T14:16:02.968Z DRIVER version 14.3.8
2025-02-12T14:16:02.968Z DRIVER
2025-02-12T14:16:03.035Z DRIVER Serial port errored: The socket closed unexpectedly! (ZW0100)
2025-02-12T14:16:11.047Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-02-12T14:16:11.047Z DRIVER version 14.3.8
2025-02-12T14:16:11.047Z DRIVER
2025-02-12T14:16:11.056Z DRIVER Serial port errored: The socket closed unexpectedly! (ZW0100)
2025-02-12T14:16:26.065Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-02-12T14:16:26.065Z DRIVER version 14.3.8
2025-02-12T14:16:26.065Z DRIVER
2025-02-12T14:16:26.071Z DRIVER Serial port errored: The socket closed unexpectedly! (ZW0100)
2025-02-12T14:16:41.087Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-02-12T14:16:41.087Z DRIVER version 14.3.8
2025-02-12T14:16:41.087Z DRIVER
2025-02-12T14:16:41.103Z DRIVER Serial port errored: The socket closed unexpectedly! (ZW0100)
2025-02-12T14:16:56.111Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-02-12T14:16:56.111Z DRIVER version 14.3.8
2025-02-12T14:16:56.111Z DRIVER
2025-02-12T14:16:56.126Z DRIVER Dropping message because the driver is not ready to handle it yet.
2025-02-12T14:16:56.134Z DRIVER Dropping message because the driver is not ready to handle it yet.
2025-02-12T14:16:57.120Z CONFIG version 14.3.8
2025-02-12T14:16:57.281Z CNTRLR querying Serial API capabilities…
2025-02-12T14:16:57.290Z CNTRLR received API capabilities:
firmware version: 1.0
manufacturer ID: 0x0c
product type: 0x04
product ID: 0x0371
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SerialAPISetup (0x0b)
· SetRFReceiveMode (0x10)
· SendNodeInformation (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· EnterBootloader (0x27)
· UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMReadLongByte (0x2c)
· NVMOperations (0x2e)
· ClearTxTimers (0x37)
· GetTxTimers (0x38)
· ClearNetworkStats (0x39)
· GetNetworkStats (0x3a)
· GetBackgroundRSSI (0x3b)
· SetListenBeforeTalkThreshold (0x3c)
· ExtendedNVMOperations (0x3d)
· RemoveSpecificNodeIdFromNetwork (0x3f)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· AddPrimaryController (0x4d)
· AssignPriorityReturnRoute (0x4f)
· SetLearnMode (0x50)
· AssignSUCReturnRoute (0x51)
· RequestNetworkUpdate (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· SendSUCNodeId (0x57)
· AssignPrioritySUCReturnRoute (0x58)
· ExploreRequestInclusion (0x5e)
· ExploreRequestExclusion (0x5f)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· undefined (0x65)
· RequestProtocolCCEncryption (0x68)
· GetRoutingInfo (0x80)
· LockUnlockLastRoute (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· VirtualNodeSetNodeInfo (0xa0)
· VirtualNodeSendNodeInfo (0xa2)
· VirtualNodeSetLearnMode (0xa4)
· GetVirtualNodes (0xa5)
· IsVirtualNode (0xa6)
· BridgeApplicationCommand (0xa8)
· SendDataBridge (0xa9)
· SendDataMulticastBridge (0xab)
· GetLibrary (0xbd)
· SendTestFrame (0xbe)
· GetProtocolStatus (0xbf)
· StartWatchdog (0xd2)
· StopWatchdog (0xd3)
· SetMaximumRoutingAttempts (0xd4)
· SetMaxSmartStartInclusionRequestInterval (0xd6)
· undefined (0xd7)
· undefined (0xd8)
· Shutdown (0xd9)
· GetLongRangeNodes (0xda)
· GetLongRangeChannel (0xdb)
· SetLongRangeChannel (0xdc)
· SetLongRangeShadowNodeIDs (0xdd)
· Proprietary_DE (0xde)
· Proprietary_DF (0xdf)
· Proprietary_E7 (0xe7)
· Proprietary_E8 (0xe8)
2025-02-12T14:16:57.291Z CNTRLR querying additional controller information…
2025-02-12T14:16:57.346Z CNTRLR received additional controller information:
Z-Wave API version: 1 (official)
Z-Wave chip type: EFR32ZG23 / ZGM230S
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
Z-Wave Classic nodes: 1, 2, 4, 5, 6, 8, 9, 10, 11, 14, 15, 16, 18, 19,
21, 22, 24, 25, 26, 27, 28, 30, 31, 32, 33, 34, 35, 37, 38, 39, 40, 42, 43, 4
4, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 58, 59, 62, 64, 67, 69, 70, 71, 72,
73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85
2025-02-12T14:16:57.347Z CNTRLR querying version info…
2025-02-12T14:16:57.398Z CNTRLR received version info:
controller type: Bridge Controller
library version: Z-Wave 7.22
2025-02-12T14:16:57.399Z CNTRLR querying protocol version info…
2025-02-12T14:16:57.454Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 7.22.2
appl. framework build no.: 43981
git commit hash: 64616164383330646162613131323737
2025-02-12T14:16:57.455Z CNTRLR querying controller capabilities…
2025-02-12T14:16:57.504Z CNTRLR received controller capabilities:
controller role: Primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2025-02-12T14:16:57.505Z CNTRLR querying serial API setup capabilities…
2025-02-12T14:16:57.564Z CNTRLR supported serial API setup commands:
· GetSupportedCommands
· SetTxStatusReport
· SetLongRangeMaximumTxPower
· SetPowerlevel
· GetLongRangeMaximumTxPower
· GetPowerlevel
· GetMaximumPayloadSize
· GetLongRangeMaximumPayloadSize
· SetPowerlevel16Bit
· GetPowerlevel16Bit
· GetRFRegion
· SetRFRegion
· SetNodeIDType
2025-02-12T14:16:57.564Z CNTRLR querying max. payload size…
2025-02-12T14:16:57.619Z CNTRLR maximum payload size: 46 bytes
2025-02-12T14:16:57.620Z CNTRLR supported Z-Wave features:
· SmartStart
2025-02-12T14:16:57.620Z CNTRLR Querying configured RF region…
2025-02-12T14:16:57.669Z CNTRLR The controller is using RF region USA (Long Range)
2025-02-12T14:16:57.670Z CNTRLR Querying configured max. Long Range powerlevel…
2025-02-12T14:16:57.722Z CNTRLR The max. LR powerlevel is 14.0 dBm
2025-02-12T14:16:57.722Z CNTRLR Querying configured Long Range channel information…
2025-02-12T14:16:57.773Z CNTRLR received Z-Wave Long Range channel information:
channel: Auto
supports auto channel selection: true
2025-02-12T14:16:57.773Z CNTRLR Performing soft reset…
2025-02-12T14:16:57.823Z CNTRLR Waiting for the controller to reconnect…
2025-02-12T14:16:58.100Z CNTRLR reconnected and restarted
2025-02-12T14:16:58.100Z CNTRLR Starting hardware watchdog…
2025-02-12T14:16:58.101Z CNTRLR Switching serial API to 16-bit node IDs…
2025-02-12T14:16:58.103Z CNTRLR querying Z-Wave Long Range capabilities…
2025-02-12T14:16:58.154Z CNTRLR Switching to 16-bit node IDs successful
2025-02-12T14:16:58.275Z CNTRLR received Z-Wave Long Range capabilities:
max. payload size: 148 bytes
nodes:
2025-02-12T14:16:58.276Z CNTRLR Switching serial API to 16-bit node IDs…
2025-02-12T14:16:58.330Z CNTRLR Switching to 16-bit node IDs successful
2025-02-12T14:16:58.330Z CNTRLR querying controller IDs…
2025-02-12T14:16:58.382Z CNTRLR received controller IDs:
home ID: 0x3d309c
own node ID: 1
2025-02-12T14:16:58.383Z CNTRLR Enabling TX status report…
2025-02-12T14:16:58.441Z CNTRLR Enabling TX status report successful…
2025-02-12T14:16:58.441Z CNTRLR finding SUC…
2025-02-12T14:16:58.493Z CNTRLR This is the SUC
2025-02-12T14:16:58.611Z CNTRLR [Node 001] No device config found
2025-02-12T14:16:58.615Z CNTRLR [Node 002] Embedded device config loaded
2025-02-12T14:16:58.616Z CNTRLR [Node 004] Embedded device config loaded
2025-02-12T14:16:58.618Z CNTRLR [Node 005] Embedded device config loaded
2025-02-12T14:16:58.621Z CNTRLR [Node 006] Embedded device config loaded
2025-02-12T14:16:58.623Z CNTRLR [Node 008] Embedded device config loaded

And then those resets seem to propagate a rescan of the whole network. This is from the z-ui_2025-02-12.log file I see an incredible amount of continual chatter that looks like this, just a very small snip but it continues through all of my devices. (I think that this is what was triggering some of my automations by re-reporting the off state of a device):

2025-02-12 00:01:21.524 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-244 => NaNs
2025-02-12 00:01:21.524 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-245 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-245 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-246 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-246 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-247 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-247 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-248 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-248 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-249 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-249 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-250 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-250 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-251 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-251 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-252 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-252 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-253 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-253 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-254 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-254 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-level-255 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-44-0-dimmingDuration-255 => NaNs
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-91-0-scene-001 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-91-0-scene-002 => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-91-0-slowRefresh => undefined
2025-02-12 00:01:21.525 INFO Z-WAVE: [Node 071] Value added 71-112-0-3 => 1
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-4 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-5 => 14
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-6 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-11 => 3
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-12 => 3
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-13 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-14 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-21 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-22 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-23 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-24 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-25 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-26 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-27 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-30 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-31-1 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-31-2 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-31-4 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-31-8 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-31-16 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-31-32 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-112-0-31-64 => 0
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-114-0-productId => 12342
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-114-0-productType => 17479
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-114-0-manufacturerId => 12
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-134-0-hardwareVersion => 255
2025-02-12 00:01:21.526 INFO Z-WAVE: [Node 071] Value added 71-134-0-firmwareVersions => 5.14
2025-02-12 00:01:21.527 INFO Z-WAVE: [Node 071] Value added 71-134-0-protocolVersion => 4.61
2025-02-12 00:01:21.527 INFO Z-WAVE: [Node 071] Value added 71-134-0-libraryType => 3
2025-02-12 00:01:21.532 INFO Z-WAVE: [Node 071] Ready: HomeSeer Technologies - HS-WD200+ (Scene Capable Wall Dimmer Switch)
2025-02-12 00:01:21.565 INFO Z-WAVE: [Node 038] Is alive
2025-02-12 00:01:21.581 INFO Z-WAVE: [Node 038] Value added 38-37-0-currentValue => true
2025-02-12 00:01:21.581 INFO Z-WAVE: [Node 038] Value added 38-37-0-targetValue => true
2025-02-12 00:01:21.581 INFO Z-WAVE: [Node 038] Value added 38-43-0-sceneId => undefined
2025-02-12 00:01:21.581 INFO Z-WAVE: [Node 038] Value added 38-43-0-dimmingDuration => NaNs
2025-02-12 00:01:21.581 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-1 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-1 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-2 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-2 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-3 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-3 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-4 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-4 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-5 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-5 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-6 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-6 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-7 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-7 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-8 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-8 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-9 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-9 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-10 => undefined
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-10 => NaNs
2025-02-12 00:01:21.582 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-11 => undefined
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-11 => NaNs
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-12 => undefined
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-12 => NaNs
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-13 => undefined
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-13 => NaNs
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-14 => undefined
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-dimmingDuration-14 => NaNs
2025-02-12 00:01:21.583 INFO Z-WAVE: [Node 038] Value added 38-44-0-level-15 => undefined

2 posts - 2 participants

Read full topic

I am new to home automation and microprocessors. I am just beginning to work through Home Assistant and should receive my hardware tomorrow. However, I am designing a digital control system for my greenhouse and need some direction for an obscure point. I am planning to use Shelly devices to control many operations. There is one that I haven’t found support for. I have a passive vent system that I need to open and close based on temperature. In my previous analog control system I used limit switches to control the max open and close vent positions. I haven’t found an easy way to do that with my RPi and Home Assistant and associated hardware. I was thinking that I could tie GPIO pin N to the open limit switch common terminal, then tie the open limit switch NO terminal to GPIO pin N+1 (or whatever). That way I could raise GPIO pin N when starting to open the vent and GPIO pin N+1 would go high when the limit switch is hit. This uses the 3.3v from GPIO pin N to raise GPIO pin N+1. So, first, can an automation access the GPIO pins, both to raise them or as a trigger? Second, is this a really stupid approach and is there a much easier way to do this? The problem is that the physical vent movement needs to be accurate, repeatable and reliable, especially closing in the winter and I am leary of using a button, though the action is the same. As extra credit, I would like to set a timeout so that if the open/close operation doesn’t complete in some time period that I can stop the process and send a failure notification. TIA!

2 posts - 2 participants

Read full topic

I am creating a second post for this question as the first one is pretty stale now.
What I am attempting is to supply the URL for the Picture-Elements image: entry by using a variable. The contents (URL) of the variable changes, obviously. The particular variable is declared in the config/variables yaml file and as such should be globally available. I have not found a method that works and I have tried a lot of variations. If the problem is simply that the Picture-Element card simply cannot use anything except a URL in the form of a text string, then I will have to revert to changing the picture URL manually as before. If this cannot be accomplished with the current Picture Elements code maybe this can be a new feature. My partial current code:

type: picture-elements
panel: true
image: $ [ season-pix ]
width: 99.9%
title: Today

3 posts - 2 participants

Read full topic

I can’t find any document that specifies all the possible config.txt keywords, their possible values and meaning.

I want to configure console resolution and hot-plug, ethernet static IPV4 address, wifi credentials, etc.

If such document exists please let me know where I can find it.

3 posts - 3 participants

Read full topic

(topic deleted by author)

1 post - 1 participant

Read full topic

Is it possible to have home assitant to find devices on two subnets?

I am running UBIQUITI SDWAN between two sites Australia and Thailand.

Main site is 192.168.0.x & other is 192.168.1.x

Any help appreciated.

1 post - 1 participant

Read full topic

I have the fan spinning using the custom button card. But the card/fan only has a toggle action on/off. (See code below).

How do I add in the High, Medium, Low, Off options as per the popup. And then bring all the fans into a card (eg Entities) card.

Does anyone have sample code which may do this. Or can show me the yaml i need.

Customer Button Card Code

type: custom:button-card
aspect_ratio: 4/1
name: Fanny 
state:
  - value: "on"
    color: green
    styles:
      icon:
        - animation:
            - rotating 1s linear infinite
        - height: 50px
        - width: 50px
  - value: "off"
    color: red
tap_action:
  action: toggle
entity: fan.fanny
icon: null

2 posts - 2 participants

Read full topic

I had RTL433 set a little too aggressive on protocols it was looking at, and the number of devices MQTT is seeing for 433 is over 350. Every time I move my RV (where Home Assistant resides), it picks up 100s more as I travel. From TPMS sensors (now disabled) and weather stations, etc.

When I put the question above (the topic title) into Google trying to find an answer, the AI answer gave me this script for automation. But how to get it to go through and cycle through the devices… that I have no clue.

  - alias: "Delete Inactive MQTT Devices"
    trigger:
      - platform: time
        at: "03:00:00"  # Run daily at 3am
    condition:
      - condition: template
        value: "{{ state_attr('your_mqtt_device_entity', 'last_updated') | timestamp_custom('%Y-%m-%dT%H:%M:%S') |  as_timestamp < (now() | timestamp_custom('%Y-%m-%dT%H:%M:%S') | as_timestamp - (5 * 24 * 60 * 60)) }}"
    action:
      - service: homeassistant.remove_entity
        data:
          entity_id: "your_mqtt_device_entity" 

Is there a way to get an automation or a script to loop through all MQTT devices and check for last_updated and delete those that are older than say 5 days and do so automatically?

4 posts - 2 participants

Read full topic

My Home Assistant OS is running on a Raspberry Pi 4, and Agent DVR is installed on Windows 11 Pro. The Windows network is set to private, and the firewall is G Data, where I have opened port 8090. API is not enabled.

The following problem occurs: I go to Device Integration in Home Assistant, try to add Agent DVR, and it asks for Host and Port. The port is clear: 8090.
For the host, I assume it is the IP address of the Windows PC (e.g., 192.168.x.x).
I entered it like this:

``
http://192.168.x.x:8090

I also tried `localhost` and similar things.
**Something is blocking it**, but I cannot figure out what it is.

**A ping from Home Assistant to my PC worked, so the PC is reachable**.
I cannot figure out where the issue lies.

**Do you know more? Maybe a hint would already help.**

1 post - 1 participant

Read full topic

I used a template to give me a time for my next alarm.

{% if states('sensor.sm_a526u_next_alarm') not in ['unavailable', 'None'] %}
{{ (states('sensor.sm_a526u_next_alarm')|as_datetime|as_local).strftime('%H:%M') }}
{% else %} No Next Alarm{% endif %}

Which gives me
Next Alarm 06:33

I have an automation that kicks in 15 minutes after this for the coffee maker. How can I add 15 minutes to the template so I can show true brew time? Thanks.

1 post - 1 participant

Read full topic

Hi,

I have these individual devices defined :

Works fine, except I get them in an other order :

Is this a bug ?

3 posts - 2 participants

Read full topic

Hi! I use a handful of 433mhz temperature sensors. I’ve added them in configuration.yaml with RFlink. Once in a while, I need to replace the batteries, but that changes the ID of the sensor. I can find the new ID in the log, and replace it in the configuration, but this creates a new sensor with new sensor data. Is there a way to merge the old sensor data with the new one?

Before I used Home Assistant, I used Domoticz. It had a feature where you could replace a sensor with a new one, keeping all the logs intact. Does HA have a similiar functionality?

1 post - 1 participant

Read full topic

Hello everybody,

I need you support, please.
I want to have a special output name for a switch.
Instead of “On/Off” I want to have as an output “open/closed” (garage door).

How can I change the state to an output I want to have?

Thank you very much and have a nice day.

4 posts - 3 participants

Read full topic

General question. In case of having a large number of devices. Let’s say 100 of which a 30 have a static IP on a single network. What would be the best approach in term of IP management. I currently have a lease of 48hrs.

I try to find the optimal settings for my router to give the most stable net work. I experience loss of connection with a reconnection within seconds to 1-2 minutes if it happens. I try to resolve that by managing a separate range for dynamic (DHCP) and static ip address and lease time.

Any advice?

4 posts - 3 participants

Read full topic

Hi guys
I made an automation that use a logic simulating assist_satellite.start_conversation. here there is the topic: Make assist ask First Automation .

1 post - 1 participant

Read full topic

Hi everyone, after more than one year on Jeedom, I’ve decided to move to HA. The dashboard being one of the reason why I moved.
So far I managed to build such dashboard

On the center up position, one can see Mushroom Chips Card icons and I’ve been trying over the last 2 days to use card-mod to increase the size of those icon without success. In fact, even the basic exemple from the guide is not working

card_mod:
  style: |
    ha-card {
      color: red;
    }

I’ve installed card-mod using the git command from the hacs directory

git clone https://github.com/thomasloven/lovelace-card-mod

one can see that the files seems to be there

and update my configuration.yalm like this

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes
  extra_module_url:
    - /hacsfiles/lovelace-card-mod/card-mod.js
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

If I’m not mistaken hacsfile points to /homeassistant/www/community

I’ve of course tried to reboot/reload but nothing help.

As I’m very new with HA be gentle and already thanks in advance for your help

Fred

1 post - 1 participant

Read full topic

Hi everyone, I recently discovered my router reassigned my Home Assistant IP address which caused problems with remote access. I resolved that, but now I’m seeing problems with my Frigate and HACS integrations throwing errors which I’m struggling to resolve.

HACS:

Logger: homeassistant.config_entries
Source: config_entries.py:637
First occurred: 9:17:18 PM (1 occurrences)
Last logged: 9:17:18 PM

Error setting up entry for hacs
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 637, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/__init__.py", line 220, in async_setup_entry
    setup_result = await async_initialize_integration(hass=hass, config_entry=config_entry)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/__init__.py", line 206, in async_initialize_integration
    await async_try_startup()
  File "/config/custom_components/hacs/__init__.py", line 193, in async_try_startup
    startup_result = await async_startup()
                     ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/hacs/__init__.py", line 171, in async_startup
    hass.config_entries.async_setup_platforms(
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'. Did you mean: 'async_unload_platforms'?

Frigate integration:

Logger: homeassistant.config_entries
Source: config_entries.py:637
First occurred: 9:17:19 PM (2 occurrences)
Last logged: 9:17:41 PM

Error setting up entry 192.168.1.160:5000/ for frigate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 637, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/frigate/__init__.py", line 280, in async_setup_entry
    await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2272, in async_forward_entry_setups
    await integration.async_get_platforms(platforms)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1185, in async_get_platforms
    import_future.result()
    ~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1185, in async_get_platforms
    import_future.result()
    ~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1185, in async_get_platforms
    import_future.result()
    ~~~~~~~~~~~~~~~~~~~~^^
  [Previous line repeated 3 more times]
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1173, in async_get_platforms
    platforms.update(self._load_platforms(platform_names))
                     ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1098, in _load_platforms
    platform_name: self._load_platform(platform_name)
                   ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1272, in _load_platform
    cache[full_name] = self._import_platform(platform_name)
                       ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/loader.py", line 1304, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
           ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 201, in protected_loop_func
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.13/importlib/__init__.py", line 88, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/config/custom_components/frigate/sensor.py", line 8, in <module>
    from homeassistant.const import CONF_URL, PERCENTAGE, TEMP_CELSIUS
ImportError: cannot import name 'TEMP_CELSIUS' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)

1 post - 1 participant

Read full topic

Can anyone provide guidance or advice on how to play MP3 audio and TTS through the audio jack on a host machine? We have a home announcement speaker installed in several rooms, and its audio jack is connected to the host machine.

I have Home Assistant OS installed on an x86 machine.

Alternatively, I also have a Raspberry Pi 3. Can it be configured to act as a local network audio device?

3 posts - 3 participants

Read full topic