Closed mulcmu closed 4 months ago
I can confirm that nibble 4 represents the number of MyQ devices paired. I did a factory reset and it showed 0, then added a MyQ bridge and it shows 1.
We should add this to the Sync
step and present it in the diagnostics section.
Superb! Thanks for confirming.
I will roll this into #149 with functionality to clear memory as well. I was thinking to implement both the get() and clear() operations as a service back to HA. Accidental activation of the clear() would be undesirable so putting it in a service call seems like a good spot to make usage deliberate. Not an operation I would expect users to put in an automation. A new ratgdo event to trigger when additional device is learned would be useful.
Merged in #149.
Is there a simple way to call query_paired_devices(), or see a breakdown in the log of the counts/types of paired devices without needing to add all the sensors (which were removed due to high memory usage)?
The Web UI Documentation shows a button to call this query, but I don't see it in the actual UI.
Gdo responds to a Command 0x307 sent from ratgdo with Command 0x308. The 0x308 response appears to contain the number of paired devices in byte2. When 0x307 is issued with non-zero nibbles, it appears a subset of the paired devices is returned:
I don't have any myQ accessories to pair so help is needed to see if and where they are included in the 0x308 response. Below yaml can be added to the
button:
block to collect the 0x308 data with logging set to VERBOSE to collet the data. The command for clearing memory has a similar structure, so this will support adding ability to clear paired devices by ratdgo.After flashing new code with above changes, connect to logs over wireless and share 0x308 the response output here along with details of the connected devices.