homekit | : house : A HomeKit Accessory implementation in Node.js

I have this code:

I am trying to mimic the following curl:

I have small SwiftUI app, tab bar items have two color, selected have blue color and unselected have gray color and when I click the tab bar items , background switching to the dark color, and I want to change tab bar items border color like selected will have blue color, unselected will have red color when background switch to dark color , is it possible?

DemoView:

My app was rejected for TestFlight Beta as follows:

"Guideline 2.5.4 - Performance - Software Requirements

Your app declares support for external-accessory in the UIBackgroundModes key in your Info.plist file but does not declare any external accessory protocols supported by your app. The external accessory background mode is intended for apps that communicate with hardware accessories through the External Accessory framework.

If your app is meant to work with external hardware, supported protocols must be included in the UISupportedExternalAccessoryProtocols key in your app's Info.plist file - and the hardware's PPID # should be provided in the Review Notes field of your app in App Store Connect.

Additionally, your app must be authorized by MFi to use the desired hardware. If you are not yet in the MFi Program, you can enroll at MFi program."

I read similar questions, but none answer or solve my problem.

In Xcode project settings I have checked "Uses Bluetooth LE accessories" under Background Modes.

In info.plist I have NSBluetoothPeriperalUsageDescription="Uses Bluetooth for switches and adaptive toys".

If I uncheck "Uses Bluetooth LE accessories" under Background modes I think my app will be approved, but it leaves out the following important set of users of the app as follows:

The app is for capability switch users in the Accessibility realm, which is already a small set of users. The feature requiring background communication between the app (central) and switches (peripheral) is for a specific subset of switch users that have a visual impairment and significant cognitive delays. This is an even smaller set of users, probably < 100 in the world, but it is an extremely important use case for these users. It is not practical to have the app always in the foreground when they use the app to use audio to say 1 or 2 words, typically "Yes"/"No", or "I need help!”, needed even when there is no WiFi or cell signal. For example, my test user (downloaded to her app directly from my Xcode dev env) with Fox G1 syndrome uses this mode exclusively and has seen great improvements in having some minimal control of things in her life (e.g., saying “I need help” when she feels a seizure coming on or requires diapering).

Current capability switches on the market use the Bluetooth HID profile, which does not allow for background use or 2-way communication between central (my app) and accessory (switch box), to do important feedback like adjusting delay time for switch activations for users with movement disorders and tremors, also the case of my test user.

Has anyone successfully received app approval for background communication with an accessory as a peripheral that is not MFi or HomeKit approved? When I read the MFi FAQ, this peripheral accessory does not appear to fall into the MFi umbrella, and with HomeKit I already came across the limitation that it does not work when the device is sleeping (this latter case is another bone I have to pick, since non-touch users cannot turn on lights, open auto-doors, turn up heaters... unless the device is open which they cannot physically do, and Siri is not an option since they are non-verbal!).

Additional technical background regarding the app: I use only CoreBluetooth (UART), where the app is the central. My API is so simple I am slightly embarrassed to list it, but here goes:

// BLE UART API

let receiveSwitch1On: NSString = "SWITCH1_ON"

let receiveSwitch1Off: NSString = "SWITCH1_OFF"

let receiveSwitch2On: NSString = "SWITCH2_ON"

let receiveSwitch2Off: NSString = "SWITCH2_OFF"

let sendSwitchboxOn: NSString = "ON"

let sendSwitchboxOff: NSString = "OFF"

let updateDebouncePrefix: NSString = "DEBOUNCE="

let updateGraceOffPrefix: NSString = "GRACE_OFF=“

Does anyone have a suggestion on what I could change technically, or advice for navigating the app approval process on what my lowest cost option would be to keep this use case of background comm between app and peripheral? Already I've spent significant time and money to create this capability. I am not in this to make money, but to provide some benefit to a small set of users that are largely left out of technology. I am willing to spend more time and money to reach the finish line, but I really can't afford a lot of ongoing program costs as I expect MFi or HomeKit might be.

Thanks for reading!

I'm running home-assistant in a docker container on MacOS Catalina and need to allow HomeKit to interface with it. I'm trying to register a service with dns-sd to get it to work based on a fix recommended in a thread on the issue. The registration works, but the service doesn't appear afterward if I understand it correctly.

I first enter:

I'm working on an app using Xamarin.iOS. I need to add the possibility to add an accessory to HomeKit using the address coming from an internal API (basically I retrieve the address of the device using a web request). Once I have this setupCode of the accessory I try to use the following API from HomeKit

https://docs.microsoft.com/en-us/dotnet/api/homekit.hmhome.addandsetupaccessories?view=xamarin-ios-sdk-12#HomeKit_HMHome_AddAndSetupAccessories_HomeKit_HMAccessorySetupPayload_System_Action_HomeKit_HMAccessory___Foundation_NSError__

in particular the API with the following signature AddAndSetupAccessories(HMAccessorySetupPayload, Action) but the Action that should be called on completion it's never called.

The only result that I get is that my app tries to go in background but it remain stuck and become unusable.

The only hint that I get from the device log is this:

HomeUIService Host app does not have entitlement 'com.apple.homekit.private-spi-access' or 'com.apple.developer.homekit.allow-setup-payload' -- not allowed to add from URL!

but I have the Entitlement for Homekit added to my app. I'm not able to find any documentation on the entitlements specified in the log message.

Has anyone experienced something like this?

Thank you guys

I'm trying to use Google Sheets as a scraper to get product descriptions prices and images from a specific store. https://www.aliexpress.com/store/group/xiaomi-Aqara-Smart-home/2389096_516541380.html

I'm trying to retrieve the image URLs from this page but in the end, I'm not able to make it work.

I'm making a light with an ESP32 and the HomeKit library I chose uses FreeRTOS and esp-idf, which I'm not familiar with.

Currently, I have a function that's called whenever the colour of the light should be changed, which just changes it in a step. I'd like to have it fade between colours instead, which will require a function that runs for a second or two. Having this block the main execution of the program would obviously make it quite unresponsive, so I need to have it run as a task.

The issue I'm facing is that I only want one copy of the fading function to be running at a time, and if it's called a second time before it's finished, the first copy should exit(without waiting for the full fade time) before starting the second copy.

I found vTaskDelete, but if I were to just kill the fade function at an arbitrary point, some variables and the LEDs themselves will be in an unknown state. To get around this, I thought of using a 'kill flag' global variable which the fading function will check on each of its loops.

Here's the pseudocode I'm thinking of: