Quantcast
Viewing all 105799 articles
Browse latest View live

Losing Connection to Google Home?

I have Google integration all set up. However, I often give Google commands and it says it lost connection to . I open up the Google Home app, and there is everything, perfectly controllable. I give the command again and it works fine. But 5 minutes later, it’ll give me the same error, even though the Google Home app still shows everything.

Does anyone else experience this? Anyone know how to fix it?

1 post - 1 participant

Read full topic


Z-Wave Switch ERROR: Dropping command, expected response not received after 1 attempt(s)

I am setting up my first Z-Wave network and trying it out with just the controller and one z-wave switch. It’s an Eaton accessory switch. It shows up just fine as RF9517 Accessory Light Switch and there is a Remote Switch Switch entity. But when I try to toggle it, the command fails.

I’m using Home Assistant 0.118.5 on a Raspberry Pi 3 B and a Zooz Z-Wave Plus S2 USB Stick ZST10.

2020-12-10 21:24:12.484 Detail, Node005, Removing current message
2020-12-10 21:24:12.484 Detail, Node005, Notification: Notification - TimeOut
2020-12-10 21:24:14.406 Detail, Node001, Queuing (Controller) Request Node Neighbor Update
2020-12-10 21:24:14.406 Detail, Node005, Queuing (Controller) Request Node Neighbor Update
2020-12-10 21:24:14.407 Info, Requesting Neighbor Update for node 1
2020-12-10 21:24:14.407 Detail, Node001, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0x20, 0x93
2020-12-10 21:24:14.407 Detail, Notification: ControllerCommand - Starting
2020-12-10 21:24:14.408 Detail, 
2020-12-10 21:24:14.408 Info, Node001, Sending (Command) message (Callback ID=0x20, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0x20, 0x93
2020-12-10 21:24:14.554 Detail, Node001,   Received: 0x01, 0x05, 0x00, 0x48, 0x20, 0x21, 0xb3
2020-12-10 21:24:14.554 Detail, 
2020-12-10 21:24:14.554 Info, Node001, REQUEST_NEIGHBOR_UPDATE_STARTED
2020-12-10 21:24:14.554 Detail, Node033,   Expected callbackId was received
2020-12-10 21:24:14.554 Detail, Node033,   Expected reply was received
2020-12-10 21:24:14.554 Detail, Node033,   Message transaction complete
2020-12-10 21:24:14.554 Detail, 
2020-12-10 21:24:14.554 Detail, Node001, Removing current message
2020-12-10 21:24:14.554 Detail, Notification: ControllerCommand - InProgress
2020-12-10 21:24:14.555 Info, WriteNextMsg Controller nothing to do
2020-12-10 21:24:24.210 Detail,   Received: 0x01, 0x05, 0x00, 0x48, 0x20, 0x23, 0xb1
2020-12-10 21:24:24.210 Detail, 
2020-12-10 21:24:24.210 Warning, WARNING: REQUEST_NEIGHBOR_UPDATE_FAILED
2020-12-10 21:24:24.210 Detail, Notification: ControllerCommand - Failed
2020-12-10 21:24:24.211 Info, Requesting Neighbor Update for node 5
2020-12-10 21:24:24.211 Detail, Node005, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=5): 0x01, 0x05, 0x00, 0x48, 0x05, 0x21, 0x96
2020-12-10 21:24:24.212 Detail, Notification: ControllerCommand - Starting
2020-12-10 21:24:24.212 Detail, 
2020-12-10 21:24:24.212 Info, Node005, Sending (Command) message (Callback ID=0x21, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=5): 0x01, 0x05, 0x00, 0x48, 0x05, 0x21, 0x96
2020-12-10 21:24:24.234 Detail, Node005,   Received: 0x01, 0x05, 0x00, 0x48, 0x21, 0x21, 0xb2
2020-12-10 21:24:24.234 Detail, 
2020-12-10 21:24:24.234 Info, Node005, REQUEST_NEIGHBOR_UPDATE_STARTED
2020-12-10 21:24:24.234 Detail, Node033,   Expected callbackId was received
2020-12-10 21:24:24.234 Detail, Node033,   Expected reply was received
2020-12-10 21:24:24.234 Detail, Node033,   Message transaction complete
2020-12-10 21:24:24.234 Detail, 
2020-12-10 21:24:24.234 Detail, Node005, Removing current message
2020-12-10 21:24:24.234 Detail, Notification: ControllerCommand - InProgress
2020-12-10 21:24:24.236 Info, WriteNextMsg Controller nothing to do
2020-12-10 21:24:24.579 Detail,   Received: 0x01, 0x05, 0x00, 0x48, 0x21, 0x22, 0xb1
2020-12-10 21:24:24.580 Detail, 
2020-12-10 21:24:24.580 Info, REQUEST_NEIGHBOR_UPDATE_DONE
2020-12-10 21:24:24.580 Detail, Requesting routing info (neighbor list) for Node 5
2020-12-10 21:24:24.580 Detail, Node005, Queuing (Command) Get Routing Info (Node=5): 0x01, 0x07, 0x00, 0x80, 0x05, 0x00, 0x00, 0x03, 0x7e
2020-12-10 21:24:24.580 Detail, Notification: ControllerCommand - Completed
2020-12-10 21:24:24.581 Detail, 
2020-12-10 21:24:24.581 Info, Node005, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=5): 0x01, 0x07, 0x00, 0x80, 0x05, 0x00, 0x00, 0x03, 0x7e
2020-12-10 21:24:24.586 Detail, Node005,   Received: 0x01, 0x20, 0x01, 0x80, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x5f
2020-12-10 21:24:24.586 Detail, 
2020-12-10 21:24:24.586 Info, Node005, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
2020-12-10 21:24:24.586 Info, Node005,     Neighbors of this node are:
2020-12-10 21:24:24.586 Info, Node005,     Node 1
2020-12-10 21:24:24.586 Detail,   Expected reply was received
2020-12-10 21:24:24.586 Detail,   Message transaction complete
2020-12-10 21:24:24.586 Detail, 
2020-12-10 21:24:24.586 Detail, Node005, Removing current message
2020-12-10 21:24:37.926 Info, Node005, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2020-12-10 21:24:37.927 Info, Node005, SwitchBinary::Set - Setting node 5 to On
2020-12-10 21:24:37.927 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x25, 0x01, 0xff, 0x25, 0x22, 0x3c
2020-12-10 21:24:37.927 Detail, Node005, Queuing (Send) SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x23, 0xc3
2020-12-10 21:24:37.927 Detail, 
2020-12-10 21:24:37.927 Info, Node005, Sending (Send) message (Callback ID=0x22, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x25, 0x01, 0xff, 0x25, 0x22, 0x3c
2020-12-10 21:24:37.936 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-10 21:24:37.936 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-10 21:24:37.957 Detail, Node005,   Received: 0x01, 0x18, 0x00, 0x13, 0x22, 0x00, 0x00, 0x03, 0x00, 0xb8, 0x7f, 0x7f, 0x7f, 0x7f, 0x01, 0x01, 0x04, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0x6a
2020-12-10 21:24:37.957 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x22 received (expected 0x22)
2020-12-10 21:24:37.957 Info, Node005, Request RTT 29 Average Request RTT 28
2020-12-10 21:24:37.957 Detail,   Expected callbackId was received
2020-12-10 21:24:37.957 Detail,   Expected reply was received
2020-12-10 21:24:37.957 Detail,   Message transaction complete
2020-12-10 21:24:37.957 Detail, 
2020-12-10 21:24:37.957 Detail, Node005, Removing current message
2020-12-10 21:24:37.957 Detail, 
2020-12-10 21:24:37.958 Info, Node005, Sending (Send) message (Callback ID=0x23, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x23, 0xc3
2020-12-10 21:24:37.966 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-10 21:24:37.966 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-10 21:24:37.986 Detail, Node005,   Received: 0x01, 0x18, 0x00, 0x13, 0x23, 0x00, 0x00, 0x03, 0x00, 0xb8, 0x7f, 0x7f, 0x7f, 0x7f, 0x01, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0x6c
2020-12-10 21:24:37.986 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x23 received (expected 0x23)
2020-12-10 21:24:37.986 Info, Node005, Request RTT 28 Average Request RTT 28
2020-12-10 21:24:37.986 Detail,   Expected callbackId was received
2020-12-10 21:24:42.493 Detail, Node005, Polling: COMMAND_CLASS_SWITCH_BINARY index = 0 instance = 1 (poll queue has 0 messages)
2020-12-10 21:24:42.493 Detail, Node005, Queuing (Poll) SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x24, 0xc4
2020-12-10 21:24:47.958 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-12-10 21:24:47.959 Detail, Node005, Removing current message
2020-12-10 21:24:47.959 Detail, Node005, Notification: Notification - TimeOut
2020-12-10 21:24:47.962 Detail, 
2020-12-10 21:24:47.963 Info, Node005, Sending (Poll) message (Callback ID=0x24, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x25, 0x02, 0x25, 0x24, 0xc4
2020-12-10 21:24:47.971 Detail, Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-10 21:24:47.972 Detail, Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-10 21:24:47.991 Detail, Node005,   Received: 0x01, 0x18, 0x00, 0x13, 0x24, 0x00, 0x00, 0x02, 0x00, 0xb6, 0x7f, 0x7f, 0x7f, 0x7f, 0x01, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0x64
2020-12-10 21:24:47.991 Detail, Node005,   ZW_SEND_DATA Request with callback ID 0x24 received (expected 0x24)
2020-12-10 21:24:47.991 Info, Node005, Request RTT 28 Average Request RTT 28
2020-12-10 21:24:47.991 Detail,   Expected callbackId was received
2020-12-10 21:24:57.963 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-12-10 21:24:57.963 Detail, Node005, Removing current message
2020-12-10 21:24:57.963 Detail, Node005, Notification: Notification - TimeOut

1 post - 1 participant

Read full topic

Help restoring a snapshot (snapshot not recognized)

OK, I see to have broken my HA Supervised install. Since it was running on an unsupported OS (Ubuntu) I’ve decided to create a new HA VM and migrate to that but I can’t seem to restore the snapshot to the new system.

I have access to the old system and I managed to tar up the hassio folder. Inside of that folder is a “backup” folder which seems to contain tars of the snapshots that I have been regularly taking but when I try to restore the snapshots I am getting an “Unsupported file format” error.

What does the system look for to know that the tar I am uploading is a valid HA snapshot (which it is by the way). Is there a file naming convention or something? Mine is named 6148249e.tar.

4 posts - 2 participants

Read full topic

Change size of Lovelace Light Card

I’m trying to combine the Lovelace light card with the color wheel of the custom light-entity-card to control the brightness, everything works fine but I’m trying to find a way to adjust the size of the brightness ‘arc’ to be the same as the color wheel diameter and maybe make the icon a little smaller.

I’ve got card-mod installed but can’t find any way to adjust the sizes of the light card elements.

Any ideas would be appreciated.

1 post - 1 participant

Read full topic

Schlage lock seems to flood Z-Wave network, causing light automation to delay 10s

I know this place has its share of posts on Z-Wave issues, and more it seems with Schlage locks. All the ones I can find, however, seem to be about things not working. Everything I’m about to say works…eventually. It’s just that it shouldn’t take 10 seconds.

My goal is to have my front lights turn on when I unlock the door to let the dog out (at certain times of night, but that’s not the issue) and then turn back off when I lock the door.

This was working perfectly on SmartThings before I made the jump to Home Assistant, but now there’s a delay of ~10 seconds. Same door lock, same light switch.

The setup:

  • Schlage BE469ZP Connect Smart Deadbolt
  • GE (Jasco) 14292 In-Wall Smart Toggle Switch
  • Home Assistant 0.118.5 on Raspberry Pi 4, HassOS 4.17
  • Z-Wave integration with GoControl HUSBZB-1 stick

Things I tried:

  • I tried healing the network, and then looking at each node’s neighbors to map it out on paper. Everything is pretty much connected to everything. 6 total devices - 5 light switches and the lock. Each device has many neighbors - lots of ways to get from point A to point B.
  • I checked the Home Assistant status of the lock after locking/unlocking. It updates in the Home Assistant UI immediately. Asking it to lock or unlock from Home Assistant is also quick.
  • I checked the responsiveness of the in-wall switch in isolation. When I ask it to turn on/off from Home Assistant, it does so immediately.
  • I tried removing conditions from the automation to make sure none of them were stalling the automation. No effect.
  • I tried using a ZigBee button as the automation trigger. Light toggles immediately.
  • I tried using the lock as the automation trigger but having it toggle the Christmas tree (on a ZigBee plug) and that was instant.
  • I tried using a different Z-Wave light switch as the target of the automation. Same delay.

This led me to conclude that the problem was specifically the event from the Z-Wave lock followed by an attempt to update a Z-Wave device.

Time to go to the OZW log. I wasn’t sure if any of the byte values in the log could be used to reverse engineer the security key, so I zeroed them out. Node004 is the Schlage lock. Node003 is the light switch. Note the ##### separators (inserted by me) surrounding the Node 4 error, corresponding with a 10-second period of absolutely nothing happening.

2020-12-09 17:15:10.991 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, Node004, Received SecurityCmd_NonceGet from node 4
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.991 Info, Node004, Sending (Send) message (Callback ID=0x00, Expected Reply=0x00) - Nonce_Report - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00:
2020-12-09 17:15:10.998 Detail,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:10.998 Detail,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-09 17:15:11.019 Detail,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.020 Detail,   ZW_SEND_DATA Request with callback ID 0x00 received (expected 0x00)
2020-12-09 17:15:11.048 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.048 Info, Raw: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.049 Detail, Node004, Decrypted Packet: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.049 Detail,
2020-12-09 17:15:11.049 Info, Node004, Received Alarm report: type=21, level=1, sensorSrcID=0, type:Access Control event:1, status=255
2020-12-09 17:15:11.049 Detail, Node004, Refreshed Value: old value=22, new value=21, type=byte
2020-12-09 17:15:11.049 Detail, Node004, Changes to this value are not verified
2020-12-09 17:15:11.049 Detail, Node004, Setting Encryption Flag on Message For Command Class COMMAND_CLASS_DOOR_LOCK
2020-12-09 17:15:11.049 Detail, Node004, Queuing (Send) DoorLockCmd_Get (Node=4): 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.049 Detail, Node004, Refreshed Value: old value=1, new value=1, type=byte
2020-12-09 17:15:11.049 Detail, Node004, Changes to this value are not verified
2020-12-09 17:15:11.049 Detail, Node004, Refreshed Value: old value=0, new value=0, type=byte
2020-12-09 17:15:11.049 Detail, Node004, Changes to this value are not verified
2020-12-09 17:15:11.049 Detail, Node004, Refreshed Value: old value=2, new value=1, type=byte
2020-12-09 17:15:11.049 Detail, Node004, Changes to this value are not verified
2020-12-09 17:15:11.049 Detail, Node004, Notification: ValueChanged
2020-12-09 17:15:11.055 Detail, Node004, Notification: ValueChanged
2020-12-09 17:15:11.060 Detail, Node004, Notification: ValueChanged
2020-12-09 17:15:11.065 Detail, Node004, Notification: ValueChanged
2020-12-09 17:15:11.068 Detail,
2020-12-09 17:15:11.068 Info, Node004, Processing (Send) Nonce Request message (Callback ID=0x00, Expected Reply=0x00)
2020-12-09 17:15:11.068 Info, Node004, Sending (Send) message (Callback ID=0x00, Expected Reply=0x00) - Nonce_Get(DoorLockCmd_Get) - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00:
2020-12-09 17:15:11.073 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.073 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-09 17:15:11.093 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.093 Detail, Node004,   ZW_SEND_DATA Request with callback ID 0x00 received (expected 0x00)
2020-12-09 17:15:11.093 Info, Node004, Request RTT 24 Average Request RTT 61
2020-12-09 17:15:11.112 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.112 Info, Node004, Received SecurityCmd_NonceReport from node 4
2020-12-09 17:15:11.112 Info, Node004, Sending (Send) message (Callback ID=0x00, Expected Reply=0x00) - DoorLockCmd_Get (Node=4): 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.121 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.121 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-09 17:15:11.131 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, Node004, Received SecurityCmd_NonceGet from node 4
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.131 Info, Node004, Sending (Send) message (Callback ID=0x00, Expected Reply=0x00) - Nonce_Report - 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00:
2020-12-09 17:15:11.138 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.138 Detail, Node004,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-09 17:15:11.162 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.162 Detail, Node004,   ZW_SEND_DATA Request with callback ID 0x00 received (expected 0x00)
2020-12-09 17:15:11.162 Info, Node004, Request RTT 93 Average Request RTT 77
2020-12-09 17:15:11.183 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.183 Detail, Node004,   ZW_SEND_DATA Request with callback ID 0x00 received (expected 0x00)
2020-12-09 17:15:11.183 Info, Node004, Request RTT 114 Average Request RTT 95
2020-12-09 17:15:11.213 Detail, Node004,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.213 Info, Raw: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.213 Detail, Node004, Decrypted Packet: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.213 Detail,
2020-12-09 17:15:11.213 Info, Node004, Response RTT 144 Average Response RTT 228
2020-12-09 17:15:11.213 Info, Node004, Received DoorLock report: DoorLock is Secured
2020-12-09 17:15:11.213 Detail, Node004, Refreshed Value: old value=false, new value=true, type=bool
2020-12-09 17:15:11.213 Detail, Node004, Changes to this value are not verified
2020-12-09 17:15:11.213 Detail, Node004, Notification: ValueChanged
2020-12-09 17:15:11.352 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - False
2020-12-09 17:15:11.352 Info, Node003, SwitchBinary::Set - Setting node 3 to Off
2020-12-09 17:15:11.352 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Set (Node=3): 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:11.352 Detail, Node003, Queuing (Send) SwitchBinaryCmd_Get (Node=3): 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
###############################################
2020-12-09 17:15:21.069 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
###############################################
2020-12-09 17:15:21.069 Detail, Node004, Removing current message
2020-12-09 17:15:21.070 Detail, Node004, Notification: Notification - TimeOut
2020-12-09 17:15:21.072 Detail,
2020-12-09 17:15:21.073 Info, Node003, Sending (Send) message (Callback ID=0x00, Expected Reply=0x00) - SwitchBinaryCmd_Set (Node=3): 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:21.078 Detail, Node003,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:21.079 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-09 17:15:21.093 Detail, Node003,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:21.093 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x00 received (expected 0x00)
2020-12-09 17:15:21.093 Info, Node003, Request RTT 20 Average Request RTT 20
2020-12-09 17:15:21.094 Detail,   Expected callbackId was received
2020-12-09 17:15:21.094 Detail,   Expected reply was received
2020-12-09 17:15:21.094 Detail,   Message transaction complete
2020-12-09 17:15:21.094 Detail,
2020-12-09 17:15:21.094 Detail, Node003, Removing current message
2020-12-09 17:15:21.094 Detail,
2020-12-09 17:15:21.094 Info, Node003, Sending (Send) message (Callback ID=0x00, Expected Reply=0x00) - SwitchBinaryCmd_Get (Node=3): 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:21.100 Detail, Node003,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:21.100 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-12-09 17:15:21.114 Detail, Node003,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:21.114 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x00 received (expected 0x00)
2020-12-09 17:15:21.114 Info, Node003, Request RTT 20 Average Request RTT 20
2020-12-09 17:15:21.114 Detail,   Expected callbackId was received
2020-12-09 17:15:21.124 Detail, Node003,   Received: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-12-09 17:15:21.124 Detail,
2020-12-09 17:15:21.125 Info, Node003, Response RTT 30 Average Response RTT 30
2020-12-09 17:15:21.125 Info, Node003, Received SwitchBinary report from node 3: level=Off
2020-12-09 17:15:21.125 Detail, Node003, Refreshed Value: old value=true, new value=false, type=bool
2020-12-09 17:15:21.125 Detail, Node003, Changes to this value are not verified
2020-12-09 17:15:21.125 Detail, Node003,   Expected reply and command class was received
2020-12-09 17:15:21.125 Detail, Node003,   Message transaction complete
2020-12-09 17:15:21.125 Detail,
2020-12-09 17:15:21.125 Detail, Node003, Removing current message
2020-12-09 17:15:21.125 Detail, Node003, Notification: ValueChanged

This is actually the second log. I did this once, and after looking at it I was like what are all these sensor values I don’t care about?

So I went to the Z-Wave Node Management and saw how the door lock exposed nearly a dozen different entities including Alarm Type, Alarm Level… For each of these I checked the Exclude this entity from Home Assistant except for the ones I cared about, the lock status and the battery level.

My hope was this would cut down on the extraneous cross-traffic, making it more likely the lock would get done allowing the light switch to get its time.

It didn’t work. The result is the log above. I forgot to keep the old one so I don’t actually know if it’s shorter or not.

So, not sure what to do, and while I can make some educated guesses from the logs, but that’s about it. The thing that really gets me is that it worked fine on SmartThings. (Of course maybe SmartThings just included the lock in insecure mode which is faster and I just never knew.)

1 post - 1 participant

Read full topic

Is there a pie or doughnut chart that works?

I tried few of them, but all have a color bug, is a version that works ?
Thank you

1 post - 1 participant

Read full topic

Weird blank screen in browser glitch

So this isnt an issue with Home Assistant I dont think. In firefox everything is working fine. In chrome I am suddenly getting a weird issue only when a second dialog box is open. For example say I go to Supervisor->System->Hardware. If I try to select text and move the mouse around the screen flashes blank. Moving the mouse will make it come back, and sometimes flicker. I get the same when ever I have a second dialog window that opens in Home Assistant. Has not always been this way. Firefox on same PC works. Chrome on other PC works. I have tried clearing cache, browser settings, etc. It remains. No other issues with other sites in chrome on this PC, just suddenly in Home Assistant and again only when a second dialog window is open. Any suggestions?

1 post - 1 participant

Read full topic

How to delete devices


Issue with the configuration and Automation

I have this error while checking the config:

Invalid config for [automation]: The ‘hide_entity’ option is deprecated, please remove it from your configuration. This option became invalid in version 0.110. Got OrderedDict([(‘default_config’, {}), (‘http’, OrderedDict([(‘base_url’, ‘xxxxxx.duckdns.org added:8123’), (‘ssl_certificate’, ‘/ssl/fullchain.pem’), (‘ssl_key’, ‘/ssl/privkey.pem’), (‘ip_ban_enabled’, True), (‘ssl_profile’, ‘modern’), (‘login_attempts_threshold’, -1), (‘server_port’, 8123), (‘cors_allowed_origins’, [‘https://cast.home-assistant.io’])])), (‘frontend’, OrderedDict([(‘themes’, OrderedDict([(‘GreyNight’, OrderedDict([(‘base-hue’, ‘220’), (‘base-sat’, ‘5%’), (‘huesat’, 'var(–bas… (See ?, line ?).
Invalid config for [automation]: The ‘hide_entity’ option is deprecated, please remove it from your configuration. This option became invalid in version 0.110. Got OrderedDict([(‘default_config’, {}), (‘http’, OrderedDict([(‘base_url’, ‘xxxxxx.duckdns.org added:8123’), (‘ssl_certificate’, ‘/ssl/fullchain.pem’), (‘ssl_key’, ‘/ssl/privkey.pem’), (‘ip_ban_enabled’, True), (‘ssl_profile’, ‘modern’), (‘login_attempts_threshold’, -1), (‘server_port’, 8123), (‘cors_allowed_origins’, [‘https://cast.home-assistant.io’])])), (‘frontend’, OrderedDict([(‘themes’, OrderedDict([(‘GreyNight’, OrderedDict([(‘base-hue’, ‘220’), (‘base-sat’, ‘5%’), (‘huesat’, 'var(–bas… (See ?, line ?).

I tried to read in the forum, didnt get any answer that is working.

in confgiration.yaml I have defined:

automation: !include automations.yaml

1 post - 1 participant

Read full topic

Trigger with Or-condition never fires

First greetings to all and thanks for the huge amount of hints and help.
But still, it does not help me Image may be NSFW.
Clik here to view.
:confused:

Home Assistant runs as a docker installation on a Synology Diskstation, I did update recently. Most devices are Zigbee2mqtt which is not relevant for the problem.

My goal is to switch on my Christmas decoration in the morning. The start time shall be different for the weekend. The action simply turns on an input_boolean switch. That triggers the real switching. I found this idea in this forum. I summed up everything in a package file from where I copy parts and add english comment as the names and descriptions are in German. I do not change the code.

For completeness, this is the switch which should be toggled by the automation (innen is german for inside, lichter is lights):

input_boolean:
  # Switch to toggle group of light
  xmas_lichter_innen:
    name: "Weihnachtsbeleuchtung im Haus"
    # initial: off

I can also use it to manually turn on/off the lights.

These are the input-fields for giving different starttimes (germen startzeit)

input_datetime:
  # time when switch should turn on during the week
  xmas_innen_startzeit_morgens:
    name: "Weihnachtsbeleuchtung Zeit zum Einschalten morgens innen"
    has_date: false
    has_time: true
    initial: '06:30'

  # time when switch should turn on at weekends
  xmas_innen_startzeit_morgens_we:
    name: "Weihnachtsbeleuchtung Wochenend-Zeit zum Einschalten morgens innen"
    has_date: false
    has_time: true
    initial: '08:00'

That was the easy part, now for the automation.
The trigger should fire at both the start-time I entered in the input_datetime fields for weekdays and weekends. The condition should decide:

  1. is the time equal to weekdays start-time and do we have a weekday?
    or
  2. is the time equal to weekends start-time and do we have weekend?

If one of both is true, the input_boolean should be turned on.

automation:
  - id: xmas_innen_morgens_ein
    description: Weihnachtsbeleuchtung innen morgens ein zu fester Zeit
    alias: Weihnachtsbeleuchtung innen morgens ein
    trigger:
      - platform: time
        at: input_datetime.xmas_innen_startzeit_morgens
      - platform: time
        at: input_datetime.xmas_innen_startzeit_morgens_we
    condition:
      - condition: or
        conditions:
          - condition: template
            value_template: >-
              {{ states.sensor.time.state == states.input_datetime.xmas_innen_startzeit_morgens.state[0:5]
                 and now().weekday() < 5
              }}
          - condition: template
            value_template: >-
              {{ states.sensor.time.state == states.input_datetime.xmas_innen_startzeit_morgens_we.state[0:5]
                 and now().weekday() > 4
              }}
    action:
      - service: input_boolean.turn_on
        entity_id: input_boolean.xmas_lichter_innen
    mode: single

And this does not fire, I never found an entry in the logbook or the logfile (homeassistant.components.automation: debug).

Yes, I checked the YAML with YAML Validator and I read conditions manual. I pasted the template and parts of the template into the developer tools and watched the parts of the template to show the expected values (I love that automatic update). I also tried now().strftime instead of sensor.time and other stuff.
I have the same automation for outside lights and for both to turn them off in the evening. As an experienced programmer I am able to keep my errors consistent, so none of them four works Image may be NSFW.
Clik here to view.
:slight_smile:

Can anyone give me a hint what I am doing wrong?
Any relevant information missing?

I am fighting nearly two weeks now and I hope to get my lights working until christmas. At least the turn on for sunset with a delay depending on the weather Image may be NSFW.
Clik here to view.
:grin:

1 post - 1 participant

Read full topic

Template sensor value drops to 0

I have a template energy sensor. very simple (see config bellow). I have noticed a strange behavior. sometimes the value drops to 0 literally for one reading, that’s of course further screws up my utility meters.
Image may be NSFW.
Clik here to view.
2020-12-11_09-29-39

- platform: template
  sensors:
    energy_total_usage:
      friendly_name: "Total energy usage"
      unit_of_measurement: Wh
      value_template: >-
        {{ (states('sensor.energija_a_faze')|float + states('sensor.energija_b_faze')|float + states('sensor.energija_c_faze')|float) }}

the sensors used in this template gets data from ESPHome integration. I thought maybe in some cases I got 0 from integration. but if I check this sensors, everything looks like ok, there are no zeros recorded.

Any ideas?

2 posts - 2 participants

Read full topic

Roborock S6, send reminder if a floor hasn't been cleaned for X days?

I recently bought Roborock S6 MaxV and I’m using the Roborock iOS app which I’m fairly happy with. From what I’ve read it’s complicated/not possible to integrate it with HA if I’m using the Roborock app, and except for one thing the Roborock app provides me with enough functionality.

We have multiple floors so I need to (manually) move the vacuum between the floors for it to clean the full house. I try to do this every other day and I’ve scheduled it to run a full floor clean every day, so as long as I remember to move the vacuum cleaner there are no problems.

What I would like to setup is a reminder/notification if a floor hasn’t been cleaned in 3-4 days or something like that which basically means I’ve forgotten to move the cleaner to that floor.

Is it possible with the HomeAssistant integration to somehow monitor or access the previously vacuumed floors so that I can send a notification if “Floor X” hasn’t been cleaned for a couple of days?

If not possible with the HomeAssistant integration, can anyone think of any other solution to send these kind of reminders (and not just a fixed send reminder every 3rd day regardless)?

1 post - 1 participant

Read full topic

Bluetooth LE Tracker doesn't find devices

Hi all,
I’m trying to integrate traking of my BLE devices, but I have some problems.

I have two kinds of devices:

In configuration.yaml I created this configuration:

device_tracker:
  - platform: bluetooth_tracker
    interval_seconds: 60
    consider_home: 180
    new_device_defaults:
      track_new_devices: true
  - platform: bluetooth_le_tracker
    interval_seconds: 60
    consider_home: 180
    new_device_defaults:
      track_new_devices: true

The file know_device.yaml has been created but the problem is that in this file are present only BT devices (phone, TV and so on) and not BLE devices.

If I search with my PC the BT devices, I see the Tile and Nut devices, so they are active.

I followed the official guide and searched in the community for solution but I have not found anything.

I use:

  • Raspberry PI 3b
  • Home Assistant 0.118.5
  • HassOS 4.17

Could you please help me?
Thanks,
Roberto.

1 post - 1 participant

Read full topic

Restore backup from Google Drive add-on not working

Hello smart people!

I am trying to restore HA Supervised from a backup using the Google Drive add-on.

After a crash, I reinstalled HA and added the Google Drive backup-addon. I can se my current snapshots and I have selected Restore everything. After pressing that button, I loose the connection to HA and then nothing more is happening.

What am I doing wrong? Is there some other way to restore my system using a downloaded backup-file.

Edit: After following these instructions on how to set up HA supervised, I can access my system and then I can also add the Gdrive backup ad-on. But from there, the procedure is as described above.

4 posts - 2 participants

Read full topic

Hass.io + ConBee - automate smart plug

I have setup hass.io on my PI and connected my ConBee ll stick. By deCONZ I can now connect to the controller and add new devices and the first device I have added is a Aqara smart plug (non wifi version) https://www.aqara.com/eu/smart_outlet.html and it is now listed under devices/lights
Image may be NSFW.
Clik here to view.
SmartPlug

I can click on the device to turn it on and off so there is a working connection between the device and the controller

If I go to Developer Tools in Home Assistant the new device is not listed there in the states tab. I would like to add an automation for this device so I need to know the entity id.

Is there something else that I need to do to get this setup working?

2 posts - 2 participants

Read full topic


Reolink+AI Tool+Home Assistant - FREE Edition for AI Motion Detection

Quote from reolink reddit: https://www.reddit.com/r/reolinkcam/comments/k98oss/reolink_ai_tool_home_assistant_free_edition/

So here’s my current system, and I’ll say upfront I take zero credit for any development of any of the tools used with this method. With this I’m using 4 total components. I’m not going to go too deep into Home Assistant because that’d take a LONG time to write up and there are lots of great YouTube tutorials on it already.

  1. Reolink Cameras (2x RLC-520, 1x RLC-810A)
  2. iSpy v7.2.1.0 64-bit (Freeware)
  3. AI-Tool
  4. Deepstack AI

Here’s the workflow:

  • Obviously set your cameras. I’m sure you’ve already done this…
    install Ispy
  • Load your cameras into iSpy
    • I used the “Add IP Cameras with Wizard” option. Currently the 520 and 810A are not part of the Wizard, so you’ll want to use “Not Listed” and add the Make and Model manually.
    • Tick the “Scan RTSP Addresses” box.
    • Click Next
    • Enter your Username/Password for the camera. I didn’t input anything in the Channel option as I don’t use a DVR. I believe if you’re using a DVR, you can use your DVR here and select individual channels all from one source.
    • Click Next
    • If you know your camera’s IP address, you can input it manually here or you can click “Scan Local Network”.
    • Click Next Again
    • This next page will give you tons of options for how to grab the stream. I used the FFMPEG:410:rtsp://user:password@IP Address:554/h264Preview_01_sub for this setup.
    • The reason I’m using sub instead of main is to reduce network traffic. This solution doesn’t require high-resolution, and I found that using the “Fluent”/sub stream provided less frame drops than using the "Clear’/main stream
    • Click Next and you should see your camera added to your Dashboard now and you can name it with “Edit Camera”
  • Set Image capture within iSpy.
  1. On the “Edit Camera” screen there are tons of options. I’m only going to say exactly what is needed to make this work. So I have literally turned off everything else, motion recording, alerts, scheduling… it’s all turned off.
  2. Go to the Motion Detection Tab.
  3. In Detection Zones - draw a square(s) over the area you want motion detection to work. I used the entire area, because the real motion detection happens in the next step anyways. Too many false positives here isn’t a bad thing.
  4. On the Images Tab - enable Local Saving Enabled and set Save When to Motion Detection. Feel free to remove the Overlay Text.
  5. Storage Tab Media Location - Set this to a folder easy to remember. I still am using C:\aiinput\ from the last write-up. I changed my Directory names to match the camera names. I enabled Storage Management so the software would only keep images for 24 hours. - I have an NVR running 24/7, so I don’t personally care about these photos. I could have easily set it for 1 hour and it would still perform fine. Finish.
  • Install Deepstack AI for Windows. The Docker one won’t work with this new workflow.
  • Get the AI-Tool .zip for installation here: github.com/VorlonCD/bi-aidetection/releases
  • Extract the Zip folder. If you previously were using AI-Tool, you can copy this into the same folder and your settings with remain. If you haven’t used AI-Tool before, extract the Zip folder. I personally extracted it to Program Files just so I could easily find it later.
  • Configuring AI Tool. - This new version contains MQTT built-in, which is why we no longer need Blue Iris.
    • DeepStack tab:
      • Select your Deepstack installation Folder
      • Select API: Detection API, Mode: High, Port: ??. I’m using Port 83 still, but this can be anything you want.
      • Select Automatically Start Deepstack <- Another new addition with the updated AI Tool. Save
    • Settings:
      • Default Input Path - This is the folder you used for Media Location in iSpy
      • Deepstack URL - localhost:port# (localhost:83)
      • Start - tick “Start with user login”. Save
    • Cameras:
      • Click Add, give it a camera name. I’ll use FrontDoor for this example.
      • Input Folder: click the Select - then navigate to the folder where iSpy is putting the images. If you renamed the Directory name it’ll look something like C:/aiiinput/video/FrontDoor/Grabs
      • Select the Relevant objects you want detected.
    • MQTT Time - under Actions click “Settings”. Then click “Settings” again next to MQTT. Input your Server:Port for your Home Assistant MQTT broker. Example: [192.168.0.72:1883](add https:// before 192.168.0.72:1883/). Set the Username/Password that MQTT uses on Home Assistant.
      • Topic is what the HA (Home Assistant) Configuration.yaml file will work based off. This new version of Ai Tool also has variables, so be default the Topic will be:
      • ai/[Camera]/motion [Detection] - Which will pass a payload that looks like this:
      • ai/FrontDoor/motion Person - if it’s a person
      • ai/FrontDoor/motion Car - if it’s a Car
      • If you want the Detection Type to be specified in the message, leave it as [Detection]. If you don’t care about the detection type, change it to something line “On”.
    • Cooldown Time: I highly recommend setting this variable unless you want a ton of alerts and an annoyed wife because her phone received 250 notification over the course of an hour. I set this to one minute which seems to we working out pretty well.
  • Configuration.Yaml:
    • Update your HA Configuration.yaml file to look for these new MQTT payloads. If you’re using the Detection variable, you’ll need the payload_on for each detection type you set in AI Tool. Here’s an example of mine where I only care about People and Cars…

binary_sensor:

  • platform: mqtt

name: “Motion - Front Door - Vehicle”

device_class: motion

state_topic: “ai/FrontDoor/motion”

payload_on: “Car”

off_delay: 60

  • platform: mqtt

name: “Motion - Front Door - Person”

device_class: motion

state_topic: “ai/FrontDoor/motion”

payload_on: “Person”

off_delay: 60

  • Automation configuration: Once the MQTT messages has reached HA, we can do a couple things with it. Some people will use NodeRed to really customize their event but I prefer automation because it’s just easier IMO.
    • Name: Motion Detection - Vehicle Front Door
      • Mode: Single (default)
    • Triggers:
      • Type: MQTT
      • Topic: ai/FrontDoor/Motion
      • Payload: Vehicle
    • Conditions - I don’t use anything here
    • Actions:
      • Type: Call service
      • Service: Notify.mobile_app_iphone
      • Service Data - If you have your cameras integrated into HA, you can send a snapshot of their current state along with the notification.

message: Motion Detection - Front Door - Vehicle

data:

attachment:

content-type: jpeg

push:

category: camera

entity_id: camera.front_door

Save!

And that’s it. I know this was pretty lengthy, but I wanted to be pretty verbose in case someone else wanted to do a similar setup. I’d be happy to help anyone with this is you run into issues or have general questions. I believe I’ve done this as close to step by step as possible, if I missed anything please let me know. Also if you have an Android phone that Service Data code will not work, it’s only for iPhones.

1 post - 1 participant

Read full topic

Rfbridge_demux Received unknown RF command

I’m using the Sonoff RFbridge with Tasmota and the rfbridge demux Python script. I have several Sonoff RM433 remotes with 8 buttons each that I’ve been using for serval months now and I haven’t edited the script for months either. I believe the problem started after I updated to Home Assistant Core 0.118.4. On my remote called Remote 2, all of the buttons fail to work except for Remote 2 Button 2. That button works just fine. The light on the remote comes on when every button is pressed. I see entries for each button press in the console in Tasmota on the RFbridge. And button 2 actually works.

When I checked Configuration > Logs, I see this:

Logger: homeassistant.components.python_script.rfbridge_demux.py
Source: rfbridge_demux.py:53
Integration: Python Scripts (documentation, issues)
First occurred: December 1, 2020, 7:29:32 PM (148 occurrences)
Last logged: 5:34:31 AM

<rfbridge_demux> Received unknown RF command: 718992
<rfbridge_demux> Received unknown RF command: 718994
<rfbridge_demux> Received unknown RF command: 718999
<rfbridge_demux> Received unknown RF command: 718995
<rfbridge_demux> Received unknown RF command: 718993

If I compare those unknown codes to the script, /config/python_scripts/rfbridge_demux.py, the codes are all defined there. And all of these codes work, except for 7 or the 8 buttons on remote 2.

d = { 'F3C748':['remote1_button1','ON','false'],
      'F3C74C':['remote1_button2','ON','false'],
      'F3C744':['remote1_button3','ON','false'],
      'F3C749':['remote1_button4','ON','false'],
      'F3C742':['remote1_button5','ON','false'],
      'F3C745':['remote1_button6','ON','false'],
      'F3C741':['remote1_button7','ON','false'],
      'F3C743':['remote1_button8','ON','false'],
      '718998':['remote2_button1','ON','false'],
      '71899C':['remote2_button2','ON','false'],
      '718994':['remote2_button3','ON','false'],
      '718999':['remote2_button4','ON','false'],
      '718992':['remote2_button5','ON','false'],
      '718995':['remote2_button6','ON','false'],
      '718991':['remote2_button7','ON','false'],
      '718993':['remote2_button8','ON','false'],
      '398EE8':['remote3_button1','ON','false'],
      '398EEC':['remote3_button2','ON','false'],
      '398EE4':['remote3_button3','ON','false'],
      '398EE9':['remote3_button4','ON','false'],
      '398EE2':['remote3_button5','ON','false'],
      '398EE5':['remote3_button6','ON','false'],
      '398EE1':['remote3_button7','ON','false'],
      '398EE3':['remote3_button8','ON','false'],
      'A650D8':['remote4_button1','ON','false'],
      'A650DC':['remote4_button2','ON','false'],
      'A650D4':['remote4_button3','ON','false'],
      'A650D9':['remote4_button4','ON','false'],
      'A650D2':['remote4_button5','ON','false'],
      'A650D5':['remote4_button6','ON','false'],
      'A650D1':['remote4_button7','ON','false'],
      'A650D3':['remote4_button8','ON','false'],
      '0BB2D8':['remote5_button1','ON','false'],
      '0BB2DC':['remote5_button2','ON','false'],
      '0BB2D4':['remote5_button3','ON','false'],
      '0BB2D9':['remote5_button4','ON','false'],
      '0BB2D2':['remote5_button5','ON','false'],
      '0BB2D5':['remote5_button6','ON','false'],
      '0BB2D1':['remote5_button7','ON','false'],
      '0BB2D3':['remote5_button8','ON','false'],
      'D6BC06':['living_room_motion','ON','false'],
      '105A16':['dining_room_motion','ON','false'],
      '1F2006':['hallway_motion','ON','false']
    }

p = data.get('payload')

if p is not None:
  if p in d.keys():
    service_data = {'topic':'home/{}'.format(d[p][0]), 'payload':'{}'.format(d[p][1]), 'qos':0, 'retain':'{}'.format(d[p][2])}
  else:
    service_data = {'topic':'home/unknown', 'payload':'{}'.format(p), 'qos':0, 'retain':'false'}
    logger.warning('<rfbridge_demux> Received unknown RF command: {}'.format(p))
  hass.services.call('mqtt', 'publish', service_data, False)

One thing that I noticed that could just be a red herring. Is that the 7 codes that do not work are the only codes in the list that are exclusively numbers with no letters. Remote 2 button 2 has a letter in it and that one works. I don’t know Python, I’m afraid, but it made me wonder if there was a string to integer conversion happening somewhere by accident. I assume the codes being in quotes would make them strings though.

Any ideas on where else I could be looking for the problem?

1 post - 1 participant

Read full topic

Automation to turn on switch at specific time frame and if temp & precipitation met specific conditions

Hi All, I want to create an automation to control the electric heating

The switch should be turned for 1 hour on
only between 05:00-07:00 or 15:00–16:00
and if the Temp is below 8°C or precipitation is above 4 for 5 minutes.

The following Automation which I have created don’t trigger when the conditions met.
The action part with the 1 hour delay is working Ok! when I manually execute it.

Any help or ideas what is not correct in the trigger and conditions section??

alias: ‘Heat: On 101 ->Velz Tmp Blw 8°C or Rain Above 4’
description: ‘’
trigger:

  • platform: time
    at: ‘05:00:00’
  • platform: time
    at: ‘16:00:00’
  • platform: numeric_state
    below: ‘8’
    entity_id: sensor.wupws_temp
  • platform: numeric_state
    entity_id: sensor.wupws_preciptotal
    for: ‘00:05:00’
    above: ‘4.0’
    condition:
  • condition: and
    conditions:
    • condition: time
      after: ‘05:00’
      before: ‘06:00’
    • condition: or
      conditions:
      • condition: time
        after: ‘16:00’
        before: ‘17:00’
      • condition: and
        conditions:
        • condition: numeric_state
          entity_id: sensor.wupws_temp
          below: ‘8’
      • condition: or
        conditions:
        • condition: numeric_state
          entity_id: sensor.wupws_preciptotal
          for: ‘00:05:00’
          above: ‘4’
          action:
  • service: switch.turn_on
    data: {}
    entity_id: switch.sonoff_xxxxxx
  • service: notify.gmail_xxxx
    data:
    title: Heat turned on
    message: ‘Heat turned on from Heat:On 101’
  • delay: ‘01:00:00’
  • service: switch.turn_off
    data: {}
    entity_id: switch.sonoff_xxxxxx
  • service: notify.gmail_xxxx
    data:
    title: Heat turned off
    message: ‘Heat turned off from Heat:On 101’
    mode: single

1 post - 1 participant

Read full topic

WARNING: latest docker-ce (20.10.0) not compatible with Home Assistant supervised

If you are installing home assistant under docker, you will run into a problem Likely, if you upgrade docker-ce to the latest official version 20.10.0 be very careful.

1 post - 1 participant

Read full topic

Can't Edit Lovelace Manual Card

I wanted to make a Custom Button Card so I made a Manual card and pasted in this example config:

- type: 'custom:button-card'
  color_type: card
  entity: binary_sensor.intruder
  name: Intruder Alert
  state:
    - value: 'on'
      color: red
      icon: mdi:alert
      styles:
        card:
          - animation: blink 2s ease infinite
    - operator: default
      color: green
      icon: mdi:shield-check

I changed the entity to something I have and saved it but it was not there until I refreshed the page. I thought that was weird as I don’t recall having to do that after making a card. I tested the button and it works great. However when I wanted to make a change (I clicked on the 3 dots then edit dashboard) the card disappears. I tried this on Edge and Chrome. I made another Custom Button Card and the same thing happens. Every time I go to the view with that card on it I have to refresh the page in order to see it. Using version 0.118.5, button card version is 3.4.0.

1 post - 1 participant

Read full topic

Viewing all 105799 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>