Fix secrets, add "update secret" endpoint, fix search bar RWD

Pull Request Description

Fix https://github.com/enso-org/cloud-v2/issues/828

Fix appearance of search bar on small screens

Close https://github.com/enso-org/cloud-v2/issues/830

Rename "Data Connector" back to "Secret" for now
Fix "create secret" endpoint
Add "update secret" endpoint

Repurpose "create secret" modal to also be usable for updating secrets
Add new context menu option for editing secrets
Add new shortcut (Ctrl+E) for editing secrets
Add double-click trigger for editing secrets

Fix https://github.com/enso-org/cloud-v2/issues/831

Add the redirect, that was previously missing (only present in the very old dashboard)

Fix https://github.com/enso-org/cloud-v2/issues/835

Fix search query not updating when clicking label in sidebar
Fix search query breaking when clicking a suggested label, after tabbing into a selection

Important Notes
None
Screencast
https://github.com/enso-org/enso/assets/4046547/3be89985-0882-4967-bedb-951db3ea9969
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

ignore the stretching of the screen at the end, that's because webm supports resizable videos but mp4 doesn't.
the important thing to note though, is that the search bar no longer does anything funky at any screen size

create_secret now returns just secretId encoded in json (with "). We should either adjust frontend to expect just string or I could add return_type optional param with json as value. @somebody1234 wdyt?

also ctrl+e is not working on mac

yup, frontend should already expect string.
as for the shortcut, I guess I'll change it - maybe it's being overridden by a system shortcut

@somebody1234 qa 🟢 I aslo approved. Please fix ci actions and you can put ready to merge


Implement finalizer and NATS account deletion for Account object

Also should cleanup Account reconcile logic now that server-side apply supports no-op.

Account has been renamed to Namespace and no longer uses NATS accounts under the hood. Hence, this issue is no longer valid.


Aspect ratio is not always kept because of snapping to grid.

After setting the preserveAspectRatio option to true, I observed that not all the elements actually keep the aspect ratio.
For ratio = 1, everything seems to be fine, but for other aspect ratios, it doesn't seem to work because of the snapping back to grid.
When I'm resizing the element, I can see that it has the correct aspect ratio, but when dropping it, because it takes the closest place in the grid, it doesn't always takes into account the aspect ratio.
I found a fix to ensure that the aspect ratio is preserved if the preserveAspectRatio option is true and I will add a PR asap.

@gmsa is this something you plan support in the library?


Implement Action update

Generic action update
support for Action Update in health check
support for fingerprint
support for Action Update in backend service

assign/ @Bowei
cc/ @mag-kol


update the readme file

Describe the bug
the "npm dev " command is getting  error
Expected behaviour
without error
Screenshots
No response
Additional context
No response

Sure @akshaya-hub assigning it to you, go ahead
additionally I would also prefer if you can delete the yarn.lock file in the front end, I believe as we are using npm, that file is not needed anymore.

@J0SAL  ok so should i delete the whole yarn.lock file

@J0SAL ok so should i delete the whole yarn.lock file

Yes!
but the one in the frontend/

@J0SAL  kk

@J0SAL  i made another pull request for yarn.lock .

@J0SAL i made another pull request for yarn.lock .

I have requested some changes, please go through it.

the read me file is still not updated, "npm dev" change it to "npm run dev"

@SagarSharma2809 @J0SAL  yes i have raised the PR  but not yet merged


just for windows OS ?

can i use it in linux 、Mac？

As far as I know, that isn't possible (at least not with the provided natives)

There are alternatives.
Please check https://github.com/dstjacques/JHotKeys, it is a wrapper for JIntellitype (Windows) and JXGrabKey (Linux).
Keep in mind, that the behavior could be in detail different to system-hook!

Hello ljheee, luecking and markozajc are right, JSysHook currently ONLY supports Windows! There are already issues addressing this (#20, #27), but currently I don't find any time to drive the impelemtnation personally. In case you'd like to take that, please feel free to raise a pull request. I will close this issue as a duplicate to the two linked issues. Thanks.


Init benches

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (cfe8e11) 88.40% compared to head (ff7afae) 88.40%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   88.40%   88.40%
=======================================
  Files          19       19
  Lines         742      742
=======================================
  Hits          656      656
  Misses         86       86

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


HEAD Request support

Support request for HEAD additionaly to GET POST etc.
This is usefull for checking if the endpoint output changes, saves CPU/Bandwitdh etc (in certain cases)

Appearently it works i just put
    Restivus.addRoute 'test',
	    get: ->
		return 1
	    head: ->
		return {
			statusCode: 200,
			headers: {
				'X-HEAD': 'customheader',
			},
			body: {
				status: 'lol',
				data: {
					message: "noey"
				}
			}
		};

when i do
curl -X HEAD -i http://localhost:3004/test/
i get:
HTTP/1.1 200 OK
Content-Type: text/plain
Date: Wed, 03 Jun 2015 12:56:25 GMT
Connection: keep-alive
But i noticed the connection is not closing. Any idea?

I'll look into this later tonight. I was living in a fantasy world where I assumed that the HEAD responses were being automatically handled. I'll run some tests and get back to you. This certainly sounds like a bug, so I'll mark it as such.

Sorry for the delayed response on this. I was able to get the connection to close, but HEAD requests aren't returning any useful information from what I can tell.
To get the connection to close, apparently you just have to tell it to (from this stack overflow answer:
curl -i http://localhost:3000/api/override-default-heade -X HEAD -H "Connection: close"

or if you want something curl-specific, you can use the -I option:
 curl -i http://localhost:3000/api/override-default-heade -X HEAD -I

However, as I mentioned, HEAD requests don't seem to be returning any useful information. I got the same response you posted above even when I sent requests to non-existent endpoints. I shamefully assumed that this was something that just worked in HTTP, but that was a false assumption.
Apparently a HEAD should return the headers from a GET request, but I'm not quite sure how to do that without actually calling the GET endpoint to get the headers set and then stripping away the body, which would destroy the whole "saving CPU" concept. What information are you looking to obtain about the endpoint? You mentioned checking if the "endpoint's output changes." When you say the "endpoint's output," are you referring to the response data, or the underlying resource? In my experience, HEAD requests are used to check things like the last modified time of some underlying resource (e.g., a file). I suppose that functionality could be carried over to collection endpoints, if users maintain some sort of lastModified field on a document. My goal is to make Restivus more modular, so features like these would probably wind up in the restivus-collections package, or maybe even an add-on package for that (to make things really modular).
I plan to add a default OPTIONS endpoint in v0.8.0 (you can already setup your own default OPTIONS endpoint on the 0.8.0 branch) that will return the accepted HTTP methods, and my hope is to someday bring support for API documentation via OPTIONS.

@kahmali I'm seeing this as well, any news for us? :)


Built and Tested MacForge

Just wanted to give a small review even though I know this is a beta software and not released yet. :)
So far works great!  I especially like the fact that macOS doesn't ask for permission every time MacForge tries to inject a plugin like it used to with Mojave/mySIMBL.
Even my plugin (EnhanceDiskUtil) worked that somehow compatibility broke when I updated to Mojave.
Keep up the good work.

Thanks for the feedback!


Casting options without menu-items

Hi! It all works fine now, casting a unique view to 3 different devices.
However, the menu-bars (marked red in picture) are a bit annoying, can these be removed by any options?
Not sure it its the correct place to ask, but I'll Try..

Resolved... Did not realize at first that the "URL+?kiosk" required an HACS plugin named "kiosk-mode". Installed, and all OK.

Hey, yes you can use Kiosk Mode to remove these menu bars 😄
https://github.com/NemesisRE/kiosk-mode

Just seen your comment! - Good to hear.

I'll also add that note to the readme. Thank you


okHttpCookieJar tests added

Coverage increased (+0.3%) to 45.866% when pulling 214d604404f5d83f8bbd35b699060fd628efcc20 on maqzi:cookies into 1726fe6204ebfab9f758a3f89208d47cf97fbe75 on ViDA-NYU:cookies.


iCloud v3, Beta Testers List - Latest Version: Beta 9, 1-22-2023

Please add your username to this thread so I can easily notify you of any updates. Also add a comment to this Issue. Then you will be notified when a new version is available. It will also help me keep track of who is testing it and the number of people that are giving it a try.
Do not download from HACS. The beta is not available on HACS. If you download from HACS, v2.4.7 will overwrite the iCloud3 directory, wiping out the v3 beta and you will have to start over.

iCloud3 v3 Documentation can be found here
Download from the Release page here. Select Assets, then select icloud3-beta-#.zip. or,
All of the Change Logs can be found here

I'll post a notice to this Issue when a new beta version is available. I'll add it to the bottom of this Issue and it will list of what changed.
Thanks
Gary.

garyak will be testing.

Hans is on the test

Peter (poudenes > on GitHub and HA)

marcelof will be testing as well

Commencing with testing.

bgnzo is available to test

bgnzo available for testing

Beta 2 has been posted. You will find it here
Beta 2 change log:

Do not display an error messgage when trying to get the model of a device if t is
not in the HA device registry. (entity_io:137)
Fix a problem checking if info for all of configured devices that had been set
up had been returned from iCloud account during startup. If not, the FmF devices
were being refreshed when it should be refreshing the FamShr devices. (start_ic3:1315)
Fixed an error copying the Event Log image sample files to the custom cards directory.
It was copyingthe files from 'event_log' instead of 'event_log_card'. (start_ic3:722)
Added 'Erase All Devices' to the Configuration > Action menu that will reinitialize the
iCloud3 Devices List.
The Time Format (12/24-hour) was converted incorrectly. It was creating '12/24-hour-hour'
This has been fixed and the invalid parameter in the configuration file was corrected.
Fixed a problem where a check was being made to see if 2fa authentication was needed when
the connection to the iCloud Location Services had not been completed, causing a problem
with the parameter migration (icloud_main:732).
Reformatted the items written to the icloud3_migration.log file for clarity.
Fixed a problem shrinking the Event Log (event_log:538 recursion error).
Fixed a problem when Family Sharing info from iCloud Location Services had not completely
loaded during initialization and was generating an error during the retry operation (start_ic3:1113).
Fixed a problem, hopefully, that was generating the HA Blocking error when starting up the iCloud Location Services interface. This was also occurring (sometimes) when logging into a new the iCloud account from the Configurator.

Hi. Please let me try. Do we use the b1?Is that the latest?

No. Beta 2

No. Beta 2 here

Got it, didn't see it, but saw references to it. Thanks.

Ho Ho Ho. Happy holidays. 🎄🎅
If you don’t have plans, enjoy iCloud3 v3.0.0 beta 3
Gary

Ho. Ho. Ho. Happy holidays.🎄🎅
If you don’t have any plans, enjoy iCloud3 v3.0.0 beta 3
Beta 3 - 12/24/2022

Fixed a problem where the Configurator > Sensors would generate an 'Unknown Error Ocurred'
error message. This was caused by an invalid sensor field name ('tracking_from_zones')
in the configuration file.
Fixed a problem on the Configurator > Sensors screen dealing with an invalid 'battery_status'
error message.
Fixed a problem where error messages were displayed getting device info from the HA device
registry when the device was not in the registry.
Fixed a problem displaying the obscured email address if there was more than one @-sign
in the address.
Added 'Reinitialize All Devices' to the Configurator > iCloud3 Devices screen. With it,
you can remove all devices from iCloud3 or reset the selections for the iCloud FamShr & FmF
and the iOS App parameters to None. This will clear any errors due to device migration errors.
Setting up the log_level (info, debug, rawdata) a lot earlier. It is now setup when HA loads iCloud3
instead of later. Debug and RawData information should now be written to the HA Log file
(home-assistant.log) when the iCloud Account connection is first established.
Moved Event Log Configuration option to Menu Page 1 and moved Display Text As option to Menu
Page 2. Also added the Log Level parameter to the Event Log Configuration screen. This
will reduce the steps needed to change the Log Level parameter when debug/rawdata logging
is desired. ---> YOU MAY NEED TO REFRESH YOUR BROWSER WITH THE CONFIGURATOR OPEN <---
Fixed problem changing the devices Friendly Name that would generate an error message deleting
tracking_from_zone sensors when they had not been created.
The device_tracker state value is now lower-case.
Log level debug and rawdata records are now written to the '/config/icloud3_debug.log' file
instead of the HA log file. A new file is created every time HA starts.
The file extension for the Event Log file was changed from '.txt' to '.log'. The file name is now
'icloud3-event-log_[time].log'.

Pauly7300 Testing.  Loving it so far.

Mobiledude testing

installed and testing.

Beta 4 is alive and ready to be downloaded.
It fixes a few things, add a few others and finalizes the icloud3-debug.log handling. I also have a question at the end about the naming of the Event Log exported file...should it have the date as part of the file name so every export is unique or should it just be 'icloud3-event-log.log' so each export overwrites the previous one.
The change log follows and has fewer items than beta 3. Yea, and thanks to all.
Beta 4 - 12/17/2022

Inactive/Untracked devices are listed at the end of the Startup Event Log messages.
Fixed some problems displaying the EVent Log when there were no devices to track.
Fixed problem dealing with Gb.ic3_debug_log_write_secs variable not found.
Fixed problem where the Event Log records were not displayed in a timely manner when starting.
The tracking results written to the Log file now include the zone, distance and time values.
Reworked the icloud3-debug.log file:
- A new file is created when:
- HA/iCloud3 starts and the Log Level is debug or rawdata or
- Starting Debug Logging from Event Log > Actions or
- At midnight when debug logging is on and the file is more thn 20-hours old.
- Otherwise debug records are added to the existing Debug Log file.
- If the Log Level is debug or rawdata in the Configurator > Event Log parameters and
Stop Debug Logging was selected on Event Log > Actions, the ic3 config will be changed
to 'info' (no debug logging).
- If the configuration is set to 'info' (no debug logging) and it is started on
Event Log > Actions, the configuration is not updated and the debug logging will
remain on until midnight, the next iCloud3 restart or when it is turned off.

QUESTION: Currently the Exported Event Log file contains the date/time indicating when it was created.
This creates a new file for every export.
Example: 'icloud3-event-log_2022-12-26 18:00:00.log'
Another option is to not have the date/time in the file name so a new Export overwrites
the last one.
Example: 'icloud3-event-log.log'
      Does anyone have an opinion on this.

I like having the datestamp in the file name.

On Dec 27, 2022, at 5:59 PM, Gary Cobb @.***> wrote:
Beta 4 is alive and ready to be downloaded.
It fixes a few things, add a few others and finalizes the icloud3-debug.log handling. I also have a question at the end about the naming of the Event Log exported file...should it have the date as part of the file name so every export is unique or should it just be 'icloud3-event-log.log' so each export overwrites the previous one.
The change log follows and has fewer items than beta 3. Yea, and thanks to all.
Beta 4 - 12/17/2022
Inactive/Untracked devices are listed at the end of the Startup Event Log messages.
Fixed some problems displaying the EVent Log when there were no devices to track.
Fixed problem dealing with Gb.ic3_debug_log_write_secs variable not found.
Fixed problem where the Event Log records were not displayed in a timely manner when starting.
The tracking results written to the Log file now include the zone, distance and time values.
Reworked the icloud3-debug.log file:

A new file is created when:

HA/iCloud3 starts and the Log Level is debug or rawdata or

Starting Debug Logging from Event Log > Actions or

At midnight when debug logging is on and the file is more thn 20-hours old.

Otherwise debug records are added to the existing Debug Log file.

If the Log Level is debug or rawdata in the Configurator > Event Log parameters and
Stop Debug Logging was selected on Event Log > Actions, the ic3 config will be changed
to 'info' (no debug logging).

If the configuration is set to 'info' (no debug logging) and it is started on
Event Log > Actions, the configuration is not updated and the debug logging will
remain on until midnight, the next iCloud3 restart or when it is turned off.
QUESTION: Currently the Exported Event Log file contains the date/time indicating when it was created.
This creates a new file for every export.
Example: 'icloud3-event-log_2022-12-26 18:00:00.log'
Another option is to not have the date/time in the file name so a new Export overwrites
the last one.
Example: 'icloud3-event-log.log'
Does anyone have an opinion on this.

—
Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3_v3/issues/2#issuecomment-1366245057, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDD4KC2VVE4JXJ2NB3PCBDWPNYEJANCNFSM6AAAAAATCEGWJY.
You are receiving this because you commented.

Im testing as well

Oops. I forgot to change the iCloud3 beta version number from b3 to b4 on the update. I fixed that but have not created a new release. Just download beta 4 again.

Hi Gary, good morning.
I’m having a hard time to upgrade from 2.4.7 to 3.0 so I have decided to start from scratch using a virtual machine.
After installing Beta4 I restarted HA. After restart and trying to login to my apple account it get stuck with the spinning circle and never goes to the next page, although I still receive and apple icloud notification that someone is trying to log in to my account.
@.***
I tried to delete both icloud and icloud3 folders under .storage folder and restart but it didn’t work.
Thanks in advance,
Marcelo Franco
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: Gary @.>
Sent: terça-feira, 27 de dezembro de 2022 20:54
To: @.>
Cc: @.>; @.>
Subject: Re: [gcobb321/icloud3_v3] iCloud v3.0.0 Beta - User List (Issue #2)
Oops. I forgot to change the iCloud3 beta version number from b3 to b4 on the update. I fixed that but have not created a new release. Just download beta 4 again.
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgcobb321%2Ficloud3_v3%2Fissues%2F2%23issuecomment-1366266243&data=05|01||55a860a6b6fd4fdc7f3e08dae865bd94|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638077820922721699|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Xo%2F%2FQQSt7mn74dDj53QemzuuPspKD4upcZiNhExGVbQ%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYEHS6EZMK4KWB2BOJYPBDWPN6URANCNFSM6AAAAAATCEGWJY&data=05|01||55a860a6b6fd4fdc7f3e08dae865bd94|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638077820922877921|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=kw9Y8%2F7ju8iP5DVvhRhJLIIpKjVswc1CGwcbKXaYduM%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

Marcelo,

FYI-The config/.storage/icloud directory contains the icloud account
cookies & session verification info so there is no need to delete that.
The config/.storage/icloud3 contains the icloud3 parameter and utility
files.
On the restart, does it show any errors in the HA log file?
Did you go to the iCloud Account Login Credentials screen and select
Login or something else? AppleID/password OK?
Did the HA Notifications show an alert (orange bell) that indicates
the verification code is needed? If Yes, select it and enter the
verification code. Maybe it was waiting for the code to be entered (The
spinning circle indicates HA is waiting for something to happen since it
has control at that point).
What does restarting HA do? I do not know what running on a virtual
machine would do?
Restart HA and go to iCloud3 Configurator > Event Log Configuration.
Change Log Level to Rawdata. This will dump the iCloud Account rawdata
to /config/icloud3-debug.log and show all the network traffic between
you and your iCloud account.
Restart HA again to start the Debug Log from scratch.
See if you are logged into your iCloud account. Make sure you can
enter the 6-digit verification code. Check the iCloud3 Devices screen to
see if your devices are listed.
Can you see the Event Log screen (iCloud3 v3) is the on the title
line at the top? if yes, do Actions > Export Event Log.

email the icloud3-event-log_[datetime],log and icloud3-debug,log to
@.*** and I'll take a look at them.
Gary Cobb
------ Original Message ------
From "marceloaf" @.>
To "gcobb321/icloud3_v3" @.>
Cc "Gary Cobb" @.>; "Author"
@.>
Date 12/28/2022 9:12:52 AM
Subject Re: [gcobb321/icloud3_v3] iCloud v3.0.0 Beta - User List (Issue
#2)

Hi Gary, good morning.
I’m having a hard time to upgrade from 2.4.7 to 3.0 so I have decided
to start from scratch using a virtual machine.
After installing Beta4 I restarted HA. After restart and trying to
login to my apple account it get stuck with the spinning circle and
never goes to the next page, although I still receive and apple icloud
notification that someone is trying to log in to my account.
@.***
I tried to delete both icloud and icloud3 folders under .storage folder
and restart but it didn’t work.
Thanks in advance,
Marcelo Franco
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for
Windows
From: Gary @.>
Sent: terça-feira, 27 de dezembro de 2022 20:54
To: @.>
Cc: @.>; @.>
Subject: Re: [gcobb321/icloud3_v3] iCloud v3.0.0 Beta - User List
(Issue #2)
Oops. I forgot to change the iCloud3 beta version number from b3 to b4
on the update. I fixed that but have not created a new release. Just
download beta 4 again.
—
Reply to this email directly, view it on
GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgcobb321%2Ficloud3_v3%2Fissues%2F2%23issuecomment-1366266243&data=05|01||55a860a6b6fd4fdc7f3e08dae865bd94|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638077820922721699|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Xo%2F%2FQQSt7mn74dDj53QemzuuPspKD4upcZiNhExGVbQ%3D&reserved=0,
or
unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYEHS6EZMK4KWB2BOJYPBDWPN6URANCNFSM6AAAAAATCEGWJY&data=05|01||55a860a6b6fd4fdc7f3e08dae865bd94|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638077820922877921|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=kw9Y8%2F7ju8iP5DVvhRhJLIIpKjVswc1CGwcbKXaYduM%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub
https://github.com/gcobb321/icloud3_v3/issues/2#issuecomment-1366682892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIOOVB5OPOI764SJ3ZFOFZLWPRDGJANCNFSM6AAAAAATCEGWJY.
You are receiving this because you authored the thread.Message ID:
@.***>

For me, the primary reason I have referenced the previous version of the
icloud3-event log file was for comparison.  IE, to see if a change I made
to a config produced a different outcome.  I guess my preference would be
to keep the current behavior.  Cleaning up (deleting) the old ones really
isn't that much overhead.  Anyone that cares enough to generate an
ic3-event-log knows where it is and it doesn't seem like a hassle to remove
unwanted versions but of course that's just one opinion.
On Tue, Dec 27, 2022 at 4:59 PM Gary Cobb @.***> wrote:

Beta 4 is alive and ready to be downloaded.
It fixes a few things, add a few others and finalizes the
icloud3-debug.log handling. I also have a question at the end about the
naming of the Event Log exported file...should it have the date as part of
the file name so every export is unique or should it just be
'icloud3-event-log.log' so each export overwrites the previous one.
The change log follows and has fewer items than beta 3. Yea, and thanks to
all.
Beta 4 - 12/17/2022

Inactive/Untracked devices are listed at the end of the Startup
Event Log messages.
Fixed some problems displaying the EVent Log when there were no
devices to track.
Fixed problem dealing with Gb.ic3_debug_log_write_secs variable not
found.
Fixed problem where the Event Log records were not displayed in a
timely manner when starting.
The tracking results written to the Log file now include the zone,
distance and time values.
Reworked the icloud3-debug.log file:

A new file is created when:
HA/iCloud3 starts and the Log Level is debug or rawdata or
Starting Debug Logging from Event Log > Actions or
At midnight when debug logging is on and the file is more thn
20-hours old.
Otherwise debug records are added to the existing Debug Log file.
If the Log Level is debug or rawdata in the Configurator > Event Log
parameters and
Stop Debug Logging was selected on Event Log > Actions, the ic3 config
will be changed
to 'info' (no debug logging).
If the configuration is set to 'info' (no debug logging) and it is
started on
Event Log > Actions, the configuration is not updated and the debug
logging will
remain on until midnight, the next iCloud3 restart or when it is
turned off.

QUESTION: Currently the Exported Event Log file contains the date/time
indicating when it was created.
This creates a new file for every export.
Example: 'icloud3-event-log_2022-12-26 18:00:00.log'
Another option is to not have the date/time in the file name so a new
Export overwrites
the last one.
Example: 'icloud3-event-log.log'
  Does anyone have an opinion on this.

—
Reply to this email directly, view it on GitHub
https://github.com/gcobb321/icloud3_v3/issues/2#issuecomment-1366245057,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXWFJCJMN5GK6WMKX3U4SDWPNYEJANCNFSM6AAAAAATCEGWJY
.
You are receiving this because you commented.Message ID:
@.***>

I just uploaded Beta 5 -- It fixes a error message that is displayed sometimes at start up, adds some enhancements to the Event Log and updates the Event Log Lovelace card that will require a browser refresh on all devices running HA (you will see a message on each device with instructions for that device).
The exported Event Log log report name stays as it is. The vote was 2 (don't mess with the name) to 0 (one EvLog file is plenty). Thanks for the feedback.
Here is the Change List (2 minor bugs fixed, 2 enhancements to the Event Log):

Fixed a 'log_info_msg' not defined error message in the routine that identifies the notify
service  used for a device. This is just an informative message indicating HA has not set it
up yet.
Periodically, the events currently displayed for a device is reduced from all events to less
than a screen. This number was increased from 1/2-screen to about 2-screens.
When the displayed events for a device were reduced (#2 above), the screen was never refreshed so you would always see the old events and had to do a refresh to see the latest events. Now, the device's events are automatically refreshed when they are updated.
Updated the Event Log Lovelace card to v3.0.1. This fixes a problem when the date/time should not  be displayed if there was an alert message was displayed.

I was just about to send all the logs from the tests I did with Beta4 but I will try again tomorrow with Beta5. Thanks

@marceloaf  Go ahead and send them. The items i fixed probably would not have anything to do with your issues.

Hi Gary. Here they are.
My responses are below. Just for your information I created a brand new Home assistant environment in a virtual machine running on Virtual Box. The only addons I’m running are SAMBA, DuckDns and NGINX. I registered a specific duckdns domain for this test and configured my router and certificates to enable login using https from outside. A bit suspicious NGINX throwing some errors at the same time I was trying to authenticate in icloud through icloud3
I also tried to cover my apple credentials in the logs… 😊
I’m not sure if the attachment is also posted on github. If so, could you please delete them from the thread?
Many thanks in advance
From: Gary Cobb<EMAIL_ADDRESS>Sent: Wednesday, December 28, 2022 11:59 AM
To: gcobb321/icloud3_v3<EMAIL_ADDRESS>Cc: marceloaf<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [gcobb321/icloud3_v3] iCloud v3.0.0 Beta - User List (Issue #2)
Marcelo,

FYI-The config/.storage/icloud directory contains the icloud account
cookies & session verification info so there is no need to delete that.
The config/.storage/icloud3 contains the icloud3 parameter and utility
files.
Ok

On the restart, does it show any errors in the HA log file?
Yes, some errors are shown immediately and others as the HA runs for some time.

Did you go to the iCloud Account Login Credentials screen and select
Login or something else? AppleID/password OK?
Initially I left on the default option (SAVE), filled the apple id and password and then SUBMIT. But I also tested with the Login option and the behavior is the same. The id and password are correct because I’m receiving the 2fa 6 digit code when I try to save the credentials and log in.

Did the HA Notifications show an alert (orange bell) that indicates
the verification code is needed? If Yes, select it and enter the
verification code. Maybe it was waiting for the code to be entered (The
spinning circle indicates HA is waiting for something to happen since it
has control at that point).
No, it didn’t show any orange alert/notification

What does restarting HA do? I do not know what running on a virtual
machine would do?
Sometimes I receive the 2fa 6 digit code as someone is trying to log on but whenever I try to enter it on the code verification menu it fails with unknown error

Restart HA and go to iCloud3 Configurator > Event Log Configuration.
Change Log Level to Rawdata. This will dump the iCloud Account rawdata
to /config/icloud3-debug.log and show all the network traffic between
you and your iCloud account.
Ok

Restart HA again to start the Debug Log from scratch.
I did it and am attaching some errors collected during the tests

See if you are logged into your iCloud account. Make sure you can
enter the 6-digit verification code. Check the iCloud3 Devices screen to
see if your devices are listed.
I didn’t not work

Can you see the Event Log screen (iCloud3 v3) is the on the title
line at the top? if yes, do Actions > Export Event Log.

email the icloud3-event-log_[datetime],log and icloud3-debug,log to
<EMAIL_ADDRESS>and I'll take a look at them.
Gary Cobb
------ Original Message ------
From "marceloaf"<EMAIL_ADDRESS>To "gcobb321/icloud3_v3"<EMAIL_ADDRESS>Cc "Gary Cobb"<EMAIL_ADDRESS>"Author"
<EMAIL_ADDRESS>Date 12/28/2022 9:12:52 AM
Subject Re: [gcobb321/icloud3_v3] iCloud v3.0.0 Beta - User List (Issue
#2)

Hi Gary, good morning.
I’m having a hard time to upgrade from 2.4.7 to 3.0 so I have decided
to start from scratch using a virtual machine.
After installing Beta4 I restarted HA. After restart and trying to
login to my apple account it get stuck with the spinning circle and
never goes to the next page, although I still receive and apple icloud
notification that someone is trying to log in to my account.
<EMAIL_ADDRESS>I tried to delete both icloud and icloud3 folders under .storage folder
and restart but it didn’t work.
Thanks in advance,
Marcelo Franco
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for
Windows
From: Gary<EMAIL_ADDRESS>Sent: terça-feira, 27 de dezembro de 2022 20:54
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [gcobb321/icloud3_v3] iCloud v3.0.0 Beta - User List
(Issue #2)
Oops. I forgot to change the iCloud3 beta version number from b3 to b4
on the update. I fixed that but have not created a new release. Just
download beta 4 again.
—
Reply to this email directly, view it on
GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgcobb321%2Ficloud3_v3%2Fissues%2F2%23issuecomment-1366266243&data=05|01||55a860a6b6fd4fdc7f3e08dae865bd94|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638077820922721699|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Xo%2F%2FQQSt7mn74dDj53QemzuuPspKD4upcZiNhExGVbQ%3D&reserved=0,
or
unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYEHS6EZMK4KWB2BOJYPBDWPN6URANCNFSM6AAAAAATCEGWJY&data=05|01||55a860a6b6fd4fdc7f3e08dae865bd94|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638077820922877921|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=kw9Y8%2F7ju8iP5DVvhRhJLIIpKjVswc1CGwcbKXaYduM%3D&reserved=0.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHub
https://github.com/gcobb321/icloud3_v3/issues/2#issuecomment-1366682892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIOOVB5OPOI764SJ3ZFOFZLWPRDGJANCNFSM6AAAAAATCEGWJY.
You are receiving this because you authored the thread.Message ID:
<EMAIL_ADDRESS>
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgcobb321%2Ficloud3_v3%2Fissues%2F2%23issuecomment-1366712041&data=05|01||391998e6175549fab09508dae8e4144c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638078363537336572|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=5U%2F0d3ZOeeodTSFjsNrAqdJP8SaAg12Ltf44Sb3sQG8%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYEHS3GA7HYH4RY6OECQADWPRIT7ANCNFSM6AAAAAATCEGWJY&data=05|01||391998e6175549fab09508dae8e4144c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638078363537336572|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=%2B3CrOPjVH9h0qYz5ORfRDGfNNSkxmA9yNhCL5bky5v0%3D&reserved=0.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

Gary, maybe i'm downloading the wrong thing but the descriptions on the zip files in the beta archive seem like they're off.  Beta 4a has a description of 'Beta 5'.

@pauly7300
That refers to the description of the update, not the file to download.
Download from the Release page here. Select Assets, then select icloud3-beta-#.zip.  or,
Download directly from the Code page here

Beta 6, Beta 6, Beta 6 - It's the weekend so, now that the holidays are almost over, it's time to download the latest beta version. This fixes a few minor issues, makes sure the Debug Log is recreated when iCloud3 is restarted, adds an autorefresh function to the Event Log, speeds up the display of the Initial Locate and a few other things. Details are below.
Download from the Release page here. Select Assets, then select icloud3-beta-#.zip. or,
Download directly from the GitHub Code page here. Click download on the right side of the screen.
Change Log:

Corrected a mispelled directory name used for installing sample device images (ipad.png, watch.png). The image directory nane was 'event_log_cad'. It should be 'event_log_card'.
A new icloud3-debug.log file will now be created when restarting iCloud3 from the Event Log or when HA was started and the log level is debug. New records will be added to the existing log file when debug is started from Event Log > Actions and the log file is less than 20-hours old.
Fixed a problem where location data from iCloud FamShr/FmF was not always being rejected due to poor gps_accuracy. This could lead to location & zone errors until the next locate was processed.
Improved the performance displaying the results of the Initial Device Locate results in the Event Log.
The Event Log for the selected devices is automatically refreshed when new information is added. The number of items was increased from 15 to 50 so more events are displayed without refreshing.
Added a prefilter to the rawdata debug log to make sure usernames & passwords are not displayed.
Some internal code cleanup and minor tweaking.

Thanks everyone for helping me make sure iCloud3 is as solid as a rock. I appreciate your comments, suggestions and working through some of the things you have found.
Wishing you all the best for 2023.

Thanks for building this out, it’s much appreciated.  Have a great 2023 as well.

On Dec 31, 2022, at 6:59 PM, Gary Cobb @.***> wrote:
Thanks everyone for helping me make sure iCloud3 is as solid as a rock. I appreciate your comments, suggestions and working through some of the things you have found.
Wishing you all the best for 2023.
https://user-images.githubusercontent.com/35449479/210157805-e5a95263-c421-496c-a86a-3b33d00cf866.GIF
—
Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3_v3/issues/2#issuecomment-1368295698, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDD4KDLHL6XXKDAXOC3PADWQDCEZANCNFSM6AAAAAATCEGWJY.
You are receiving this because you commented.

Thanks for building this out, it’s much appreciated.  Have a great 2023 as well.

On Dec 31, 2022, at 6:59 PM, Gary Cobb @.***> wrote:
Thanks everyone for helping me make sure iCloud3 is as solid as a rock. I appreciate your comments, suggestions and working through some of the things you have found.
Wishing you all the best for 2023.
https://user-images.githubusercontent.com/35449479/210157805-e5a95263-c421-496c-a86a-3b33d00cf866.GIF
—
Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3_v3/issues/2#issuecomment-1368295698, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDD4KDLHL6XXKDAXOC3PADWQDCEZANCNFSM6AAAAAATCEGWJY.
You are receiving this because you commented.

Was dealing with an all hands-on-deck hot ticket at work for the last few weeks, but I am now clear to test.  Please sign up diothar for testing if possible.

Was dealing with an all hands-on-deck hot ticket at work for the last few weeks, but I am now clear to test.  Please sign up diothar for testing if possible.

Testing. Thanks!

Testing.

Testing, looking good!

I will be testing as well

J-Fartz is testing

Beta 8, Beta 8, Beta 8

Fixed the problem accessing the iCloud3 Devices screen. Again. I hope. The problem is a timing issue and an issue between HA and requesting data from the iCloud Account. I tried a completely new approach and hope it works this time.
The Waze server selection method was changed so it is in line with how Waze does it. (US/Canada, Israel, Rest of the World).
The battery and battery status updates have been fixed so the battery level is reported every 15-seconds like it was suppose to have been.
Fixed an when 3 or more devices where sharing their location and iCloud3 would stop updating everyone's location.
And a few more issues..

See the change list below for the details.
Download from the Release page here. Select Assets, then select icloud3-beta-#.zip. or,
Download directly from the GitHub Code page here. Click download on the right side of the screen.
All of the Change Logs can be found here
Change Log

Fixed the bug accessing the iCloud3 Devices screen. Again. I hope. It is a timing issue and an
issue with accessing the iCloud Account through HA. I could make it fail yesterday but not today
when trying to verify that the new approach fixed it. For those that are having this problem,
please let me know if you are still having a problem and I'll take another crack at it.

The Waze Route Service is handled by 3-servers around the world - United States/Canada, Israel,
and the Rest of the World. The HA Country Code is now used to determine that
the appropriate server is used. It is still shown on the Waze configuration screen for
information only. It is verified and corrected when HA starts if the wrong server is selected.

Combined the configuration screens for the Waze Route Server and Waze History Database into one
screen. THIS MAY REQUIRE A BROWSER CACHE REFRESH

Added the 'iCloud3 Theme' that tweeks the field labels in the Configurator so the descriptive
text is a little more readable (at least for me with my old eyes). It has both a light and dark
mode and only a few entries. You can find the it in config/custom_components/icloud3/theme.
Move the 'iCloud3 Theme' from the 'icloud3/theme' folder to the 'config/themes' folder.
(1) If you are already using a theme, copy the 'icloud3_theme.yaml' file statements (both the
light and dark mode) into the appropriate location in your theme's yaml file. Then restart HA.
(2) If you are not using a theme, restart HA, open your Profile screen, then select 'iCloud3 Theme'
on the Themes list.
I used it when capturing screenshots for the iCloud3 documentation.

Fixed a number of problems with the battery and battery status sensors. (1) It was being updated
by the iOS App every 15-minutes instead of every 5-seconds. (2) The value was resetting to 0 when
HA or iCloud3 restarted instead of restoring it's value from the last update. (3) It was not being
updated when iCloud3 restarted until the next poll, which may be 2-hours if you are in a zone.
(4) It was only being saved to the restore_state file on the next poll, not the value when it
changed in the iOS App. Again, if you are in a zone, the value might be 2-hours old from the last
iCloud update, leading to drops and spikes in the battery sensor in the HA history.

Fixed a problem that might cause iCloud3 to hang when you are tracking 2 or more devices and they
are all close to eack other. The problem occured when device A was using device B tracking results
(distance, travel time, next update time, etc), B was using C, and C was using A. This created a
circular loop so every device used the same data and a new update was never done.

Addressed a problem building the picture file list for the iCloud3 Devices screen. I can not
reproduce the error but changed some code so the error being encountered would not occur.

After upgrading from b7 to b8 I'm getting the following errors constantly in the HA log file:
2023-01-14 22:08:05.084 ERROR (SyncWorker_10) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'
2023-01-14 22:08:05.085 ERROR (SyncWorker_10) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'
2023-01-14 22:08:05.087 ERROR (SyncWorker_10) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'
2023-01-14 22:08:05.088 ERROR (SyncWorker_10) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'

Also, when trying to EDIT DEVICES in the configuration menu I just get "Unknown error occurred" and the following in the log file:
2023-01-14 22:08:00.130 ERROR (SyncWorker_11) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'
2023-01-14 22:08:00.132 ERROR (SyncWorker_11) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'
2023-01-14 22:08:00.133 ERROR (SyncWorker_11) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'
2023-01-14 22:08:00.134 ERROR (SyncWorker_11) [icloud3] invalid literal for int() with base 10: 'not_set'
Traceback (most recent call last):
  File "/config/custom_components/icloud3/device.py", line 1382, in update_iosapp_battery_information
    self.dev_data_battery_level = int(entity_io.get_state(self.iosapp_entity[BATTERY_LEVEL]))
ValueError: invalid literal for int() with base 10: 'not_set'
2023-01-14 22:08:00.954 ERROR (MainThread) [icloud3] list index out of range
Traceback (most recent call last):
  File "/config/custom_components/icloud3/config_flow.py", line 2329, in _build_opt_picture_filename_list
    if file.rsplit('.', 1)[1] in image_extensions:
IndexError: list index out of range
2023-01-14 22:08:01.152 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 227, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 81, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 241, in post
    return await super().post(request, flow_id)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 286, in async_configure
    result = await self._async_handle_step(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 374, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/config/custom_components/icloud3/config_flow.py", line 609, in async_step_menu
    return await self.async_step_device_list()
  File "/config/custom_components/icloud3/config_flow.py", line 1559, in async_step_device_list
    self._build_device_form_selection_lists()
  File "/config/custom_components/icloud3/config_flow.py", line 2136, in _build_device_form_selection_lists
    self._build_opt_famshr_devices_list()
  File "/config/custom_components/icloud3/config_flow.py", line 2150, in _build_opt_famshr_devices_list
    devices_desc = start_ic3.get_famshr_devices(self.PyiCloud)
AttributeError: module 'custom_components.icloud3.support.start_ic3' has no attribute 'get_famshr_devices'

Thanks

@derekoharrow

The first error with the battery info is generated before everything is set up and can be ignored. I have removed the error message from displaying.
The get_famshr_devices error has been fixed. I was running b7 code in b8 and it didn't work. Will update to b8a in a few minutes.
FYI-I almost never saw these messages. I am keeping track of problems using the issues page (the bug in the Event Log takes you right to it).Thaw way, things I have to address are in one place rather than scattered around..

Thanks

I just updated Beta 8 to Beta 8a (Saturday, 6:01PM EST)

The Configuration was the beta 7 version instead of the beta 8 version. The beta 7 version did not play nice with a lot of things.
Beta 8 had a problem with the Waze Server selection based on the HA Country Code and you could not select the correct Waze server. The Servers are now alligned with Waze and you can select the one to be used for your location.

Download directly from the GitHub Code page here. Click download on the right side of the screen.

Please add me to the list - uyuarasy

Hi,
I'll be testing.
Thanks

I don't think I can see a solution above.... Is there a forum I should be posting in for questions.  Just installed the beta.  It seems to be having problems with my country code..
It is set on config.yaml
homeassistant:
  country: GB

2023-01-16 19:29:10.185 ERROR (MainThread) [homeassistant.setup] Error during setup of component icloud3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 253, in _async_setup_component
    result = await task
  File "/config/custom_components/icloud3/__init__.py", line 74, in async_setup
    v2v3_config_migration.convert_v2_config_files_to_v3()
  File "/config/custom_components/icloud3/support/v2v3_config_migration.py", line 179, in convert_v2_config_files_to_v3
    self._set_data_fields_from_config_parameter_dictionary()
  File "/config/custom_components/icloud3/support/v2v3_config_migration.py", line 570, in _set_data_fields_from_config_parameter_dictionary
    Gb.conf_general[CONF_WAZE_REGION]                = WAZE_SERVERS_BY_COUNTRY_CODE.get(Gb.ha_country_code, 'row')
AttributeError: type object 'GlobalVariables' has no attribute 'ha_country_code'

Please advise.

When you have a question or an issue, create a new issue on this forum.
About the country code error, what beta version did you install? Beta 8a is the latest.

Thanks. I installed 8a. Problem was in that version.

ive been offline since christmas but just starting to test too
First of all i tried to add via HACS (custom reposiotory pointing to _V3 but versioning isnt avalaible there atm)
I then tried to install Beta 8a from the zip posted
same issue re country code both times - no migration here this is a straight install on a new machine - AU if that matters
2023-01-17 10:35:02.296 ERROR (MainThread) [icloud3] type object 'GlobalVariables' has no attribute 'ha_country_code'
File "/config/custom_components/icloud3/__init__.py", line 144, in async_setup_entry
File "/config/custom_components/icloud3/support/v2v3_config_migration.py", line 179, in convert_v2_config_files_to_v3
File "/config/custom_components/icloud3/support/v2v3_config_migration.py", line 570, in _set_data_fields_from_config_parameter_dictionary
2023-01-17 10:35:02.304 ERROR (MainThread) [icloud3] 'NoneType' object has no attribute 'evlog_sensor_state_value'
File "/config/custom_components/icloud3/sensor.py", line 1157, in native_value

It asks if you want to setup, then asks what zone and throws the error.
If i hit 'configure' from integrations page i can then continue setup (though i havent been able to get that to work either) - as a side note perhaps need to change this alert type to a confirmation - the current css/display makes it look like an error occurred

if at all interested (and assuming i can find some time) - if you were to commit the code for v3 to this repository i could potentially provide some assistance in small fixes etc.
I have created HA integrations previously so know what i am doing in that regard

iCloud3 Beta 8b update just posted.
This fixes the problem when migrating from v2 to v3 and getting the ha_country_code not found error message.
If you are already running v3, this update is not needed. Your files have already been migrated.

@gcobb321 found the fix for https://github.com/gcobb321/icloud3_v3/issues/37
appears you commented out and changed the variable name in init.py#247 to
Gb.country_code = Gb.ha_location_info.country_code.lower()
Gb.use_metric   = Gb.ha_location_info.use_metric
# Gb.ha_country_code = Gb.ha_location_info.country_code.lower()
# Gb.ha_use_metric   = Gb.ha_location_info.use_metric

so that made support\v2v3_config_migration.py#570 throw an error
changing line 570 from
Gb.conf_general[CONF_WAZE_REGION]                = WAZE_SERVERS_BY_COUNTRY_CODE.get(Gb.ha_country_code, 'row')
to
Gb.conf_general[CONF_WAZE_REGION]                = WAZE_SERVERS_BY_COUNTRY_CODE.get(Gb.country_code, 'row')
has fixed that setup issue - onto actually setting up the integration

I checked every module and 'ha_country_code' is not being used in 8b. I must have missed it before when I went to just 'country_code' for clarity.

Sorry to say, it doesn't seem to have fixed the issue.
I deleted the icloud3 folder from custom_components.
Copied in the new one from the 8b beta zip file.
restarted multiple times.
Still getting the same error messages.........
2023-01-17 08:26:21.502 WARNING (MainThread) [icloud3] iCloud3 - Migrating Configuration Parameters
2023-01-17 08:26:21.504 ERROR (MainThread) [homeassistant.setup] Error during setup of component icloud3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 253, in _async_setup_component
    result = await task
  File "/config/custom_components/icloud3/__init__.py", line 74, in async_setup
    v2v3_config_migration.convert_v2_config_files_to_v3()
  File "/config/custom_components/icloud3/support/v2v3_config_migration.py", line 179, in convert_v2_config_files_to_v3
    self._set_data_fields_from_config_parameter_dictionary()
  File "/config/custom_components/icloud3/support/v2v3_config_migration.py", line 570, in _set_data_fields_from_config_parameter_dictionary
    Gb.conf_general[CONF_WAZE_REGION]                = WAZE_SERVERS_BY_COUNTRY_CODE.get(Gb.ha_country_code, 'row')
AttributeError: type object 'GlobalVariables' has no attribute 'ha_country_code'
2023-01-17 08:26:21.507 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform icloud3.device_tracker: Unable to set up component.

Looking at the file v2v3_config_migration, it still has this line in it....
        Gb.conf_general[CONF_WAZE_REGION]                = WAZE_SERVERS_BY_COUNTRY_CODE.get(Gb.ha_country_code, 'row')
I changed this to Gb.country_code and it seemed to fix the problem.

I am testing v3

I'm testing v3,  the only issue that I have is I can't get the zone to display, it shows up on the states for the tracker but the tracker isn't sticking when I assign the tracker to the person.  It works for me but I also have the HA app the other device doesn't at this time.   May not be anything to do with Icloud3.  Under person.name it shows a source: device_tracker.icloud3device for me.  The other person doesn't have that, but the persons configuration file under .storage list that right tracker.  Sorry if this doesn't make sense.

Hey guys. I need some help,
Last night my Rpi froze and I could no longer log into HA. I'm running a Rpi4b-8gb with an SSD (boot & data). I can access the drive via Windows SSH and have copied all code and HA backup files onto my Windows drive so I have everything to do a restore from. I can open a terminal session into the Rpi and have access the Supervisor, poked around and tried to do a restore of a backup but always get a 401 error message (whatever that means, maybe access is not available but I do not know). I've also gotten into the file system with WinSCP but having SSL issues with PuTTY. I'm ready to do a fresh install and start from scratch but hoping someone has an easy way...
I've downloaded a SD image and can burn an SD card. Then reformat the SSD, get the HA image onto the SSD, reboot, restore etc. but hoping there is an easy way to just get the HA image onto the SSD (Maybe plug it into a USB port on my windows computer which I have done and can see the boot partition).
??? Can I Etcher the HA image directly onto the SSD, put back in the Rpi, start and let HA start rebuilding everything?
??? Or reformat it via Windows so the Rpi will boot off of the SD (hopefully) and go from there.
Thanks

Oh no. That sounds like a nightmare.
I don’t have any experience doing what you are saying.
If it was me I’d probably do a clean ha install then restore a ha backup and hope all was ok.

401 is an unauthorized error. How did you get the image onto the SSD in the first place? I would recommend doing that again, then upgrading HA to the latest version if your image isn't up to date. Then take a snapshot of the fresh image, then restore the backup. If it fails after the restore, then something probably crapped out in the database or something. If that happens, then restore to the fresh install backup and try to restore an older backup file. You mentioned you have all your yaml files so you shouldn't lose more than maybe some logs.

Are you connecting directly to the ip address or are you going through an nginx reverse proxy or something? If so, try going directly to the ip address:8123 or whatever port you listen on instead.

I access it using ip::8123 on my win computer. Goint to burn the SSD with the latest HA Rpi image and plug it in and start all over. I remember putting an empty 'network' file in the boot directory of the SSD and checking that out now.

Beta 9 will be delayed to sometime this weekend, hopefully. My HA had a hard crash and I've spent all day recreating-restoring-updating-backing up-etc. On my third try.

I just uploaded Beta 9. Download it from the Release page here. Select Assets, then select icloud3-beta-#.zip)
The complete list of changes is on the Releases page but the highlights of this beta are::

Addresses some zone naming issues
Fixes a problem where iCloud3 would hang and stop tracking when determining if a near by device can be used for tracking information
Fixes some battery level/status update problems
Changes some methods logging into the iCloud account and getting device information when iC3 starts
Changes some messages and actions in the Event Log (Requires a browser refresh)
Added an Exclude Sensor screen to select specific sensor entities that should not be created

I just uploaded Beta 9. Download it from the Release page here. Select Assets, then select icloud3-beta-#.zip)
The complete list of changes is on the Releases page but the highlights of this beta are::

Addresses some zone naming issues
Fixes a problem where iCloud3 would hang and stop tracking when determining if a near by device can be used for tracking information
Fixes some battery level/status update problems
Changes some methods logging into the iCloud account and getting device information when iC3 starts
Changes some messages and actions in the Event Log (Requires a browser refresh)
Added an Exclude Sensor screen to select specific sensor entities that should not be created

It didn't fix this issue for me - I've added a comment. Do you want to re-open it?
https://github.com/gcobb321/icloud3_v3/issues/42

denac testing

I will be testing also

I am also testing. But: I already have seen an issue with updating locations per interval.
I watch 6 devices. And noticed that when a person is moving the update interval might not work anymore.
Eg. today I noticed that a person was near his work zone and the update interval for his device was 1 minute. But when I looked at it the LastUpdate was over 1.5 hours old. When I manually refreshed the location it did update correctly but then I got PassThru Zone Delay > Entered zone but may be just passing through, ZoneEntered-CncFertigung, UpdateIn-07:26:35 (1 min) but still the same: The location is not refreshed even after minutes.

Beta 10 was just released
Download it from the Release page here. Select Assets, then select icloud3-beta-#.zip)
This update fixes some problems, adds a few new features and makes some minor changes, The highlights are:

Added some FamShr & FmF checking to see if data for all configured devices was received from iCloud when starting up. If not, the data request will now be retried up to 2 times instead of giving an error that a device will not be tracked.

Added an option on the Event Log Parameter screen to display the device's device_tracker zone using the actual zone name or the zone's display_as formatted name.

Fixed a problem where the Battery and other text based sensors were displaying as numeric fields on the HA History screen.

The NearBy zone will now only uses location results from tracked devices, monitored devices are no longer used.

Fixed some problems when 2-devices in the Family Sharing list had the same name.

And some other minor fixes and tweeks.

Download from the Release page here. Select Assets, then select icloud3-beta-#.zip.
iCloud3 v3 Documentation can be found here
All of the Change Logs can be found here

I'll be testing

Thanks for all your work on this!

Fixes a problem where iCloud3 would hang and stop tracking when determining if a near by device can be used for tracking information

This seems to have fixed an issue I was seeing :thumbsup:
One issue I am seeing is that the "Stationary" zone seems to be overriding a named zone from the homeassistant configuration file. Instead of seeing person is at "NamedZone", I am seeing the person is at "Stationary". Is this by design and is there a option to change the behaviour somewhere?

@beyondwatts I just released beta 10a for that error message.
On the other Stationary zone problem, will you open a new issue for this. I have some questions and it is easier for me to keep track of problems on the issues page rather than here.

Thanks! I have created https://github.com/gcobb321/icloud3_v3/issues/55 please let me know how I can help debug

I'll hop in and test as well

Hi Gary I would also love to test v3.

I am trying v3 as of today.
I apologize if this is covered somewhere, (I didn't see any mention) but I discovered that this can't work with security keys enabled on your appleID, because you don't get a verification code with security keys enabled so you can't proceed to the configuration.  I was able to remove the security keys, and get the verification code as a workaround.

I must admit, that I‘m quite new to HA but wanted to try icloud3.
Tried the official icloud integration first but wanted to switch over to icloud3 because of the annoying emails sent whenever HA tried to access my icloud account.
But with icloud3 I suffered the same issues.
In addition to the emails I get notifications on my iPhone with a MFA key. But were do I have to isert that key?

@ChrisBuHa I think you'll get all the info you need regarding the steps on this page in the new documentation area.  https://gcobb321.github.io/icloud3_v3_docs/#/chapters/2.0-installing-and-configuring
Hopefully you can follow this sequence after you get the integration installed which you'll find the steps to in the link above...

I'll be testing as well.

jodfie will be testing

Just installed it!

Been a user of iCloud3 for a couple of years - I've recently found that I've been having to restart it regularly, so came to log an issue only to see there's a v3 beta. Have just installed it and excited to see how it develops.
Thanks for continuing to support this!

I'm trying out v3 beta as well, commenting for notifications as requested. It's working good for me too. Thank you gcob321!
The person badges I use on my dashboard often show the iCloud3 "stationary" zone names instead of my own map zone names or away. I hope I can figure that out (maybe passive zones for iCloud3?). Doesn't look like I can change that, with the HA gui at least. I did see a feature request for this but can't seem to find it now to check that it's for v3. Plus I haven't read all the documentation yet so maybe it's already been addressed. Still searching.

The Person uses the latitude/longitude attributes of the dev_trkr entity to see what zone they are in. Ic3 should not put a device in a stationary zone when an HA zone exists for the location. Look at the zone that was selected in he Event Log when the tracking results were determined for the device at the time the Stationary zone was created

andrzejf1994 – I will be testing.
I can also make a translation into polish.

@freekode singing up for the tests

@andrzejf1994 Thanks for the offer to translate the Configuration Wizard file. See here for an issue about this.

I'm testing v3 right now! :)

I will start to test today.

I am testing V3 since a week or 2.

testing v3 for about a week; it works great so far!

Just found the v3 beta. I'm going to switch over this weekend. I was actually a little concerned that this project was being abandoned while looking at the v2 repo. Maybe it may make sense to add a note indicating that v3 is being developed and point to this repo? Though I can understand why you may not want new people installing this version yet.

I'll do that when it is out of beta. I hope to have beta17 up this weekend. There are a few issues with reauthenticating the iCloud account. It works but you have to restart HA to get around the problem with b16


Missing documentation for failover configuration.

In 1, there is no documentation about the following configuration variables (there are comments in the code in 2):

MasterFailoverDetachSlaveMasterHost
MasterFailoverLostInstancesDowntimeMinutes
PostponeSlaveRecoveryOnLagMinutes

Note that the options above are in sample conf file 3.
I will submit a PR once a question related to MasterFailoverDetachSlaveMasterHost is answered in a private Slack.

Corresponding PR: https://github.com/github/orchestrator/pull/1043

closed by #1043


Fix SelectField rendering in SSR env

Closes #107

Late to the party! Good job on this one!
I'm thinking whether there is some method to automatically test on a unit-test level that components can be server-rendered. If you guys are aware of something like that, please share it with me :) Otherwise I'll try to figure it out in my free time.

@jvorcak I have the same thought. Will create a task for it.


Structuring and De-Structuring Bundles

Structuring and De-Structuring Connections
The "structured connection" type (name-debate in #4, referred to as "bundle" here) is one of Hdl21 and similar libraries' primary productivity-improvement mechanisms for connecting Modules to one another.
For example from the Hdl21 unit tests:
    @h.bundle
    class Jtag:
        roles = HostDevice
        tck, tdi, tms = h.Signals(3, src=roles.HOST, dest=roles.DEVICE)
        tdo = h.Signal(src=roles.DEVICE, dest=roles.HOST)

    @h.bundle
    class Spi:
        roles = HostDevice
        sck, cs = h.Signals(2, src=roles.HOST, dest=roles.DEVICE)
        dq = h.Signal(src=roles.DEVICE, dest=roles.HOST, width=4)

    @h.module
    class Chip:
        spi = Spi(role=HostDevice.HOST, port=True)
        jtag = Jtag(role=HostDevice.DEVICE, port=True)
        ...  # much more internal content

Here Chip.spi and Chip.jtag are bundle-valued Ports, each of which has several underlying (scalar) Signals. Each set of signals commonly travels together, and the bundle-type allows passing them around as a single entity rather than via each of their constituent elements.
Here
This issue is about creating ("structuring") and breaking up ("destructuring") these connection-objects. This will need to happen at both the top and bottom of Hdl21 hierarchies, for a few common reasons:

At hierarchy-bottom, Modules will eventually need to connect to Primitive elements, which do not include bundle-valued ports. Similarly many ExternalModules created in and instantiated from legacy tools will not include such a concept, and must be resolved to scalar ports.
At hierarchy-top, exposing an IO interface to said legacy tools (with fully designer-controlled names), while using bundles internally, will require constructing bundles from scalar signals.
In other cases, different bundles will require "re-wiring" between each other. These may be due to different signal-naming conventions, or to express boundary-changes in functionality (e.g. wiring each tx and rx in a symmetric communications link).

Destructuring
The former is (I think) the easier of the two cases. A dot-access into a Bundle produces a reference to its constituent Signals and/or sub-Bundles. These can then be connected to other instances, like so:
@h.bundle
class WholeBoardIo:
  spi = Spi()
  jtag = Jtag()

@h.module
class Board:
  io = WholeBoardIo(port=True)

  # Connect to a thing called `SpiFlash`, which only uses the `spi` part of `WholeBoardIo`
  flash = SpiFlash(spi=io.spi)
  # ...

This feature has been supported in Hdl21 essentially since the introduction of the structured-connection (Interface / Bundle) type.
Structuring
How to create bundles from scalar signals is a more interesting policy decision. Considering this case:
@h.bundle
class Diff:
  p = h.Signal()
  n = h.Signal()

@h.module
class Child:
  dport = Diff(port=True)

@h.module
class Parent:
  p, n = h.Ports(2)
  child = Child() # ... now what?

Module Parent exposes scalar-valued ports, and instantiates module child with one (or more) bundle-valued ports. (Similar to bullet 2, "top of hierarchy", in section "Here".)
There are a few policies I can imagine:

Connect a signal at a time
Create (something) "bundle-valued"
Connections into Bundle instances
All of the above

Connecting a Signal at a Time
The "signal at a time" concept would use nested left-hand-side dot-accesses to dictate instance connections. In the case of Parent and Child above, this would look like so:
# In `Parent` class-body
child = Child()
child.dport.p = p
child.dport.n = n
# ...

This is very similar to the typical semantics of Chisel connections.
This looks pretty good for the relatively simple case above. Noting however that bundles can be nested, as can bundle-valued ports. So larger cases would look more like:
# A more complicated port-type
child.bundle_port.sub_bundle1.sub_sub_bundle.some_signal = p

This would then require a "connection rules" policy similar to that discussed in #3. For example, imagine embedding the snippet above in a procedural set of connections, including something like so:
# Several connections to this `child.bundle_port`
child.bundle_port.sub_bundle1   = some_bundle
child.bundle_port.sub_bundle2   = some_other_bundle
child.bundle_port.sub_bundle3   = bundle3      #(1)
child.bundle_port.sub_bundle3.p = some_signal  #(2) Hm, now what?

Here p is assigned both by commented lines (1) and (2). Our resolution (thus far) to #3 has been "disallow this altogether", i.e. by not enabling the nested LHS assignment-connections.
Create Something Bundle-Valued
The primary alternative is for "instantiators" to create a structured bundle-like object to connect to each bundle-valued port. In the (more elaborate) case above in which child has a port named bundle_port, this would look something like:
child.bundle_port = Something( # Creating the `Something`-bundle-like object
  sub_bundle1 = some_other_bundle,
  sub_bundle3 = Something ( # Nesting another `Something`
    p = some_signal,
    # everything else comes from `bundle3`
  )
)

The generally anonymous Something here is very much like Bundle, but has an anomyous bundle-type. These are essentially BundleInstances of anonymous types created at instantiation time. Instances then have a single connection per-port, including for bundle-valued ports.
Connections into Bundle Instances
SystemVerilog's interface instead exposes select signals as externally-connectable ports, while maintaining other signals as internal and private. Its interfaces are more like "modules without instances" in this sense. An example from https://www.doulos.com/knowhow/systemverilog/systemverilog-tutorials/systemverilog-interfaces-tutorial/:
interface ClockedBus (input Clk);
  logic[7:0] Addr, Data;
  logic RWn;
endinterface

module RAM (ClockedBus Bus);
  always @(posedge Bus.Clk)
    if (Bus.RWn)
      Bus.Data = mem[Bus.Addr];
    else
      mem[Bus.Addr] = Bus.Data;
endmodule

// Using the interface
module Top;
  reg Clock;

  // Instance the interface with an input, using named connection
  ClockedBus TheBus (.Clk(Clock));
  RAM TheRAM (.Bus(TheBus));
  ...
endmodule

Here ClockedBus has an external input-signal Clk and several other internal, private signals. The top instance of ClockedBus in module Top gets (requires?) an external signal tied to Clk. The ClockedBus-valued port Bus of module RAM in contrast does not take such an external connection.
While admitting I don't know these connection-rules completely, I don't love this method.
Status
Commits as of https://github.com/dan-fritchman/Hdl21/commit/af2c3ce92799f4db04b9872c17a10940dd0d06dc (as of this writing, head of dev) include the "Something" bundle-valued concept, in which this type is named AnonymousBundle. It does not include nested LHS assignments, nor SystemVerilog-style connections into BundleInstances.
I do not believe AnonymousBundle should be the final name. But also don't have a better one immediately at hand. "Bundle" in contrast is used for the bundle-type definitions.
This AnonymousBundle implementation does not support connect-by-assignment, or replacement of connections by assigment. All connections are made at creation-time. This avoids needing support for a "nested connection" policy as outlined here and in #3, while perhaps making some implementations more cumbersome.

Proposal from 11/4 meeting -

Stick with "instantiators create something bundle-valued"
Rename some stuff

Bundle (class-style definition) -> BundleDef / BundleClass
AnonymousBundle -> Bundle

Include dict conversion for the (previously Anonymous) bundle-connections

+1 for the AnonymousBundle -> Bundle and Bundle -> BundleClass

Updated plan here:

The type names Bundle and AnonymousBundle stay the same.
The decorator function bundle stays the same.

The bundle decorator behavior gets the same changes described in #38.

We add a bundlize function which takes an arbitrary pile of signals and bundle instances, and returns an AnonymousBundle.

This largely makes AnonymousBundle an internal type; no one should need to directly instantiate it.

This will be in #53.


Style up the slide view.

Description:
Recently, we introduced a markdown editor and slide view. However, the style of the slide view is still crude.
For example, the text of the code is not displayed properly.

Let's style up the slide view.
Why:

Users can use prettier slide view.

@nyanji00 This is an issue we discussed in our last meeting.

@hackerwins I am interested in this issue! Could you assign this issue to me? 👀


Adding technologies to be used for Mobile

Updating technologies to be used page by adding technologies under Mobile team.

Updated page


Update README to reflect new options

I kind of monkey-ed the PR by not rebasing my fork, but the diff still looks mostly fine. Let me know what you think @beauwilliams.

Perfect! Thank you very much. I have merged this in and fixed up the formatting for consistency :)


Does configure add value?

Currently, to use the Makefile in the root of the project, you first have to run ./configure which looks for certain applications and checks they are present on your machine. It then dumps a .env with the correct paths to these applications.
I'm not convinced this adds much value to the Makefile and would rather substitute a Makefile with some preflight checks instead, ie, bail from the make target if you are missing go for instance (with a nice message).
WDYT @steakunderscore @syscll?

This sounds good to me. The ./configure file never seems to work as expected for me, so I'd agree that it would be nice to remove an additional bash script.


don't SMB unless bg > threshold

https://github.com/openaps/oref0/blob/smb-lgs/lib/determine-basal/determine-basal.js#L564-L568 skips low glucose suspend if IOB is already super negative and BG is rising faster than predicted.  However, while it's useful to be able to avoid extended zero temping in that situation, it's best to avoid SMBs until BG has risen above the LGS threshold.

working great so far for a full 24 hours. I like this new logic for SMB ...
 // min_bg of 90 -> threshold of 65, 100 -> 70 110 -> 75, and 130 -> 85     var threshold = min_bg - 0.5*(min_bg-40);


Remove MystiPanda.ClashVerge 1.6.2 to ClashVergeRev.ClashVergeRev 1.6.2

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
Related https://github.com/clash-verge-rev/clash-verge-rev/pull/1326#discussion_r1665558798

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

URL: https://github.com/clash-verge-rev/clash-verge-rev/releases/download/v1.6.2/Clash.Verge_1.6.2_x64-setup.exe
Status Code: 200
(Automated message - build 886)

https://github.com/microsoft/winget-pkgs/issues/142854


fix: Added dev.vars into dotEnv file

Closes #1338
✅ Checklist

[x] I have followed every step in the contributing guide
[x] The PR title follows the convention.
[x] I ran and tested the code works

Testing
[Describe the steps you took to test this change]

Changelog
[Short description of what has changed]

Screenshots
[Screenshots]
💯

Summary by CodeRabbit

New Features

Expanded configuration capabilities by adding support for a new environment variable file, "dev.vars".

This enhancement allows for greater flexibility in managing application settings.

Looks good! Could you add a patch changeset?

Looks good! Could you add a patch changeset?

I have pushed the changes. I am unsure if I am correct as I have never done this before.


Download Issue

I tried this url: http://www.youtube.com/watch?v=9u7hGkL57N8
but i doesn't show any informations..
and your exceptions response was 'Could not get video page content'

and also, how can i download the file without saving it in my server?.. just download it.. right away once the user get the information details?

Hello.
Please download latest version and if after that the problem persists, it maybe because VEVO is not available in all countries. try it with a VPN or proxy. I could download it btw.
if you want to just get the link, you should just call getInfo method with true as it's first parameter. Then it will give you all information about the video including download links:
<?php
include 'vendor/autoload.php';
use \Masih\YoutubeDownloader\YoutubeDownloader;

$youtube = new YoutubeDownloader('9u7hGkL57N8');
$info = $youtube->getInfo(true);
print_r($info);


luci-app-advanced-reboot: add linksys-mr8300 support

Signed-off-by: Hans Geiblinger<EMAIL_ADDRESS>Tested and confirmed working against master branch and mr8300

Hello Hans,
Thank you for this! Will be you able to squash two commits into one for this PR?

Hello Hans,
Thank you for this! Will be you able to squash two commits into one for this PR?

I will work on it this evening. I am not the most proficient in git, so will have to figure out how to do that. I was hoping that by putting both changes in the same PR, it would have cleaned it up.

will have to figure out how to do that

Read the advice...
https://github.com/openwrt/luci/blob/master/CONTRIBUTING.md#advice-on-pull-requests
Read the section "If you need to change something in the existing pull request "
(hmmm, you have disregarded the basic advice to use a separate branch for each new PR. You have used master. :-(
But if you have not updated your local repo yet, it should be just

"git rebase -i HEAD~2", squashing action by hand
then "git  push -f" to update PR

will have to figure out how to do that

Read the advice...
https://github.com/openwrt/luci/blob/master/CONTRIBUTING.md#advice-on-pull-requests
Read the section "If you need to change something in the existing pull request "
(hmmm, you have disregarded the basic advice to use a separate branch for each new PR. You have used master. :-(
But if you have not updated your local repo yet, it should be just

"git rebase -i HEAD~2", squashing action by hand
then "git  push -f" to update PR

Thanks Hannu, I am learning as I go. Pretty good at making local mods, but am not a coder my profession, so much of the process flow is new to me (git, proper basing, rebasing, squashing etc...). Thanks for the advice, I will try just that later this afternoon. If it works, it will really help me when posting the official PR for the MR8300 device as there are multiple commits I made on that one.

@hnyman  I did exactly as you described. When I issued the rebase command, it did bring up vi and had the two commits I made in there, I saved and exited and tried to push, says all is up to date:

You need to edit the rebase commit list and "squash" one of them.

You need to edit the file in git editor...
first commit is "pick"
second commit need to be "squash"
example
http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html

There is a famous saying about teaching someone to fish.... :-) Thanks Hannu, it should be good now.

However, I see that my commit message is a bit sloppy now. Would it not be cleaner for me to close this PR, fork a new copy, create a branch, make my commits, squash them, then resubmit?

You can also edit that commit message when you do the rebase squash..
But now when you only have one commit, you can just use "git commit --amend" and edit the message, and then again "git push -f"

You can also edit that commit message when you do the rebase squash..
But now when you only have one commit, you can just use "git commit --amend" and edit the message, and then again "git push -f"

Thanks a bunch, much better now. Next commit will be much cleaner, thank you for the lessons learned.

Thank you, gentlemen, for a clean commit!


BUG : Opening [order] help crashes PD

Hi.
opening [order] help crashes and quits pd (vanilla 0.48.1 Win64)

hi, what's your exact version of else? please

Hi @porres !
I'm running 1.0beta8

I don't have any issues in macOS.
well, [order] is a vanilla abstraction, and it does work for you, right?
the help file also creates other objects from else that depend on [order], they are:
[else/resonbank~], [else/resonbank2~], [else/oscbank~],  [else/bpbank~]. The only thing I can think of is that these loading this objects may crash Pd for you. Can you try them?

@porres The culprit is oscbank~. As soon as i instantiate it PD quits.

btw [order] works fine.

just to confirm, do the other "bank" objects work fine?

this is what i have if i instantiate [oscbank2~]
tried C:/Users/fremen/Documents/Pd/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/oscbank2~/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/oscbank2~/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/oscbank2~.pat and failed
tried C:/Users/fremen/Documents/Pd/oscbank2~/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~.pat and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~.pat and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/oscbank2~/oscbank2~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/oscbank2~/oscbank2~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/oscbank2~.pd and succeeded
tried C:/Users/fremen/Documents/Pd/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/cyclone/oscbank2~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/oscbank2~.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/order/order.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/order/order.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pat and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/order/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order/order.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order/order.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/break.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/break.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/break/break.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/break/break.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/break.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/break.pat and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/break/else/break.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/break.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/break.dll and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/else/order.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/order.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/./oscclone2.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./oscclone2.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./oscclone2/oscclone2.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./oscclone2/oscclone2.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./oscclone2.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/./oscclone2.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/./else/sine~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/sine~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/sine~/sine~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/sine~/sine~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/sine~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/sine~.pat and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/sine~/else/sine~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/sine~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/sine~.dll and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~/float2sig~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~/float2sig~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~.pat and failed
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~/else/float2sig~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~/float2sig~.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~/float2sig~.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/loadbanger.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/loadbanger.dll and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~.pd and succeeded
tried C:/Users/fremen/Documents/Pd/externals/else/./else/float2sig~.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/float2sig~.pd and succeeded
can't resize to zero or negative number; setting to 1
... you might be able to track this down from the Find menu.
tried C:/Users/fremen/Documents/Pd/externals/else/else/args.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/args.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/args/args.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/args/args.dll and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/args.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/args.pat and failed
tried C:/Users/fremen/Documents/Pd/externals/else/else/args/else/args.pd and failed
tried C:/Users/fremen/Documents/Pd/externals/else/args.m_i386 and failed
tried C:/Users/fremen/Documents/Pd/externals/else/args.dll and succeeded

If i try to open [oscbank2~] help PD just quits

All the various filter banks [else/resonbank~], [else/resonbank2~],[else/bpbank~] work just fine.

@porres Deleted the whole else folder and reinstalled...same crashes with [oscbank~].
As before [oscbank2~] instantiate correctly andi can correctly open the abstraction. But if i try to open the help i have a crash and pd quits as when i instantiate [oscbank~]. Porbably in the help file of [oscbank2~] there's an instance of [oscbank~].

in the help file of [oscbank2~] there's an instance of [oscbank~].

yup.
Well, I just uploaded a fix for [oscbank~] for a bug I found that might be related or not, it's worth to have a try: https://github.com/porres/pd-else/blob/7763c0ddb4a48a1a8eac2b373b4feae2c251767d/help/Abstractions/oscbank~.pd
Other than that, the [oscbank~] is the only object in else that uses the newly added [inlet2~] object, maybe you're having a problem with it. Try and see if you can instantiate it, or try to  open its help file (from the else folder).

@porres I guess you found it! I can't instantiate inlet2~ and pd suddenly quits.

bug referred in https://github.com/porres/pd-else/issues/203


hdiutil: resize: failed. Resource temporarily unavailable

Tried to make (yarn make:macos) even though the yarn install didn't work, but:
yarn run v1.22.19
$ electron-builder --mac --universal
  • electron-builder  version=22.14.13 os=21.5.0
  • loaded configuration  file=package.json ("build" field)
  • writing effective config  file=dist/builder-effective-config.yaml
  • packaging       platform=darwin arch=x64 electron=17.1.2 appOutDir=dist/mac-universal--x64
  • packaging       platform=darwin arch=arm64 electron=17.1.2 appOutDir=dist/mac-universal--arm64
  • packaging       platform=darwin arch=universal electron=17.1.2 appOutDir=dist/mac-universal
  • skipped macOS application code signing  reason=Identity name is specified, but no valid identity with this name in the keychain identity=Emmanouil Konstantinidis (3YP8SXP3BF) allIdentities=     0 identities found
                                                Valid identities only
     0 valid identities found
  • notarizing      either should not notarize or not building for macOS
  • building        target=macOS zip arch=universal file=dist/Gitify-4.3.2-universal-mac.zip
  • building        target=DMG arch=universal file=dist/Gitify-4.3.2-universal.dmg
  • Detected arm64 process, HFS+ is unavailable. Creating dmg with APFS - supports Mac OSX 10.12+
  • building block map  blockMapFile=dist/Gitify-4.3.2-universal-mac.zip.blockmap
  ⨯ Exit code: 35. Command failed: hdiutil resize -size 639839119.7 /private/var/folders/00/dd4ntv795rx101d_l6wnvdyc0000gn/T/t-fRtIO1/0.dmg
hdiutil: resize: failed. Resource temporarily unavailable (35)

hdiutil: resize: failed. Resource temporarily unavailable (35)
  failedTask=build stackTrace=Error: Exit code: 35. Command failed: hdiutil resize -size 639839119.7 /private/var/folders/00/dd4ntv795rx101d_l6wnvdyc0000gn/T/t-fRtIO1/0.dmg
hdiutil: resize: failed. Resource temporarily unavailable (35)

hdiutil: resize: failed. Resource temporarily unavailable (35)

    at /Users/bmulholland/sources/gitify/node_modules/builder-util/src/util.ts:133:18
    at ChildProcess.exithandler (node:child_process:397:5)
    at ChildProcess.emit (node:events:537:28)
    at maybeClose (node:internal/child_process:1091:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:537:28)
    at Pipe.<anonymous> (node:net:747:14)
error Command failed with exit code 1.

Looks like this one is resolved (or at least changed) by updating menubar

could you try again with the latest changes on the main branch?

I'm blocked by https://github.com/Araxeus/gitify/issues/3 so I can't confirm if this one is fixed yet

I tried upgrading /all/ packages at once and repro'd this. Don't get it on latest custom_release though

Working on custom_release

so everything works well finally? 😄

Looks like it 🎉