Feature Requests

[AnarchyNow]

1. After initial run and auto-connection to node (umbrel, raspiblitz, Mynode) we set a flag, maybe in the config.ini that tells Warden that it is connected to an Umbrel node for example, and to stop attempting to connect to the other node types?

2. Logging of the Specter desktop connection process and requests to Specter desktop; any failures or successes can be observed for troubleshooting, wallets gathered, balances, etc. Perhaps this should live in its own debug file since there is a lot going on here.

On the topic of Specter, where are you getting the URLs that are defined in Specter_importer.py?
self.login_url = self.base_url + 'auth/login'
self.tx_url = self.base_url + 'wallets/wallets_overview/txlist'
self.core_url = self.base_url + 'settings/bitcoin_core?'
These three URLs do not resolve to anything in the Specter Desktop running on Umbrel V0.4.0

[pxsocs]

Great suggestions. Keep them coming.

1. Working on this - there's a much better method already running on background that is more efficient. Will transition soon.

2. If I understand correctly, the suggestion is to create a log file with more detailed data, including connections to Specter, correct? Working on that. Right now the Log Widget works more like a "Notifications" widget. Should split into a detailed debug.log file and Notifications.

Specter_importer.py is a more comprehensive library that I worked for a different project so it contains more endpoint requests. They are unused here. Soon I will include authentication to Specter so the auth/login endpoint will probably be used.

[AnarchyNow]

Outstanding! I’m looking forward to seeing the different hooks into Specter and all that it has to offer.  By the way, I knew nothing of python before finding your project and I immediately began to reverse engineer it and teach myself a little bit of coding along the way.  Thank you for that!  This is why I find the logging useful, when I’m reading the code and want to know if part of the code is executing or not, the logs are my way of knowing for sure.  So yes, details in one spot (and maybe not purged at every restart) and big events/notifications in another spot.  Oh if I were to make one tiny suggestion with the logs, that would be to trim off any extra formatting goodness, like colors or fonts.  They look sick in the widget but make the logs harder to work with.  Just my two Sats. Is it just me or is the Specter portion still buggy?  I ask because I get different values for my wallet from the widget than when I open Specter itself. It’s probably on my side though, I see strange results when I run the Bitcoin-cli command getbalances nothing is returned.  Still more troubleshooting on my side…Thank you for the opportunity to help out. EthanOn Sun, Aug 8, 2021 at 4:18 PM, Alpha Zeta ***@***.***> wrote: Great suggestions. Keep them coming. Working on this - there's a much better method already running on background that is more efficient. Will transition soon. If I understand correctly, the suggestion is to create a log file with more detailed data, including connections to Specter, correct? Working on that. Right now the Log Widget works more like a "Notifications" widget. Should split into a detailed debug.log file and Notifications. Specter_importer.py is a more comprehensive library that I worked for a different project so it contains more endpoint requests. They are unused here. Soon I will include authentication to Specter so the auth/login endpoint will probably be used. —You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.