You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_LOGGER.exception(f"Exception while getting device id {call}, {call.data}, i know {hass.data[DOMAIN]['deviceByHassId']}, fyi deviceByID is {hass.data[DOMAIN]['devices']}")
f"Exception while getting device id {call}, {call.data}, i know {hass.data[DOMAIN]['deviceByHassId']}, fyi deviceByID is {hass.data[DOMAIN]['devices']}")
_LOGGER.warning(f"{device_id} is not a valid duofern device, I only know {hass.data[DOMAIN]['stick'].duofern_parser.modules['by_code'].keys()}. Gonna handle the other devices in {device_ids} though.")
218
+
_LOGGER.warning(
219
+
f"{device_id} is not a valid duofern device, I only know {hass.data[DOMAIN]['stick'].duofern_parser.modules['by_code'].keys()}. Gonna handle the other devices in {device_ids} though.")
Copy file name to clipboardExpand all lines: custom_components/duofern/services.yaml
+1-5Lines changed: 1 addition & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,12 @@
1
1
# Describes the format for available Wink services
2
2
3
3
start_pairing:
4
-
description: Pair duofern devices. Remember - There is no pairing UI. To pick up the newly paired devices later, you need to call sync_devices and possibly restart HA.
4
+
description: Pair duofern devices. Remember - There is no pairing UI. To pick up the newly paired devices later, you need to restart HA.
5
5
fields:
6
6
timeout:
7
7
description: timeout in seconds
8
8
example: 60
9
9
10
-
sync_devices:
11
-
description: Re-sync Devices (trigger after pairing, if it does not work, a restart of homeassistant may help). Also writes duofern config file.
12
-
May raise warnings for already-created devices. Do not worry.
13
-
14
10
clean_config:
15
11
description: Clean the duofern config. More info in the readme.
Copy file name to clipboardExpand all lines: readme.md
+3-35Lines changed: 3 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,48 +43,16 @@ To use ``pyduofern`` within [Homeassistant](https://home-assistant.io/), add the
43
43
44
44
There are some services you can call via the service interface. A few of these to get you started:
45
45
46
-
``duofern.start_pairing`` starts the pairing mode for a given number of seconds.
46
+
``duofern.start_pairing`` starts the pairing mode for a given number of seconds. After pairing reload the integration to make the new devices visible.
47
47
48
48

49
49
50
-
``duofern.sync_devices`` will force-sync any newly discovered devices.
51
-
52
-

53
-
54
-
Please use the renaming feature in the homeassistant GUI to arrive at human readable
55
-
names for your deices.
56
-
57
50
``duofern.ask_for_update``
58
51
59
52
Ask duofern devices to re-send their state in case. Can be used in setups where RF is finnicky.
60
53
61
54
``duofern.dump_device_state``
62
55
Dump the current last received state for all duofern modules as a warning level message to the log. This reflects the current state of all RF messages received from devices - What's not here wasn't received by the stick or came in garbled.
63
56
64
-
``duofern.clean_config``
65
-
> **Warning**
66
-
> You should absolutely NOT use it if you have been running duofern for a long time and your covers have "human" names in the .duofern.json file. That option hasn't been used for a long time though - it is still from the time when homeassistant had no UI way of renaming entities/devices.
67
-
68
-
**Use when:**
69
-
- you have "ghost" devices that do not correspond to a physical device
70
-
71
-
**Use like this:**
72
-
- If you want to be sure you can go back: backup ``duofern.json``.
73
-
- Call ``duofern.clean_config``.
74
-
- Restart homeassistant.
75
-
- Observe that all your duofern devices are now disabled/unavailable.
76
-
- Toggle/move all your duofern devices at the device to make sure that they send messages for homeassistant to pick up.
77
-
- You can diagnose what devices were picked up again using ``duofern.dump_device_state``.
78
-
- Once all devices are there: call ``duofern.sync_devices``.
79
-
- Restart homeassistant for good measure.
80
-
- Observe that the devices are now back.
81
-
- If some are still missing: toggle them at the device and diagnose using ``dump_device_state`` until they are found again.
82
-
- Once they are: ``duofern.sync_devices``, final restart.
83
-
- Everything works.
84
-
- If not: maybe you want to return to your backed-up ``duofern.json``.
85
-
86
-
The duofern python module keeps a list of devices that are paired. ``clean_config`` throws that list away.
87
-
88
-
In normal operation, the list should rebuild itself - whenever a message is received from a device that was previously paired it should appear in the list.
89
-
It's not very well tested because it's not a common situation. I ran it, restarted homeassistant, and my devices became available again after a few seconds.
90
-
57
+
``duofern.sync_devices``
58
+
Write the duofern config file with the known devices. normally not required from the user.
0 commit comments