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
Last couple of days I was fiddling around to move the TadoLocal server from a dedicated server to the HomeAssistant Add-ons container solution. I did not wanted to start the Tado bridge pairing sequence again, just lazy. So i moved the tado-local.db inside this container, which eventually worked out. But this made me thinking how could it be made easier to transfer the TadoLocal server without re-paring.
Looking in the source code it seams dat only the parings-table should be transferred, from the old system to the new system. Is that correct?
And from the pairing table only the following data is used:
IP (AccessoryIP)
port (AccessoryPort)
controller-id (iOSPairingId)
The rest, even the keys, are not used after pairing. Is that correct i do i miss something?
With this limited required info we could add an API call to retrieve this information and add command line parameters to create a new pairing, which provides the user to choose between PIN or these fields to fill the pairing table?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Last couple of days I was fiddling around to move the TadoLocal server from a dedicated server to the HomeAssistant Add-ons container solution. I did not wanted to start the Tado bridge pairing sequence again, just lazy. So i moved the tado-local.db inside this container, which eventually worked out. But this made me thinking how could it be made easier to transfer the TadoLocal server without re-paring.
Looking in the source code it seams dat only the parings-table should be transferred, from the old system to the new system. Is that correct?
And from the pairing table only the following data is used:
The rest, even the keys, are not used after pairing. Is that correct i do i miss something?
With this limited required info we could add an API call to retrieve this information and add command line parameters to create a new pairing, which provides the user to choose between PIN or these fields to fill the pairing table?
Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions