eufy_security
eufy_security copied to clipboard
Changing Status on Homebase is not working
Describe the bug I can't be certain exactly what is causing this bug, but it is either having: a) a secondary homebase on your system b) the original homebase 1 on your system
To reproduce Steps to reproduce the behavior: Add the secondary homebase Try changing any of the values (e.g. arm mode) Arm mode does not successfully change Note, the status is reflected when changed in the app
Expected behavior Should be able to change the mode on the second home base in the way that you do on the main homebase
Additional information Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields; Version | core-2023.11.2 Installation Type | Home Assistant OS
-
Eufy Security Add-on Version: Current version: 1.7.1
-
Eufy Security Integration Version: 7.7.4
-
Debug Logs from Home Assistant (https://github.com/fuatakgun/eufy_security/discussions/624) - Without this, I will automatically resolve this issue
home-assistant_eufy_security_2023-11-22T09-59-09.666Z.log
- Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):
cause: undefined,
message: 'Error: read ETIMEDOUT',
context: undefined,
stacktrace: 'Error: read ETIMEDOUT\n' +
' at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)'
}
}
2023-11-17 16:33:32.214 INFO Client disconnected with ip: 127.0.0.1 port: 50504 code: 1000 reason: Normal Closure
2023-11-17 18:29:34.476 INFO Client disconnected with ip: 127.0.0.1 port: 55856 code: 1000 reason: Normal Closure
2023-11-17 18:29:42.388 INFO Client disconnected with ip: 127.0.0.1 port: 39680 code: 1000 reason: Normal Closure
2023-11-18 02:35:02.047 INFO Push notification connection closed
2023-11-18 02:35:07.440 INFO Push notification connection successfully established
2023-11-19 03:10:54.788 WARN Heartbeat check failed for station T8010P2321503D3C. Connection seems lost. Try to reconnect...
2023-11-19 03:10:54.792 INFO Disconnected from station T8010P2321503D3C
2023-11-19 03:11:15.033 WARN Tried all hosts, no connection could be established to station T8010P2321503D3C.
2023-11-19 03:11:15.035 INFO Timeout connecting to station T8010P2321503D3C
2023-11-19 03:11:25.068 INFO Connected to station T8010P2321503D3C on host 192.168.1.35 and port 10634
2023-11-19 12:00:30.186 ERROR Message error
InvalidPropertyValueError Invalid value for this property according to metadata
details:
{
context: {
propertyName: 'guardMode',
propertyValue: 6,
metadata: {
key: 1224,
name: 'guardMode',
label: 'Guard Mode',
readable: true,
writeable: true,
type: 'number',
states: {
'0': 'Away',
'1': 'Home',
'2': 'Schedule',
'3': 'Custom 1',
'4': 'Custom 2',
'5': 'Custom 3',
'47': 'Geofencing',
'63': 'Disarmed'
}
}
}
}
error stack:
• utils.ts:139 validValue
usr/src/app/node_modules/eufy-security-client/src/utils.ts:139:19
• station.ts:692 setGuardMode
usr/src/app/node_modules/eufy-security-client/src/http/station.ts:692:19
• eufysecurity.ts:1635 setStationProperty
usr/src/app/node_modules/eufy-security-client/src/eufysecurity.ts:1635:31
• task_queues:95 processTicksAndRejections
node:internal/process/task_queues:95:5
• message_handler.ts:111 handle
usr/src/app/node_modules/eufy-security-ws/src/lib/station/message_handler.ts:111:17
• server.ts:125 receiveMessage
usr/src/app/node_modules/eufy-security-ws/src/lib/server.ts:125:21
2023-11-19 12:03:06.960 INFO Received push notification for changing guard mode
{
guard_mode: 0,
current_mode: 0,
stationSN: 'T8001H23183905BE'
}
2023-11-19 12:03:31.624 INFO Received push notification for changing guard mode
{
guard_mode: 1,
current_mode: 1,
stationSN: 'T8001H23183905BE'
}
2023-11-19 12:09:03.694 INFO Received push notification for changing guard mode
{
guard_mode: 0,
current_mode: 0,
stationSN: 'T8001H23183905BE'
}
2023-11-19 12:09:08.602 INFO Received push notification for changing guard mode
{
guard_mode: 1,
current_mode: 1,
stationSN: 'T8001H23183905BE'
}
2023-11-21 03:32:10.907 INFO Push notification connection closed
2023-11-21 03:32:16.352 INFO Push notification connection successfully established
2023-11-21 03:57:59.695 INFO Push notification connection closed
2023-11-21 03:58:05.140 INFO Push notification connection successfully established
2023-11-21 08:48:22.191 INFO Disconnected from station T8010P2321503D3C
2023-11-21 08:48:27.421 INFO Connected to station T8010P2321503D3C on host 192.168.1.35 and port 25016
2023-11-21 13:40:46.136 WARN Heartbeat check failed for station T8010P2321503D3C. Connection seems lost. Try to reconnect...
2023-11-21 13:40:46.140 INFO Disconnected from station T8010P2321503D3C
2023-11-21 13:41:06.397 WARN Tried all hosts, no connection could be established to station T8010P2321503D3C.
2023-11-21 13:41:06.400 INFO Timeout connecting to station T8010P2321503D3C
2023-11-21 13:41:16.554 INFO Connected to station T8010P2321503D3C on host 192.168.1.35 and port 16390
2023-11-21 14:25:05.240 INFO Client disconnected with ip: 127.0.0.1 port: 41398 code: 1006 reason: Abnormal Closure ```
- Would you share your device with me in case further debugging required? (Yes/No):
Yes
Please share problematic homebase with me.
Please share problematic homebase with me.
Sure, can you advise how I do this? Thanks
EDIT - found instructions here: https://github.com/fuatakgun/eufy_security#debugging-issues
I have now shared this device with you - thank you :)
I have the same issue with homebase 1
Debug is activated
What do you need to inspect ?
Thank you
@vaderag , have you shared the device with me, if yes, please drop an email to [email protected] with serial no and name of the device.
@vaderag , have you shared the device with me, if yes, please drop an email to [email protected] with serial no and name of the device.
Yes, shared it a while back and got notice you'd accepted. Will email now
Same problem here, hombase 1
I'm also seeing this, I think it's related to multiple homebases rather than the homebases 1 (I have a homebases 2 and 3).
Yes, I also have the same issue. I have 2 HomeBase 2s
Same here. The strange thing is I can change the guard mode on one homebase and it works but on the other homebase which is exactly the same model it won't change the mode. No errors in the logs and I've restarted the homebase, deleted it from HA and re-added it:
2024-01-16 16:46:19.259 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] domain - station - EventSourceType.product - station.set_property - {'domain': 'station', 'serial_no': 'T8010N2320360F2F', 'name': 'guardMode', 'value': '1'} - {'name': 'guardMode', 'value': '1', 'serialNumber': 'T8010N2320360F2F'}
2024-01-16 16:46:19.260 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] {'name': 'guardMode', 'value': '1', 'serialNumber': 'T8010N2320360F2F', 'command': 'station.set_property', 'messageId': 'station.set_property.bada9c7031554107a76f769ba3b7e999'}
2024-01-16 16:46:19.262 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] send_message - {'name': 'guardMode', 'value': '1', 'serialNumber': 'T8010N2320360F2F', 'command': 'station.set_property', 'messageId': 'station.set_property.bada9c7031554107a76f769ba3b7e999'}
2024-01-16 16:46:19.268 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'result', 'success': True, 'messageId': 'station.set_property.bada9c7031554107a76f769ba3b7e999', 'result': {'async': True}}
Hi fuatakgun. I have the same issue with a change of the home base status (home, away) not working. I have two home bases and it only works one. Happy to share the device if you want to have a look?