https://preview.redd.it/b1wcu1pmxp1d1.jpg?width=1200&format=pjpg&auto=webp&s=a1adeed597b6d88347e8606da572f4993a3611db
Unlike HFS+, the modern Apple APFS file system—used in macOS 10.13 High Sierra and later—supports disc encryption by default. It can therefore protect critical user data at the file system level without providing the extra abstraction that Core Storage does. Its state-of-the-art security features notwithstanding, the technology is unable to guarantee against data loss. A power outage or human mistake are two of the many possible causes. Fortunately, files erased from an encrypted APFS volume on an internal or external drive can be recovered with the correct password or recovery key. After that, it can be restored to any secure location, barring catastrophic damage that has destroyed the disk's component parts that contain the metadata and encryption key file, among other things, that are necessary to decrypt the data. To decrypt your Apple storage and recover the encrypted data in BLR BitLocker Data Recovery, RAID, or Network RAID editions, simply follow the instructions that are provided. See the second instruction if you plan to use BLR Professional Data Recovery.

Regarding the Standard, RAID, or Network RAID editions of BLR Tools

1. Connect your Apple APFS-locked device to the PC.
Attach the portable hard drive encrypted to your Mac. If it's internal storage, you'll need to take it out of the computer and use it as a secondary drive on another computer, or you can use the BLR BitLocker Recovery tool for the recovery to start your Mac in a secure environment. It is also possible to work on the same Mac, but in order to do so, System Integrity Protection must be disabled, as detailed in Unblocking access to macOS drives. However, the latter choice is not recommended because there is a high likelihood of overwriting the data. Moreover, as the linked article goes on to explain, data cannot be recovered from the system drives of Mac models that depend on Apple's M1 (Apple Silicon) or T2 security chips.
2. Run BLR BitLocker Data Recovery Tool Standard Recovery after installation.
Enter the correct username and password to open the software with elevated privileges. In the left pane, the programme will list every drive that is connected. Each physical device's logical volumes will appear beneath it.
3. Locate the necessary encrypted APFS volume from the list that appears.
Check if an APFS partition—designated by a yellow padlock icon—is present in the list.
4. To access the application's content, decrypt the storage.
Even if the file system is marked as accessible, until it is decoded, no valid data can be obtained from it. To do this, select the "Decrypt encrypted APFS volume" option from the volume's context menu by opening it. Enter the correct user password in the dialogue that appears, or copy and paste the recovery key into the appropriate field.
5. In order to recover lost or deleted files, perform a scan on the decrypted volume.
The volume will unlock and its contents will be available within the programme following a successful decryption. You can also use the storage to scan for lost or deleted files. Select only APFS from the list of file systems when using the "Scan this storage" tool from the toolbar, then click the "Start scan" button.
6. Once the required recovered elements have been verified, save them to a different location.
Once the scanning process is complete, use the application's reconstruction of the file system to locate the necessary folders and files. Next, select "Define selection", check the boxes that correspond to them, and click "Save selection." Next, designate a secure location for the copy to be stored.

Regarding BLR Tools

1. Link the computer to the encrypted Apple APFS device.

Connect the external drive that is encrypted to the Mac. You can either use the BLR Data recovery software to boot your Mac in a safe environment or extract the system disc from the machine and attach it to another computer as secondary storage if you need to work with it. If you disable System Integrity Protection as outlined in Unblocking access to macOS drives, you can still work on the same Mac, but it is not advised due to the high risk of data overwriting. Furthermore, on Mac models that use Apple's M1 (Apple Silicon) or T2 security chips, data recovery from internal drives is not possible. For further details, please see the provided article.

1. Run BLR BitLocker Data Recovery after installing it.

Once the correct user and password have been entered in the pop-up window, launch the programme with administrative privileges. In the left pane's list of connected storage devices, the application will show all of the attached drives. Logical volumes will be arranged beneath each physical device.
3. Select the required encrypted APFS volume from the storage list.
Search the list for the required encrypted APFS partition, which will be indicated by a yellow padlock icon.
4. To open the data, use the decryption tool that the software has provided.
The partition is marked as accessible, but until it is decoded, the data inside cannot be read. Select the "Decrypt encrypted storage" option from the volume context menu, then opt for the "APFS volume decryption" technique. Enter the recovery key, complete with dashes, or enter the correct user password in the designated field.
5. Look through the decrypted storage to recover lost or deleted files.
The available files will be viewable in the software interface once decryption is finished. By scanning the storage, you can also locate the ones that were lost or erased. Select the appropriate tool from the toolbar, deselect all other file systems, save APFS, and then click "Start scan" to begin the scan.
6. After selecting the necessary recovered items, copy them to a different disc.
Once the process is complete, you can locate the necessary folders and files by browsing the file system that the programme has restored. Click "Define selection", check the ones you want to save, then click "Save selection." Next, decide which safe destination folder to put the saved items in.

i’ve done the manual method and the automatic whitelist option. HAS ONLY STARTED YESTERDAY SINCE I ENABLED BANDWITH SHARING.
what should i try next ?
thanks in advance

So I have had this ongoing issue for quite a long time where occasionally i will end up with duplicate movies...the commonality that I've noticed is that the movies have a colon in them and i will end up with a duplication ( I believe this happens with TV shows too, but not as often).
I have looked at both Radarr and TMM and chased in both directions and to be honest i can't be totally sure which is the causation of the duplication, but I've found an error in the logs that suggest that TMM may be running into an issue that doesn't allow the renaming process to complete when it finds a duplicate movie (or at least that's the latest theory I'm going with) I've chased this with Radarr support and they can't quite pinpoint it from their side either.
This issue seems to be with exclusively the folder, not the movie file...all the files and artwork look fine...just the folder.
Example: Movie R.I.P.D. 2: Rise of the Damned (2022)
Configured in Radarr to replace with [space]-[space] If a colon is found.
Configured in TMM to replace colons with \"-\"
they seem to be configured in a way that would produce the same result....the example file path looks ok in TMM
However, at a later point in time ( always when I'm not watching...I've watched these processes from end-to-end and they work just fine...seems to be when my automation is doing it, that i get these results). I will get movie duplication that has the movie with the dash with no space...I feel that this is the causation of when a movie gets upgraded or replaced.
https://preview.redd.it/mraxkidkeo1d1.png?width=517&format=png&auto=webp&s=80fabe7f350231f88e59fb2b4a85b777cc9568e1
I looked in the TMM logs and i see these messages "\Movies\Movies 4\R.I.P.D. 2- Rise of the Damned (2022)\.actors\Richard_Brake.jpg"
This indicates to me that the folder exists as "R.I.P.D. 2-" after a scan has completed and files are being moved...
Then finally i see this error message in the logs that says
2024-05-20 01:58:59,926 INFO [tmmpool-rename-T1] o.t.core.movie.MovieRenamer:261 - Renaming movie: R.I.P.D. 2: Rise of the Damned
2024-05-20 01:58:59,933 ERROR [tmmpool-rename-T1] o.t.core.movie.MovieRenamer:652 - error moving folder:
org.apache.commons.io.FileExistsException: Destination 'Movies\Movies 4\R.I.P.D. 2 - Rise of the Damned (2022)' already exists

at org.tinymediamanager.core.Utils.moveDirectorySafe(Utils.java:687) at org.tinymediamanager.core.movie.MovieRenamer.renameMovieFolder(MovieRenamer.java:643) at org.tinymediamanager.core.movie.MovieRenamer.renameMovie(MovieRenamer.java:278) at org.tinymediamanager.core.movie.tasks.MovieRenameTask$RenameMovieTask.call(MovieRenameTask.java:108) at org.tinymediamanager.core.movie.tasks.MovieRenameTask$RenameMovieTask.call(MovieRenameTask.java:99) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) 

So i guess because it's already been properly named once that it is not able to do it again? I'm really at a loss on how to solve scenarios like this. I have looked at Radarr Trace logs and an error message does not exist for this movie. I would almost consider this a bug or a missed setting...but i would need to know what setting to adjust to navigate this. Please help.

I used REST API to pull status from FX3100 gateway and incorporate it within Home Assistant.
https://preview.redd.it/a1oj7nbc8o1d1.png?width=1592&format=png&auto=webp&s=bc17226ec9a787ab967142f8b4df0e44af3f0588
But seems the gateway does not provide values for RSRP and RSRQ.
below is fx3100.yaml file for home assistant:

# ============================================================================== # This is yaml file that goes into Packages folder # u/file packages/fx3100.yaml # # IMPORTANT: Enable packages in `configuration.yaml` # see https://www.home-assistant.io/docs/configuration/packages/ # # note: set `initial` in the `input_text` section below to the IP address of your FX3100. # ============================================================================== # ============================================== # Input Text # ============================================== input_text: fx3100_host: name: FX3100 host icon: mdi:server initial: # ============================================== # Input Number # ============================================== #input_number: # fx3100_data_cap: # name: FX3100 Data Cap # icon: mdi:swap-horizontal # initial: 150 # min: 0 # max: 1000 # step: 1 # mode: box # unit_of_measurement: GB # ============================================== # Sensor # ============================================== sensor: # ============================== # Usage Info # ============================== - platform: rest name: FX3100 Usage unique_id: fx3100_usage resource_template: "http://{{ states('input_text.fx3100_host') }}/apps_home/usageinfo/" value_template: "OK" json_attributes: - allowance - barPercentageRemaining - cycleEndDt - daysLeft - deviceServiceNumber - gBaseAssetsPath - gHelpURL - gHtmlLang - gIsAdminSettingsEnabled - gIsDefaultPassword - gIsDeviceAgent - gIsGpsSupported - gIsLoggedIn - gIsLongshipSupported - gIsMultiSimSupported - gIsPromptChangePassword - gIsSMSEnabled - gIsSMSLOCKED - gIsVPNSupported - gIsWanMgrSupported - gIsWiFiSupported - gLangDirection - gLocale - gPageId - gProductName - gProductNumber - gSecureToken - isHidden - isNonTelstra - isNotPrepaidService - isPostPaidTelstra - isPrePaidTelstra - lastResetDate - lineUsage - nextCycleDate - remainingUsage - rxUsage - totalShrUsage - txUsage - unit - usageInformationAvailable # ============================== # Status Info # ============================== - platform: rest name: FX3100 Status unique_id: fx3100_status resource_template: "http://{{ states('input_text.fx3100_host') }}/srv/status" value_template: "OK" json_attributes_path: "$.statusData" json_attributes: - StatusBarSoftwareUpdateCustomDesc - StatusBarSoftwareUpdateCustomDownloadMsg - StatusBarSoftwareUpdateCustomInstallFailMsg - StatusBarSoftwareUpdateCustomInstallSuccessMsg - StatusBarSoftwareUpdateCustomReadyToInstallMsg - StatusBarSoftwareUpdateInstallationDuration - StatusBarSoftwareUpdateMdipSupported - StatusBarSoftwareUpdatePackageDescription - StatusBarSoftwareUpdateSize - StatusBarSoftwareUpdateSourceVersion - StatusBarSoftwareUpdateStatus - StatusBarSoftwareUpdateTargetVersion - StatusBarSoftwareUpdateUserInitiated - StatusBarSoftwareUpdateValue - StatusBarSoftwareUpdateVersion - ethWanInterface - internetStatusGateway - internetStatusIPAddress - internetStatusIPv6Address - internetStatusIPv6LinkLocalAddress - internetStatusSubnetMask - isDualSimSupported - simWanInterface - statusBarActiveSimSlot - statusBarAirplaneMode - statusBarBand - statusBarBandwidth - statusBarBytesReceived - statusBarBytesTotal - statusBarBytesTransmitted - statusBarClientListSize - statusBarConnectionDuration - statusBarConnectionState - statusBarEthernetInterfaceType - statusBarEthernetInterfaceType1 - statusBarEthernetPortEnabled - statusBarEthernetPortEnabled1 - statusBarEthernetSupported - statusBarEthernetToggleEnabled - statusBarFemtoCellStatus - statusBarFotaInstallStatus - statusBarGpsStatus - statusBarGuestClientListSize - statusBarGuestWifiEnabled - statusBarMaxClientListSize - statusBarMaxWiFiClientListSize - statusBarMnsAvailable - statusBarMnsInUse - statusBarMnsScan - statusBarMobileDataEnabled - statusBarNetwork - statusBarNetworkID - statusBarNotificationFlag - statusBarNumSims - statusBarPCI - statusBarPrimaryClientListSize - statusBarSNR - statusBarSignalBars - statusBarSim2ConnectionState - statusBarSim2Network - statusBarSim2SignalBars - statusBarSim2Status - statusBarSim2Technology - statusBarSim2TechnologyText - statusBarSimCarrierBlockedStatus - statusBarSimMMCode - statusBarSimSlotsCount - statusBarSimStatus - statusBarSmsUnreadCount - statusBarTechnology - statusBarTechnologyText - statusBarTrafficStatus - statusBarVpnConnectDisconnectButtonText - statusBarVpnConnectionState - statusBarWiFiClientListSize - statusBarWiFiEnabled - statusExtAntennaEnabled # ============================================== # Template, usage # ============================================== template: - sensor: - name: "FX3100 Allowance" unique_id: fx3100_allowance state: "{{ state_attr('sensor.fx3100_usage', 'allowance') }}" - name: "FX3100 Bar Percentage Remaining" unique_id: fx3100_bar_percentage_remaining state: "{{ state_attr('sensor.fx3100_usage', 'barPercentageRemaining') }}" - name: "FX3100 Cycle End Date" unique_id: fx3100_cycle_end_dt state: "{{ state_attr('sensor.fx3100_usage', 'cycleEndDt') }}" unit_of_measurement: "Days" - name: "FX3100 Days Left" unique_id: fx3100_days_left state: "{{ state_attr('sensor.fx3100_usage', 'daysLeft') }}" - name: "FX3100 Device Service Number" unique_id: fx3100_device_service_number state: "{{ state_attr('sensor.fx3100_usage', 'deviceServiceNumber') }}" - name: "FX3100 GBase Assets Path" unique_id: fx3100_gbase_assets_path state: "{{ state_attr('sensor.fx3100_usage', 'gBaseAssetsPath') }}" - name: "FX3100 GHelp URL" unique_id: fx3100_ghelp_url state: "{{ state_attr('sensor.fx3100_usage', 'gHelpURL') }}" - name: "FX3100 GHtml Lang" unique_id: fx3100_ghtml_lang state: "{{ state_attr('sensor.fx3100_usage', 'gHtmlLang') }}" - name: "FX3100 Is Admin Settings Enabled" unique_id: fx3100_is_admin_settings_enabled state: "{{ state_attr('sensor.fx3100_usage', 'gIsAdminSettingsEnabled') }}" - name: "FX3100 Is Default Password" unique_id: fx3100_is_default_password state: "{{ state_attr('sensor.fx3100_usage', 'gIsDefaultPassword') }}" - name: "FX3100 Is Device Agent" unique_id: fx3100_is_device_agent state: "{{ state_attr('sensor.fx3100_usage', 'gIsDeviceAgent') }}" - name: "FX3100 Is GPS Supported" unique_id: fx3100_is_gps_supported state: "{{ state_attr('sensor.fx3100_usage', 'gIsGpsSupported') }}" - name: "FX3100 Is Logged In" unique_id: fx3100_is_logged_in state: "{{ state_attr('sensor.fx3100_usage', 'gIsLoggedIn') }}" - name: "FX3100 Is Longship Supported" unique_id: fx3100_is_longship_supported state: "{{ state_attr('sensor.fx3100_usage', 'gIsLongshipSupported') }}" - name: "FX3100 Is MultiSim Supported" unique_id: fx3100_is_multisim_supported state: "{{ state_attr('sensor.fx3100_usage', 'gIsMultiSimSupported') }}" - name: "FX3100 Is Prompt Change Password" unique_id: fx3100_is_prompt_change_password state: "{{ state_attr('sensor.fx3100_usage', 'gIsPromptChangePassword') }}" - name: "FX3100 Is SMSEnabled" unique_id: fx3100_is_smsenabled state: "{{ state_attr('sensor.fx3100_usage', 'gIsSMSEnabled') }}" - name: "FX3100 Is SMS Locked" unique_id: fx3100_is_sms_locked state: "{{ state_attr('sensor.fx3100_usage', 'gIsSMSLOCKED') }}" - name: "FX3100 Is VPN Supported" unique_id: fx3100_is_vpn_supported state: "{{ state_attr('sensor.fx3100_usage', 'gIsVPNSupported') }}" - name: "FX3100 Is WanMgr Supported" unique_id: fx3100_is_wanmgr_supported state: "{{ state_attr('sensor.fx3100_usage', 'gIsWanMgrSupported') }}" - name: "FX3100 Is WiFi Supported" unique_id: fx3100_is_wifi_supported state: "{{ state_attr('sensor.fx3100_usage', 'gIsWiFiSupported') }}" - name: "FX3100 Lang Direction" unique_id: fx3100_lang_direction state: "{{ state_attr('sensor.fx3100_usage', 'gLangDirection') }}" - name: "FX3100 Locale" unique_id: fx3100_locale state: "{{ state_attr('sensor.fx3100_usage', 'gLocale') }}" - name: "FX3100 Page Id" unique_id: fx3100_page_id state: "{{ state_attr('sensor.fx3100_usage', 'gPageId') }}" - name: "FX3100 Product Name" unique_id: fx3100_product_name state: "{{ state_attr('sensor.fx3100_usage', 'gProductName') }}" - name: "FX3100 Product Number" unique_id: fx3100_product_number state: "{{ state_attr('sensor.fx3100_usage', 'gProductNumber') }}" - name: "FX3100 Secure Token" unique_id: fx3100_secure_token state: "{{ state_attr('sensor.fx3100_usage', 'gSecureToken') }}" - name: "FX3100 Hidden" unique_id: fx3100_hidden state: "{{ state_attr('sensor.fx3100_usage', 'isHidden') }}" - name: "FX3100 Non Telstra" unique_id: fx3100_non_telstra state: "{{ state_attr('sensor.fx3100_usage', 'isNonTelstra') }}" - name: "FX3100 Not Prepaid Service" unique_id: fx3100_not_prepaid_service state: "{{ state_attr('sensor.fx3100_usage', 'isNotPrepaidService') }}" - name: "FX3100 Post Paid Telstra" unique_id: fx3100_post_paid_telstra state: "{{ state_attr('sensor.fx3100_usage', 'isPostPaidTelstra') }}" - name: "FX3100 PrePaid Telstra" unique_id: fx3100_prepaid_telstra state: "{{ state_attr('sensor.fx3100_usage', 'isPrePaidTelstra') }}" - name: "FX3100 Last Reset Date" unique_id: fx3100_last_reset_date state: "{{ state_attr('sensor.fx3100_usage', 'lastResetDate') }}" - name: "FX3100 Line Usage" unique_id: fx3100_line_usage unit_of_measurement: "GB" state: "{{ state_attr('sensor.fx3100_usage', 'lineUsage') }}" - name: "FX3100 Next Cycle Date" unique_id: fx3100_next_cycle_date state: "{{ state_attr('sensor.fx3100_usage', 'nextCycleDate') }}" - name: "FX3100 Remaining Usage" unique_id: fx3100_remaining_usage unit_of_measurement: "GB" state: "{{ state_attr('sensor.fx3100_usage', 'remainingUsage') }}" - name: "FX3100 Rx Usage" unique_id: fx3100_rx_usage unit_of_measurement: "GB" state: "{{ state_attr('sensor.fx3100_usage', 'rxUsage') }}" - name: "FX3100 Total Shr Usage" unique_id: fx3100_total_shr_usage unit_of_measurement: "GB" state: "{{ state_attr('sensor.fx3100_usage', 'totalShrUsage') }}" - name: "FX3100 Tx Usage" unique_id: fx3100_tx_usage unit_of_measurement: "GB" state: "{{ state_attr('sensor.fx3100_usage', 'txUsage') }}" - name: "FX3100 Unit" unique_id: fx3100_unit state: "{{ state_attr('sensor.fx3100_usage', 'unit') }}" - name: "FX3100 Usage Information Available" unique_id: fx3100_usage_information_available state: "{{ state_attr('sensor.fx3100_usage', 'usageInformationAvailable') }}" # ============================================== # Template, status # ============================================== - name: "FX3100 Status Bar Software Update Custom Desc" unique_id: fx3100_status_bar_software_update_custom_desc state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateCustomDesc') }}" - name: "FX3100 Status Bar Software Update Custom Download Msg" unique_id: fx3100_status_bar_software_update_custom_download_msg state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateCustomDownloadMsg') }}" - name: "FX3100 Status Bar Software Update Custom Install Fail Msg" unique_id: fx3100_status_bar_software_update_custom_install_fail_msg state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateCustomInstallFailMsg') }}" - name: "FX3100 Status Bar Software Update Custom Install Success Msg" unique_id: fx3100_status_bar_software_update_custom_install_success_msg state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateCustomInstallSuccessMsg') }}" - name: "FX3100 Status Bar Software Update Custom Ready To Install Msg" unique_id: fx3100_status_bar_software_update_custom_ready_to_install_msg state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateCustomReadyToInstallMsg') }}" - name: "FX3100 Status Bar Software Update Installation Duration" unique_id: fx3100_status_bar_software_update_installation_duration state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateInstallationDuration') }}" - name: "FX3100 Status Bar Software Update Mdip Supported" unique_id: fx3100_status_bar_software_update_mdip_supported state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateMdipSupported') }}" - name: "FX3100 Status Bar Software Update Package Description" unique_id: fx3100_status_bar_software_update_package_description state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdatePackageDescription') }}" - name: "FX3100 Status Bar Software Update Size" unique_id: fx3100_status_bar_software_update_size state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateSize') }}" - name: "FX3100 Status Bar Software Update Source Version" unique_id: fx3100_status_bar_software_update_source_version state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateSourceVersion') }}" - name: "FX3100 Status Bar Software Update Status" unique_id: fx3100_status_bar_software_update_status state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateStatus') }}" - name: "FX3100 Status Bar Software Update Target Version" unique_id: fx3100_status_bar_software_update_target_version state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateTargetVersion') }}" - name: "FX3100 Status Bar Software Update User Initiated" unique_id: fx3100_status_bar_software_update_user_initiated state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateUserInitiated') }}" - name: "FX3100 Status Bar Software Update Value" unique_id: fx3100_status_bar_software_update_value state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateValue') }}" - name: "FX3100 Status Bar Software Update Version" unique_id: fx3100_status_bar_software_update_version state: "{{ state_attr('sensor.fx3100_status', 'StatusBarSoftwareUpdateVersion') }}" - name: "FX3100 Eth Wan Interface" unique_id: fx3100_eth_wan_interface state: "{{ state_attr('sensor.fx3100_status', 'ethWanInterface') }}" - name: "FX3100 Internet Status Gateway" unique_id: fx3100_internet_status_gateway state: "{{ state_attr('sensor.fx3100_status', 'internetStatusGateway') }}" - name: "FX3100 Internet Status IP Address" unique_id: fx3100_internet_status_ip_address state: "{{ state_attr('sensor.fx3100_status', 'internetStatusIPAddress') }}" - name: "FX3100 Internet Status IPv6 Address" unique_id: fx3100_internet_status_ipv6_address state: "{{ state_attr('sensor.fx3100_status', 'internetStatusIPv6Address') }}" - name: "FX3100 Internet Status IPv6 Link Local Address" unique_id: fx3100_internet_status_ipv6_link_local_address state: "{{ state_attr('sensor.fx3100_status', 'internetStatusIPv6LinkLocalAddress') }}" - name: "FX3100 Internet Status Subnet Mask" unique_id: fx3100_internet_status_subnet_mask state: "{{ state_attr('sensor.fx3100_status', 'internetStatusSubnetMask') }}" - name: "FX3100 Is Dual Sim Supported" unique_id: fx3100_is_dual_sim_supported state: "{{ state_attr('sensor.fx3100_status', 'isDualSimSupported') }}" - name: "FX3100 Sim Wan Interface" unique_id: fx3100_sim_wan_interface state: "{{ state_attr('sensor.fx3100_status', 'simWanInterface') }}" - name: "FX3100 Status Bar Active Sim Slot" unique_id: fx3100_status_bar_active_sim_slot state: "{{ state_attr('sensor.fx3100_status', 'statusBarActiveSimSlot') }}" - name: "FX3100 Status Bar Airplane Mode" unique_id: fx3100_status_bar_airplane_mode state: "{{ state_attr('sensor.fx3100_status', 'statusBarAirplaneMode') }}" - name: "FX3100 Status Bar Band" unique_id: fx3100_status_bar_band state: "{{ state_attr('sensor.fx3100_status', 'statusBarBand') }}" - name: "FX3100 Status Bar Bandwidth" unique_id: fx3100_status_bar_bandwidth state: "{{ state_attr('sensor.fx3100_status', 'statusBarBandwidth') }}" - name: "FX3100 Status Bar Bytes Received" unique_id: fx3100_status_bar_bytes_received state: "{{ state_attr('sensor.fx3100_status', 'statusBarBytesReceived') }}" - name: "FX3100 Status Bar Bytes Total" unique_id: fx3100_status_bar_bytes_total state: "{{ state_attr('sensor.fx3100_status', 'statusBarBytesTotal') }}" - name: "FX3100 Status Bar Bytes Transmitted" unique_id: fx3100_status_bar_bytes_transmitted state: "{{ state_attr('sensor.fx3100_status', 'statusBarBytesTransmitted') }}" - name: "FX3100 Status Bar Client List Size" unique_id: fx3100_status_bar_client_list_size state: "{{ state_attr('sensor.fx3100_status', 'statusBarClientListSize') }}" - name: "FX3100 Status Bar Connection Duration" unique_id: fx3100_status_bar_connection_duration state: "{{ state_attr('sensor.fx3100_status', 'statusBarConnectionDuration') }}" - name: "FX3100 Status Bar Connection State" unique_id: fx3100_status_bar_connection_state state: "{{ state_attr('sensor.fx3100_status', 'statusBarConnectionState') }}" - name: "FX3100 Status Bar Ethernet Interface Type" unique_id: fx3100_status_bar_ethernet_interface_type state: "{{ state_attr('sensor.fx3100_status', 'statusBarEthernetInterfaceType') }}" - name: "FX3100 Status Bar Ethernet Interface Type 1" unique_id: fx3100_status_bar_ethernet_interface_type1 state: "{{ state_attr('sensor.fx3100_status', 'statusBarEthernetInterfaceType1') }}" - name: "FX3100 Status Bar Ethernet Port Enabled" unique_id: fx3100_status_bar_ethernet_port_enabled state: "{{ state_attr('sensor.fx3100_status', 'statusBarEthernetPortEnabled') }}" - name: "FX3100 Status Bar Ethernet Port Enabled 1" unique_id: fx3100_status_bar_ethernet_port_enabled1 state: "{{ state_attr('sensor.fx3100_status', 'statusBarEthernetPortEnabled1') }}" - name: "FX3100 Status Bar Ethernet Supported" unique_id: fx3100_status_bar_ethernet_supported state: "{{ state_attr('sensor.fx3100_status', 'statusBarEthernetSupported') }}" - name: "FX3100 Status Bar Ethernet Toggle Enabled" unique_id: fx3100_status_bar_ethernet_toggle_enabled state: "{{ state_attr('sensor.fx3100_status', 'statusBarEthernetToggleEnabled') }}" - name: "FX3100 Status Bar Femto Cell Status" unique_id: fx3100_status_bar_femto_cell_status state: "{{ state_attr('sensor.fx3100_status', 'statusBarFemtoCellStatus') }}" - name: "FX3100 Fota Install Status" unique_id: fx3100_fota_install_status state: "{{ state_attr('sensor.fx3100_status', 'statusBarFotaInstallStatus') }}" - name: "FX3100 GPS Status" unique_id: fx3100_gps_status state: "{{ state_attr('sensor.fx3100_status', 'statusBarGpsStatus') }}" - name: "FX3100 Guest Client List Size" unique_id: fx3100_guest_client_list_size state: "{{ state_attr('sensor.fx3100_status', 'statusBarGuestClientListSize') }}" - name: "FX3100 Guest WiFi Enabled" unique_id: fx3100_guest_wifi_enabled state: "{{ state_attr('sensor.fx3100_status', 'statusBarGuestWifiEnabled') }}" - name: "FX3100 Max Client List Size" unique_id: fx3100_max_client_list_size state: "{{ state_attr('sensor.fx3100_status', 'statusBarMaxClientListSize') }}" - name: "FX3100 Max WiFi Client List Size" unique_id: fx3100_max_wifi_client_list_size state: "{{ state_attr('sensor.fx3100_status', 'statusBarMaxWiFiClientListSize') }}" - name: "FX3100 Mns Available" unique_id: fx3100_mns_available state: "{{ state_attr('sensor.fx3100_status', 'statusBarMnsAvailable') }}" - name: "FX3100 Mns In Use" unique_id: fx3100_mns_in_use state: "{{ state_attr('sensor.fx3100_status', 'statusBarMnsInUse') }}" - name: "FX3100 Mns Scan" unique_id: fx3100_mns_scan state: "{{ state_attr('sensor.fx3100_status', 'statusBarMnsScan') }}" - name: "FX3100 Mobile Data Enabled" unique_id: fx3100_mobile_data_enabled state: "{{ state_attr('sensor.fx3100_status', 'statusBarMobileDataEnabled') }}" - name: "FX3100 Network" unique_id: fx3100_network state: "{{ state_attr('sensor.fx3100_status', 'statusBarNetwork') }}" - name: "FX3100 Network ID" unique_id: fx3100_network_id state: "{{ state_attr('sensor.fx3100_status', 'statusBarNetworkID') }}" - name: "FX3100 Notification Flag" unique_id: fx3100_notification_flag state: "{{ state_attr('sensor.fx3100_status', 'statusBarNotificationFlag') }}" - name: "FX3100 Num Sims" unique_id: fx3100_num_sims state: "{{ state_attr('sensor.fx3100_status', 'statusBarNumSims') }}" - name: "FX3100 PCI" unique_id: fx3100_pci state: "{{ state_attr('sensor.fx3100_status', 'statusBarPCI') }}" - name: "FX3100 Primary Client List Size" unique_id: fx3100_primary_client_list_size state: "{{ state_attr('sensor.fx3100_status', 'statusBarPrimaryClientListSize') }}" - name: "FX3100 SNR" unique_id: fx3100_snr state: "{{ state_attr('sensor.fx3100_status', 'statusBarSNR') }}" - name: "FX3100 Signal Bars" unique_id: fx3100_signal_bars state: "{{ state_attr('sensor.fx3100_status', 'statusBarSignalBars') }}" - name: "FX3100 Sim2 Connection State" unique_id: fx3100_sim2_connection_state state: "{{ state_attr('sensor.fx3100_status', 'statusBarSim2ConnectionState') }}" - name: "FX3100 Sim2 Network" unique_id: fx3100_sim2_network state: "{{ state_attr('sensor.fx3100_status', 'statusBarSim2Network') }}" - name: "FX3100 Sim2 Signal Bars" unique_id: fx3100_sim2_signal_bars state: "{{ state_attr('sensor.fx3100_status', 'statusBarSim2SignalBars') }}" - name: "FX3100 Sim2 Status" unique_id: fx3100_sim2_status state: "{{ state_attr('sensor.fx3100_status', 'statusBarSim2Status') }}" - name: "FX3100 Sim2 Technology" unique_id: fx3100_sim2_technology state: "{{ state_attr('sensor.fx3100_status', 'statusBarSim2Technology') }}" - name: "FX3100 Sim2 Technology Text" unique_id: fx3100_sim2_technology_text state: "{{ state_attr('sensor.fx3100_status', 'statusBarSim2TechnologyText') }}" - name: "FX3100 Sim Carrier Blocked Status" unique_id: fx3100_sim_carrier_blocked_status state: "{{ state_attr('sensor.fx3100_status', 'statusBarSimCarrierBlockedStatus') }}" - name: "FX3100 Sim MMCode" unique_id: fx3100_sim_mmcode state: "{{ state_attr('sensor.fx3100_status', 'statusBarSimMMCode') }}" - name: "FX3100 Sim Slots Count" unique_id: fx3100_sim_slots_count state: "{{ state_attr('sensor.fx3100_status', 'statusBarSimSlotsCount') }}" - name: "FX3100 Sim Status" unique_id: fx3100_sim_status state: "{{ state_attr('sensor.fx3100_status', 'statusBarSimStatus') }}" - name: "FX3100 SMS Unread Count" unique_id: fx3100_sms_unread_count state: "{{ state_attr('sensor.fx3100_status', 'statusBarSmsUnreadCount') }}" - name: "FX3100 Technology" unique_id: fx3100_technology state: "{{ state_attr('sensor.fx3100_status', 'statusBarTechnology') }}" - name: "FX3100 Technology Text" unique_id: fx3100_technology_text state: "{{ state_attr('sensor.fx3100_status', 'statusBarTechnologyText') }}" - name: "FX3100 Traffic Status" unique_id: fx3100_traffic_status state: "{{ state_attr('sensor.fx3100_status', 'statusBarTrafficStatus') }}" - name: "FX3100 VPN Connect Disconnect Button Text" unique_id: fx3100_vpn_connect_disconnect_button_text state: "{{ state_attr('sensor.fx3100_status', 'statusBarVpnConnectDisconnectButtonText') }}" - name: "FX3100 VPN Connection State" unique_id: fx3100_vpn_connection_state state: "{{ state_attr('sensor.fx3100_status', 'statusBarVpnConnectionState') }}" - name: "FX3100 WiFi Client List Size" unique_id: fx3100_wifi_client_list_size state: "{{ state_attr('sensor.fx3100_status', 'statusBarWiFiClientListSize') }}" - name: "FX3100 WiFi Enabled" unique_id: fx3100_wifi_enabled state: "{{ state_attr('sensor.fx3100_status', 'statusBarWiFiEnabled') }}" - name: "FX3100 External Antenna Enabled" unique_id: fx3100_ext_antenna_enabled state: "{{ state_attr('sensor.fx3100_status', 'statusExtAntennaEnabled') }}" 

I downloaded the DJI Mimo app version 1.12.0 (227503) from DJI's own website. Using Android 14.
I've complained about their terrible software before (forcing you to make an account, forcing you to turn location on just to use the Pocket camera...) but now I've noticed that when I run the app, this folder called "Chang Pian" is added to the DCIM folder.
It's empty, but it will be recreated along with the DJI Export and DJI Album folders whenever I reopen the app. Specifically, the DJI Export and DJI Album folders are created as soon as you agree to the TOS, and Chang Pian is created as soon as the package file is unpacked and loaded.
Searching for the name "Chang Pian" online turns up nothing helpful, even when combining with search terms like DJI and Android. What's going on here?
I only use it to update the Pocket's internal clock, so I basically treat this app as hostile and prevent it from ever getting network access. Perhaps other users can check their device to see if they have anything in this folder.
https://preview.redd.it/1lxdu9qfnl1d1.png?width=540&format=png&auto=webp&s=cc3f4ae880b3051f670ff9779da43faf966e09ea
1710904596679-DJI-Mimo-official-release-227503_sec.apk
SHA1: 8864DB2D7EB628963FAFE6FA9FF0025F43D0D4EB
Size 654MB (just 4MB too big to scan with VirusTotal)

Recover WD External Hard Drive Data
External hard drives are commonly used for storing private and confidential corporate data as well as backup files. Problems arise as a result of its widespread use. Many customers want to purchase good software to complete a WD external hard disk data recovery. BLR Tools introduces a fantastic piece of software.
Western Digital external hard drives are popular among consumers because of their ease, big data storage capacity, and fast data transfer speed. Despite all of the portable capabilities of external hard drives, you may be frustrated by the potential problems that can occur with WD hard drives, such as a WD external hard drive not working or a WD passport not recognizing Windows 10. As a result, the most pressing problem is how to perform a WD external hard drive data recovery.

Possible causes of data loss on external hard drives

In summary, your data may be lost from a WD external hard disk for the following reasons:

• Unintentional file deletion or disk formatting.
• Virus attack or invasion.
• Corrupted file system
• Broken computesystem
• The partition table was damaged.
• Unexpected power failure or surge.

True Example of Western Digital External Hard Drive Recovery

Is it possible to retrieve data from such a WD external hard drive? The answer is yes. If you choose the correct aid, recovering a WD external hard disk is simple.

WD External Hard Drive Data Recovery

BLR Data Recovery is one of the best WD data recovery software options for recovering data from an external hard drive safely. It is widely used and has a positive reputation.

What is BLR Data Recovery?

BLR Data Recovery can restore files from a variety of sources, including external hard disks. You can use this software to restore files in the following situations:

• Important files are deleted accidentally from a WD external hard drive;
• Crucial files are not visible on a WD external hard drive;
• On your computer, a WD external hard drive shows as unknown.
• A WD external hard disk does not show up on your PC.
• A WD external hard drive stops operating,

This free file recovery program offers you a clean and secure data recovery environment. Your original data will be undamaged, so you can utilize it with confidence. In the following content, I'll walk you through the process of recovering data from a WD external hard drive.

How To Recover Data From A WD External Hard Drive

Step 1: Download and install BLR NAS Data Recovery on your PC.
Step 2: Connect your WD external hard drive to your computer and start the software. If you can't find the hard drive on the main interface, click the Refresh button to bring it up or reconnect the device.
Step 3: This step is optional. To maximize performance, go to the Scan Settings interface and choose specific categories of files or file systems before scanning. After making your changes, click OK to save them, and then return to the main interface.
Step 4: On this PC screen, you have two options:
Logical Drives: This section lists all of your computer's recognized partitions, including lost partitions, unallocated partitions, RAW partitions, and others. To scan and recover data, you can select a single partition.
Devices: The Devices tab displays a list of all devices that are connected to your computer. You can select to scan the entire device at once. Consequently, the scan time will be longer than scanning a partition.
Step 5: Wait for the scan to complete. On the result page, you'll see three folders: deleted files, lost files, and existing files. You can extend different paths to find the files you want.
Step 6: Checkmark the boxes in front of the files you require. After that, click the Save button and choose a suitable path to save these files.
Step 7: Click OK to start the recovery procedure.
When the process is finished, you can navigate to the specified location to check your files. If you need to recover data from a WD external hard drive on a Mac, Stellar Data Recovery for Mac is an excellent option.

Here are several ways you can fix the problem:

Method 1: Change the Drive Letter.
If your external hard drive lacks a drive letter, it will not be detected by the computer. You can assign it a new drive letter using Disk Management.
Step 1: Press Win + X to open the WinX menu and select Disk Management.
Step 2: Right-click the external hard disk.
Step 3: Select Change Drive Letter and Paths from the context menu.
Step 4: To assign a drive letter to the drive, click the Add button, then click OK to save the changes.
Then, check to see if the drive displays in File Explorer.
Method 2: Update or Reinstall the Driver
The problem could be caused by an incompatible driver. You can try updating the related driver to see if that solves the issue.
Step 1: To open Device Manager, press Win + S and type it into the search box.
Step 2: Press Enter to bring up the window.
Step 3: Expand the Disk Drives section and right-click the external hard drive.
Step 4: Select Update Driver and Automatically Search for Drivers.
Method 3: Run the Hardware and Devices Troubleshooter.
You can also use the Hardware and Devices troubleshooter to diagnose and resolve hardware issues on your computer. This utility can help you fix the WD external hard drive not showing up.
Step 1: To open the Run window, press Win + R.
Step 2: Type cmd and press Enter to launch Command Prompt.
Step 3: To access the Hardware and Devices troubleshooter, run msdt.exe -id Device Diagnostic and press Enter.

Last Words

External hard drives are widely acknowledged to be portable in numerous ways. You may also choose to store big volumes of vital data on the WD external hard drive without regard for data loss. Errors may arise for a variety of causes, with no indication on your external hard disk. If you don't have backups, you should use professional data recovery software, such as BLR Tools Power Data Recovery.