Failed to build with latest nightly rustc.

Description
Failed to build with latest rustc due to deprecated feature [stdsimd] in ahash. Successfully built when use rustc 1.78.0-nightly (b11fbfbf3 2024-02-03) (an older nightly version) or stable rustc.

To Reproduce
rustup update
rustup default nightly # should be 1.85.0 in 2024-12-04
git clone https://github.com/thomas-mauran/chess-tui
cd chess-tui
cargo build --release

Expected behavior
Built successfully.

Error message

cargo build --release
   Compiling ahash v0.8.6
error[E0635]: unknown feature `stdsimd`
  --> ~/.cargo/registry/src/rsproxy.cn-0dccff568467c15b/ahash-0.8.6/src/lib.rs:99:42
   |
99 | #![cfg_attr(feature = "stdsimd", feature(stdsimd))]
   |                                          ^^^^^^^

For more information about this error, try `rustc --explain E0635`.
error: could not compile `ahash` (lib) due to 1 previous error

Environment

OS: Ubuntu 22.04.5 LTS on Windows 10 x86_64
Terminal Emulator: vscode
Font: consolas
Crate version: 1.5.0
Backend: none

Additional context
Rustc: rustc 1.85.0-nightly (c44b3d50f 2024-12-03)
Update ahash to 0.89 and above may solve the problem. Run cargo tree -i ahash and we get:
ahash v0.8.6
└── hashbrown v0.14.3
    └── lru v0.12.1
        └── ratatui v0.28.1
            └── chess-tui v1.5.0 (/home/adamska/chess-tui)

So update ratatui may solve this problem, but I'm not sure which version the is most appropriate. Or just compile with stable rustc.

Back to the dependencies tree
ahash v0.8.6
└── hashbrown v0.14.3
    └── lru v0.12.1
        └── ratatui v0.28.1
            └── chess-tui v1.5.0 (/home/adamska/chess-tui)

I took a quick view at crates.io and found that hashbrown v0.15.0 has removed ahash from its dependencies. run cargo update -p hashbrown will update it to 0.14.6, that may help. But cargo update -p lru will update hashbrown to 0.15.0, I guess that's better. After this everything works well.


Fix behavior of retrieve state tool

Resolves #2097
New behavior is:
Parse a BlockIdentifier from the command line argument for height.
Check on disk for each block file, download only when appropriate.

How does this work if https://github.com/casper-network/casper-node/pull/2032 hasn't been merged yet 🤔

How does this work if #2032 hasn't been merged yet thinking

That was split up, so the retrieve-state tool itself merged with #2078 and dry-run-deploys will follow.

How does this work if #2032 hasn't been merged yet thinking

That was split up, so the retrieve-state tool itself merged with #2078 and dry-run-deploys will follow.

Can you update the description and title of that PR then? It still mentiones the "retrieve state tool".

bors merge

bors merge

bors try

Closing in favor of #2182


 This will decrease load time and make the site interactive little bit faster.
While the are loading or in case of network failure the profile picture block will be light greyish block.
Testing Plan: I tested this by adding some extra users and messages (./manage.py populate_db -n100 --extra-users 100), then once the message list loads disabled the network using devtools.
GIFs or Screenshots:

This looks great; sorry for the slow review (October was a rough month for me).  Can you rebase this?
(And just to make sure I understand the screenshots, before we'd just have a blank area where the images were supposed to load, and now we have grey rounded rectanges?  It'd be good to have a night theme screenshot too)

(And just to make sure I understand the screenshots, before we'd just have a blank area where the images were supposed to load, and now we have grey rounded rectanges? It'd be good to have a night theme screenshot too)

The rounded rectangles is the img tag, it stays like that since we set the height and width of the image tag. I just added a background color to the img tag so when the images fail to load in rare cases due to internet the color makes it look nice rather than just nothing there. (I somehow lost the css part that add the background color during last rebase which might have confused you in this case!)

Screenshots (including dark mode)

It looks like the lazysizes library is built on IntersectionObserver. What happens on IE and Safari where IntersectionObserver is not supported?

In theory I thought that it would load images as normal if IntersectionObserver was not supported but to my surprise it lazyloads in IE. I think it uses event listener on scroll event which is not as fast as IntersectionObserver.

Merged as 6441ad06777a83f5ccc61c534dafd18be2ee57ed, after updating PROVISION_VERSION and yarn.lock, as well as making it close #3564.  Thanks @priyank-p for doing this and @andersk for the good questions.


palindrom-errors uses window object which is not available in NodeJs

Here palindrom-errors.js uses window.location.href as a default value for a parameter.
This is not applicable when running inside NodeJs, since the global window object is not available.
constructor(message, side, url = window.location.href, connectionType) {

I suggest to remove the default value at all from the constructor and pass window.location.href from elsewhere.


AWS adapter

:tada: This issue has been resolved in version 1.12.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Error while scaling down of nodes on an upgraded Rancher set up

**What kind of request is this (question/bug/enhancement/feature request):**bug
Steps to reproduce (least amount of steps as possible):

On rancher:v2.1.7, create a cluster with one node(all roles)
Upgrade rancher to v2.2.0-rc8.
scale up the nodes in the cluster to one node. (all roles) (number of nodes in cluster - 2)
wait for the cluster to come in active state.
perform steps 3 and 4 again. (number of nodes in cluster - 3)
perform steps 3 and 4 again. (number of nodes in cluster - 4)
Now, click on Edit Cluster, change the count of nodes in the all roles nodes from 4 to 3. And add a worker node.
Click on save.

Expected Result:
Cluster comes to active state after updating.
Actual Result:
Cluster gets stuck while trying to delete the control plane. Error is seen on the UI/Logs - Failed to delete controlplane node [ip-address] from cluster: Get https://ipaddress:6443/api/v1/nodes?timeout=30s: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.1.7 to v2.2.0-rc8
Installation option (single install/HA): HA install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Hosted - AWS
Kubernetes version (use kubectl version):

v1.13.4

Docker version (use docker version):

18.9.3

moving out

I see this or a similar issue when creating a cluster in 2.3.6 with nodes of 2 Cores and 4GiB of RAM. I've seen these sorts of issues may be caused by resource issues, but I also see them in clusters where this is not the case
Steps:

Deploy cluster with 1 cp/etcd node
Scale up to 3 nodes using + in the UI
Scale down to 1 node

Alternatively, I also see failures when scaling down one node at a time.  After a cp/etcd node was removed in the v2.3.6 cluster (leaving 2 behind) I saw one of the two get stuck with waiting on the node to respond (unfortunately I lost the screenshot and error).  Deleting the node forced a recreation and resolved the issue.
I've been unable to recreate on the same cluster after this, though I've seen this behavior on many test clusters.  As the cluster ages, it appears to become more able to perform a node pool scale down, but that may just be circumstantial.


[DC-2051] removing slack messaging for exceptions

GCP monitoring is configured to monitor for warnings or higher in the application
should remove redundant messaging from the application now.
update the unit tests to expect alert removal

This one also failed with what appears to be a keyword restriction on google buckets.  This branch is closed in favor of the pr at https://github.com/all-of-us/curation/pull/1065.


On Windows64 the Shift key doesn't produce capital letters

Maybe I'm missing something, but I can't type capital letters using the Shift key.  (Or quotation marks, or tildes, or any character you normally use the Shift key to produce.)  I am able to select text using the Shift key.
I'm running Micro version: 3deee51 on go1.6.2 windows/amd64.

I've gotten access to windows now, so I'll try to fix this problem.

Sorry I didn't get to this earlier, but I didn't have access to a windows computer. It should be fixed now.


Loop of Child bridge process ended

Describe The Bug:

The plugin was working flawlessy for several month, but now the Child bridge process ends continually
To Reproduce:

I have remove the plugin, clean the cache, restart the server, reinstall the plugin, reconfigure my Haiku Fan.
The process start normaly. when I restart Homebridge, the child bridge process ends again continually
Expected behavior:

The process stay up after a Homebridge restart
Logs:
[24/09/2022, 20:21:22] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[24/09/2022, 20:21:22] [BigAssFans-i6] Initializing child bridge 0E:7A:F6:A6:CA:CB
[24/09/2022, 20:21:24] [homebridge-i6-bigassfans] Launched child bridge with PID 4695
[24/09/2022, 20:21:24] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[24/09/2022, 20:21:24] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully
[24/09/2022, 20:21:24] [homebridge-i6-bigassfans] Init - initializing devices
[24/09/2022, 20:21:24] [homebridge-i6-bigassfans] Adding new accessory: Haiku_Salon

This a part of the loop :
[24/09/2022, 20:30:17] [homebridge-i6-bigassfans] Restarting Process...
[24/09/2022, 20:30:19] [homebridge-i6-bigassfans] Launched child bridge with PID 11307
[24/09/2022, 20:30:20] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[24/09/2022, 20:30:20] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully
[24/09/2022, 20:30:20] Loaded 1 cached accessories from cachedAccessories.0E7AF6A6CACB.
[24/09/2022, 20:30:20] [homebridge-i6-bigassfans] Loading accessory from cache: Haiku_Salon
[24/09/2022, 20:30:20] [homebridge-i6-bigassfans] Init - initializing devices
[24/09/2022, 20:30:20] [homebridge-i6-bigassfans] Restoring existing accessory from cache: Haiku_Salon
Error: listen EADDRINUSE: address already in use :::45070
    at Server.setupListenHandle [as _listen2] (node:net:1372:16)
    at listenInCluster (node:net:1420:12)
    at Server.listen (node:net:1508:7)
    at EventedHTTPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:155:20)
    at HAPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:332:21)
    at Bridge.<anonymous> (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1279:18)
    at step (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
    at Object.next (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:125:57)
    at fulfilled (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:115:62)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[24/09/2022, 20:30:20] [homebridge-i6-bigassfans] Child bridge process ended
[24/09/2022, 20:30:20] [homebridge-i6-bigassfans] Process Ended. Code: 1, Signal: null

[24/09/2022, 20:30:27] [homebridge-i6-bigassfans] Restarting Process...
[24/09/2022, 20:30:30] [homebridge-i6-bigassfans] Launched child bridge with PID 11328
[24/09/2022, 20:30:30] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[24/09/2022, 20:30:30] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully
[24/09/2022, 20:30:30] Loaded 1 cached accessories from cachedAccessories.0E7AF6A6CACB.
[24/09/2022, 20:30:30] [homebridge-i6-bigassfans] Loading accessory from cache: Haiku_Salon
[24/09/2022, 20:30:30] [homebridge-i6-bigassfans] Init - initializing devices
[24/09/2022, 20:30:30] [homebridge-i6-bigassfans] Restoring existing accessory from cache: Haiku_Salon
Error: listen EADDRINUSE: address already in use :::45070
    at Server.setupListenHandle [as _listen2] (node:net:1372:16)
    at listenInCluster (node:net:1420:12)
    at Server.listen (node:net:1508:7)
    at EventedHTTPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:155:20)
    at HAPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:332:21)
    at Bridge.<anonymous> (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1279:18)
    at step (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
    at Object.next (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:125:57)
    at fulfilled (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:115:62)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[24/09/2022, 20:30:31] [homebridge-i6-bigassfans] Child bridge process ended
[24/09/2022, 20:30:31] [homebridge-i6-bigassfans] Process Ended. Code: 1, Signal: null

Plugin Config:
Note : I have remove the "pin", "ip address" and "mac Address"
{
    "bridge": {
        "name": "Homebridge AADC",
        "username": "0E:95:9B:BC:AA:DC",
        "port": 51808,
        "pin": "",
        "advertiser": "avahi"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "auth": "form",
            "theme": "purple",
            "tempUnits": "c",
            "lang": "auto",
            "sessionTimeout": 57600,
            "platform": "config"
        },
{
            "fans": [
                {
                    "name": "Haiku_Salon",
                    "ip": "",
                    "mac": "",
                    "fanModel": "Haiku H/I Series",
                    "showWhooshSwitch": true,
                    "showFanAutoSwitch": false,
                    "showLightAutoSwitch": false,
                    "showDimToWarmSwitch": false,
                    "showEcoModeSwitch": true
                }
            ],
            "_bridge": {
                "username": "0E:7A:F6:A6:CA:CB",
                "port": 45070
            },
            "platform": "BigAssFans-i6"
        }
    ]
}

Screenshots:

Environment:: Homebridge run on a Raspberry Pi 4B, Raspbian GNU/Linux 11 (bullseye)

Plugin Version: 0.5.1
Homebridge Version:  1.5.0
Node.js Version:  v16.16.0
NPM Version:  8.11.0
Operating System:  Homebridge run on a Raspberry Pi 4B, Raspbian GNU/Linux 11 (bullseye)

Hello  Are there any messages between timestamps [24/09/2022, 20:21:24]  and [24/09/2022, 20:30:17]?

Yes, it's a repetition of what you see between
[homebridge-i6-bigassfans] Restarting Process...
(...)
[homebridge-i6-bigassfans] Process Ended. Code: 1, Signal: null
For you information, I've decided to restart my homebridge setup from scratch
I've flashed my SD card with the software "Raspberry Pi Imager v1.7.3", with the "Official Homebridge Raspberry Pi Image" dated 2022-07-08. On startup, there was one update available for the Homebridge UI. After the update the version was "homebridge-config-ui-x v4.50.1". After that, I installed the "Big Ass Fans i6" plugin version "homebridge-i6-bigassfans v0.5.1". After that, I add to the configuration one of my Haiku Fan.
The result puzzled me. The system started normally, buy when I tried to add the Homebridge setup to Homekit with the QR Code, It failed several times. I disabled the "Big Ass Fans I6" plugin and after that I was able to add Homebridge to Homekit without any delay. I enabled again the plugin, restart Homebridge and I tried to add my Haiku Fan but the Fan doesn't appeared in the list of devices to be added...

Second test:
I configure the plugin to use a Child Bridge. I restarted the Homebridge. Everything was fine. I restarted Homebridge a second time. The loop started again.
[25/09/2022, 12:42:58] [Homebridge UI] Changes to config.json saved.
[25/09/2022, 12:43:00] [Homebridge UI] Homebridge restart request received
[25/09/2022, 12:43:00] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[25/09/2022, 12:43:00] [Homebridge UI] Sending SIGTERM to Homebridge
[25/09/2022, 12:43:07] [Homebridge UI] Sending SIGKILL to Homebridge
[25/09/2022, 12:43:07] [HB Supervisor] Homebridge Process Ended. Code: null, Signal: SIGKILL
[25/09/2022, 12:43:12] [HB Supervisor] Restarting Homebridge...
[25/09/2022, 12:43:12] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules -D --strict-plugin-resolution
[25/09/2022, 12:43:12] [HB Supervisor] Started Homebridge v1.5.0 with PID: 4680
[25/09/2022, 12:43:13] Loaded config.json with 0 accessories and 2 platforms.
[25/09/2022, 12:43:13] Loaded 2 cached accessories from cachedAccessories.
[25/09/2022, 12:43:13] ---
[25/09/2022, 12:43:13] Loaded plugin<EMAIL_ADDRESS>[25/09/2022, 12:43:13] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[25/09/2022, 12:43:13] ---
[25/09/2022, 12:43:13] Loading 2 platforms...
[25/09/2022, 12:43:13] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[25/09/2022, 12:43:13] [BigAssFans-i6] Initializing child bridge 0E:DC:DD:AD:B7:EC
[25/09/2022, 12:43:13] Failed to find plugin to handle accessory Haiku-Salon
[25/09/2022, 12:43:13] Removing orphaned accessory Haiku-Salon
[25/09/2022, 12:43:13] Failed to find plugin to handle accessory Haiku-Salon
[25/09/2022, 12:43:13] Removing orphaned accessory Haiku-Salon
[25/09/2022, 12:43:13] Publishing bridge accessory (name: Homebridge B9C9, publishInfo: {
username: '0E:98:04:15:B9:C9',
port: 51704,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://00251TTL51B9Q
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 955-63-785 │
└────────────┘

[25/09/2022, 12:43:13] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge B9C9) is running on port 51704.
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] Launched child bridge with PID 4691
[25/09/2022, 12:43:14] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] Finished initializing platform
[25/09/2022, 12:43:14] Publishing bridge accessory (name: homebridge-i6-bigassfans, publishInfo: {
username: '0E:DC:DD:AD:B7:EC',
port: 52360,
pincode: '--',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] Executed didFinishLaunching callback
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] Init - initializing devices
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] Adding new accessory: Haiku-Salon
[25/09/2022, 12:43:14] Homebridge v1.5.0 (HAP v0.10.2) (homebridge-i6-bigassfans) is running on port 52360.
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] dblog progress(0/0) Haiku-Salon - product type: Haiku H/I Series (0x48, 0x61, 0x69, 0x6b, 0x75, 0x20, 0x48, 0x2f, 0x49, 0x20, 0x53, 0x65, 0x72, 0x69, 0x65, 0x73)
[25/09/2022, 12:43:14] [homebridge-i6-bigassfans] dblog progress(0/0) Haiku-Salon - firmware: 3.1.0
[25/09/2022, 12:43:27] [Homebridge UI] Homebridge restart request received
[25/09/2022, 12:43:27] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[25/09/2022, 12:43:27] [Homebridge UI] Sending SIGTERM to Homebridge
[25/09/2022, 12:43:27] Got SIGTERM, shutting down Homebridge...
[25/09/2022, 12:43:32] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[25/09/2022, 12:43:37] [HB Supervisor] Restarting Homebridge...
[25/09/2022, 12:43:37] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules -D --strict-plugin-resolution
[25/09/2022, 12:43:37] [HB Supervisor] Started Homebridge v1.5.0 with PID: 4716
[25/09/2022, 12:43:39] Loaded config.json with 0 accessories and 2 platforms.
[25/09/2022, 12:43:39] Loaded 0 cached accessories from cachedAccessories.
[25/09/2022, 12:43:39] ---
[25/09/2022, 12:43:39] Loaded plugin<EMAIL_ADDRESS>[25/09/2022, 12:43:39] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[25/09/2022, 12:43:39] ---
[25/09/2022, 12:43:39] Loading 2 platforms...
[25/09/2022, 12:43:39] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[25/09/2022, 12:43:39] [BigAssFans-i6] Initializing child bridge 0E:DC:DD:AD:B7:EC
[25/09/2022, 12:43:39] Publishing bridge accessory (name: Homebridge B9C9, publishInfo: {
username: '0E:98:04:15:B9:C9',
port: 51704,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://00251TTL51B9Q
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 955-63-785 │
└────────────┘

[25/09/2022, 12:43:39] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge B9C9) is running on port 51704.
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Launched child bridge with PID 4727
[25/09/2022, 12:43:41] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully
[25/09/2022, 12:43:41] Loaded 1 cached accessories from cachedAccessories.0EDCDDADB7EC.
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Finished initializing platform
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Loading accessory from cache: Haiku-Salon
[25/09/2022, 12:43:41] Publishing bridge accessory (name: homebridge-i6-bigassfans, publishInfo: {
username: '0E:DC:DD:AD:B7:EC',
port: 52360,
pincode: '--',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Executed didFinishLaunching callback
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Init - initializing devices
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Restoring existing accessory from cache: Haiku-Salon
Error: listen EADDRINUSE: address already in use :::52360
at Server.setupListenHandle [as _listen2] (node:net:1372:16)
at listenInCluster (node:net:1420:12)
at Server.listen (node:net:1508:7)
at EventedHTTPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:155:20)
at HAPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:332:21)
at Bridge. (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1279:18)
at step (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
at Object.next (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:125:57)
at fulfilled (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:115:62)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Child bridge process ended
[25/09/2022, 12:43:41] [homebridge-i6-bigassfans] Process Ended. Code: 1, Signal: null
[25/09/2022, 12:43:48] [homebridge-i6-bigassfans] Restarting Process...
[25/09/2022, 12:43:50] [homebridge-i6-bigassfans] Launched child bridge with PID 4751
[25/09/2022, 12:43:50] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[25/09/2022, 12:43:50] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully
[25/09/2022, 12:43:50] Loaded 1 cached accessories from cachedAccessories.0EDCDDADB7EC.
[25/09/2022, 12:43:50] [homebridge-i6-bigassfans] Finished initializing platform
[25/09/2022, 12:43:50] [homebridge-i6-bigassfans] Loading accessory from cache: Haiku-Salon
[25/09/2022, 12:43:50] Publishing bridge accessory (name: homebridge-i6-bigassfans, publishInfo: {
username: '0E:DC:DD:AD:B7:EC',
port: 52360,
pincode: '--',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
[25/09/2022, 12:43:50] [homebridge-i6-bigassfans] Executed didFinishLaunching callback
[25/09/2022, 12:43:50] [homebridge-i6-bigassfans] Init - initializing devices
[25/09/2022, 12:43:50] [homebridge-i6-bigassfans] Restoring existing accessory from cache: Haiku-Salon
Error: listen EADDRINUSE: address already in use :::52360
at Server.setupListenHandle [as _listen2] (node:net:1372:16)
at listenInCluster (node:net:1420:12)
at Server.listen (node:net:1508:7)
at EventedHTTPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:155:20)
at HAPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:332:21)
at Bridge. (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1279:18)
at step (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
at Object.next (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:125:57)
at fulfilled (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:115:62)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[25/09/2022, 12:43:51] [homebridge-i6-bigassfans] Child bridge process ended
[25/09/2022, 12:43:51] [homebridge-i6-bigassfans] Process Ended. Code: 1, Signal: null
[25/09/2022, 12:43:58] [homebridge-i6-bigassfans] Restarting Process...
[25/09/2022, 12:43:59] [homebridge-i6-bigassfans] Launched child bridge with PID 4762
[25/09/2022, 12:43:59] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[25/09/2022, 12:43:59] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully
[25/09/2022, 12:43:59] Loaded 1 cached accessories from cachedAccessories.0EDCDDADB7EC.
[25/09/2022, 12:43:59] [homebridge-i6-bigassfans] Finished initializing platform
[25/09/2022, 12:43:59] [homebridge-i6-bigassfans] Loading accessory from cache: Haiku-Salon
[25/09/2022, 12:43:59] Publishing bridge accessory (name: homebridge-i6-bigassfans, publishInfo: {
username: '0E:DC:DD:AD:B7:EC',
port: 52360,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
[25/09/2022, 12:43:59] [homebridge-i6-bigassfans] Executed didFinishLaunching callback
[25/09/2022, 12:43:59] [homebridge-i6-bigassfans] Init - initializing devices
[25/09/2022, 12:43:59] [homebridge-i6-bigassfans] Restoring existing accessory from cache: Haiku-Salon
Error: listen EADDRINUSE: address already in use :::52360
at Server.setupListenHandle [as _listen2] (node:net:1372:16)
at listenInCluster (node:net:1420:12)
at Server.listen (node:net:1508:7)
at EventedHTTPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/eventedhttp.ts:155:20)
at HAPServer.listen (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:332:21)
at Bridge. (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1279:18)
at step (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
at Object.next (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:125:57)
at fulfilled (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:115:62)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[25/09/2022, 12:44:00] [homebridge-i6-bigassfans] Child bridge process ended
[25/09/2022, 12:44:00] [homebridge-i6-bigassfans] Process Ended. Code: 1, Signal: null
[25/09/2022, 12:44:03] [Homebridge UI] Changes to config.json saved.
[25/09/2022, 12:44:03] [homebridge-i6-bigassfans] Stopping child bridge (will not restart)...

Is homebridge-i6-bigassfans the only plugin you use with homebridge?
I searched for "[HB Supervisor] Homebridge Process Ended. Code: 143" and am going through the results looking for a clue.
The "address already in use" error means there's probably a child bridge still alive that's bound to that address.  But I think that's a symptom, not a cause.  Once you see "Homebridge Process Ended. Code: 143, Signal: null" nothing after that really matters.  It appears exit code 143 is the result of a SIGTERM, implying something is deliberately trying to gracefully kill the process.  So the question is what and why.

Check out https://www.reddit.com/r/homebridge/comments/mml26u/homebridge_seems_to_restart_constantly/ and see dev_oznu's solution helps.

Yes, right now it's the only plugin in my configuration since I've reinstall everything from scratch.
The proposed solution was for a Homebridge configuration on a Mac and my Homebridge run on a Raspberry Pi.
Here's the result for the first command proposed by dev_oznu:
pi@homebridge:~ $ launchctl unload ~/Library/LaunchAgents/com.homebridge.server.plist
-bash: launchctl: command not found

Can you try running homebridge without the UI?  On the pi, hb-service stop, then run homebridge -I -D.

Sorry, I'm some kind of a newbi for that :(
First command worked
For the second command, is it the homebridge script found at /var/lib/homebridge/node_modules/homebridge/bin?
The result is :
pi@homebridge:/var/lib/homebridge/node_modules/homebridge/bin $ ./homebridge -I -D
/usr/bin/env: ‘node’: No such file or directory

Never mind that idea, it probably wouldn't have helped anyway.  Go ahead and restart homebridge with hb-service start.  I trust that will get you back to where you were.
How about setting all the switch options for your fan to false in the config and clear the cache and restart to see what happens.

Same result.
I just remember that I installed the same plugin for my girlfriend and it works fine right now.
Here the difference
node -v (v16.4.2 => I have v16.16.0)
npm -v (8.7.0 => I have V8.11.0)
Do you know how to downgrade node.js?

Offhand I don't know how to downgrade node.  But a search tells me nvm install <version-number>  In the meantime I'm going to upgrade my version to 16.16.0 and see if that breaks the plugin.

I just accidentally found out you can downgrade with hb-service update-node <version>.

Thanks,
I downgrade node.js but no effect. I will restart from scratch but with the image Raspbian-Homebridge-v1.0.33.zip instead of Raspbian-Homebridge-v1.0.38.zip. I will let you know.

okey doke.
I'm thinking at some point we try to run without the child bridge and resolve whatever issues come up there (QR failure [try to add with QR code before adding config for fan], fan doesn't appear [remove bridge using Home app]).

I installed from scratch with Raspbian-Homebridge-v1.0.33.zip. At the beginning, I configure my Haiku Fan as "Haiku H/I Series" as before and I had the same weird result.
After that, I remembered that my girlfriend has a "Haiku L" fan. Then I configured my fan as if it was an "Haiku L". With that, I was able to add Homebridge to HomeKit and the child bridge also. No loop with that. But no communication with the fan.

OK I will try that

I restarted from scratch again with Raspbian-Homebridge-v1.0.33.zip and Raspbian-Homebridge-v1.0.38.zip.
Installation of the plugin Big Ass Fans i6 version homebridge-i6-bigassfans v0.5.1 with no fan configured and no Child Bridge
Successfuly added Homebridge to HomeKit with QR code
Haiku Fan configuration added to the plugin with "Haiku L series" instead of "Haiku H/I series"
Failure to add the Fan in Homekit
I've changed the Fan configuration to "Haiku H/I series" and it still failed.

Can you show me the log file from when you start homebridge and it fails to add the fan? On Sep 25, 2022, at 8:44 PM, thicla01 @.***> wrote:
I restarted from scratch again with Raspbian-Homebridge-v1.0.33.zip and Raspbian-Homebridge-v1.0.38.zip.
Installation of the plugin Big Ass Fans i6 version homebridge-i6-bigassfans v0.5.1 with no fan configured and no Child Bridge
Successfuly added Homebridge to HomeKit with QR code
Haiku Fan configuration added to the plugin with "Haiku L series" instead of "Haiku H/I series"
Failure to add the Fan in Homekit
I've changed the Fan configuration to "Haiku H/I series" and it still failed.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Can you show me the log file from when you start homebridge and it fails to add the fan?

Hello oogje,
Another day, another test. I've downgrade the plugin to the version homebridge-i6-bigassfans v0.4.3. And the fan appeared like by magic in homekit :)

I'm at work right now. I will redo the test with the version 0.5.1 and see if there is logs for the failure to add the fan in HomeKit.

Second test. Adding the second fan with the Plugin v0.4.3: Success

Third test. Upgrading the Plugin to 0.5.1. The communication with the fans stop.
Downgrading the Plugin to 0.4.3. The communication with the fans works again.

Send logs from 0.5.1 failure please - from the time you start homebridge until it's apparent there's no communication.

Case 1) Using version 0.5.1, adding Homebridge in HomeKit without any fan in the configuration. Adding the fan in the configuration but unable to add the fan in HomeKit
[26/09/2022, 19:29:14] [HB Supervisor] Restarting Homebridge...
[26/09/2022, 19:29:14] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[26/09/2022, 19:29:14] [HB Supervisor] Started Homebridge v1.5.0 with PID: 1406
[26/09/2022, 19:29:15] Loaded config.json with 0 accessories and 2 platforms.
[26/09/2022, 19:29:15] ---
[26/09/2022, 19:29:16] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:29:16] Registering platform 'homebridge-config-ui-x.config'
[26/09/2022, 19:29:16] ---
[26/09/2022, 19:29:16] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:29:16] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[26/09/2022, 19:29:16] ---
[26/09/2022, 19:29:16] Loading 2 platforms...
[26/09/2022, 19:29:16] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[26/09/2022, 19:29:16] [BigAssFans-i6] Finished initializing platform
[26/09/2022, 19:29:16] [BigAssFans-i6] Executed didFinishLaunching callback
[26/09/2022, 19:29:16] [BigAssFans-i6] Init - initializing devices
[26/09/2022, 19:29:16] [BigAssFans-i6] -------------------------------------------
[26/09/2022, 19:29:16] [BigAssFans-i6] Init - no fan configuration found
[26/09/2022, 19:29:16] [BigAssFans-i6] Missing fans in your platform config
[26/09/2022, 19:29:16] [BigAssFans-i6] -------------------------------------------
[26/09/2022, 19:29:16] Publishing bridge accessory (name: Homebridge 300E, publishInfo: {
username: '0E:AB:29:EC:30:0E',
port: 51144,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://0024RHJNQTBJJ
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 781-94-886 │
└────────────┘

[26/09/2022, 19:29:16] Homebridge v1.5.0 (HAP v0.10.4) (Homebridge 300E) is running on port 51144.
[26/09/2022, 19:29:18] [Homebridge UI] Removed /var/lib/homebridge/persist/AccessoryInfo.0EAB29EC300E.json
[26/09/2022, 19:29:18] [Homebridge UI] Removed /var/lib/homebridge/persist/IdentifierCache.0EAB29EC300E.json
[26/09/2022, 19:29:23] [Homebridge UI] Homebridge Reset: New Username: 0E:19:56:99:AE:83
[26/09/2022, 19:29:23] [Homebridge UI] Homebridge Reset: New Pin: 824-60-360
[26/09/2022, 19:29:23] [Homebridge UI] Changes to config.json saved.
[26/09/2022, 19:29:23] [Homebridge UI] Homebridge Reset: "persist" directory removed.
[26/09/2022, 19:29:23] [Homebridge UI] Homebridge Reset: "accessories" directory removed.
[26/09/2022, 19:29:23] [Homebridge UI] Homebridge restart request received
[26/09/2022, 19:29:23] [Homebridge UI] Sending SIGTERM to process...
[26/09/2022, 19:29:23] [HB Supervisor] Stopping services...
[26/09/2022, 19:29:23] Got SIGTERM, shutting down Homebridge...
[26/09/2022, 19:29:23] Failed to save cached accessories to disk: ENOENT: no such file or directory, open '/var/lib/homebridge/accessories/cachedAccessories'
[26/09/2022, 19:29:23] Your accessories will not persist between restarts until this issue is resolved.
[26/09/2022, 19:29:28] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[26/09/2022, 19:29:35] [HB Supervisor] OS: Linux 5.15.32-v7l+ arm
[26/09/2022, 19:29:35] [HB Supervisor] Node.js v16.14.2 /usr/local/bin/node
[26/09/2022, 19:29:35] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[26/09/2022, 19:29:35] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[26/09/2022, 19:29:40] [Homebridge UI] Homebridge Config UI X v4.50.1 is listening on :: port 8581
[26/09/2022, 19:29:40] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[26/09/2022, 19:29:40] [HB Supervisor] Started Homebridge v1.5.0 with PID: 1485
[26/09/2022, 19:29:41] Loaded config.json with 0 accessories and 2 platforms.
[26/09/2022, 19:29:41] ---
[26/09/2022, 19:29:42] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:29:42] Registering platform 'homebridge-config-ui-x.config'
[26/09/2022, 19:29:42] ---
[26/09/2022, 19:29:43] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:29:43] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[26/09/2022, 19:29:43] ---
[26/09/2022, 19:29:43] Loading 2 platforms...
[26/09/2022, 19:29:43] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[26/09/2022, 19:29:43] [BigAssFans-i6] Finished initializing platform
[26/09/2022, 19:29:43] [BigAssFans-i6] Executed didFinishLaunching callback
[26/09/2022, 19:29:43] [BigAssFans-i6] Init - initializing devices
[26/09/2022, 19:29:43] [BigAssFans-i6] -------------------------------------------
[26/09/2022, 19:29:43] [BigAssFans-i6] Init - no fan configuration found
[26/09/2022, 19:29:43] [BigAssFans-i6] Missing fans in your platform config
[26/09/2022, 19:29:43] [BigAssFans-i6] -------------------------------------------
[26/09/2022, 19:29:43] Publishing bridge accessory (name: Homebridge 300E, publishInfo: {
username: '0E:19:56:99:AE:83',
port: 51144,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://0024U0YX4GXPG
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 824-60-360 │
└────────────┘

[26/09/2022, 19:29:43] Homebridge v1.5.0 (HAP v0.10.4) (Homebridge 300E) is running on port 51144.
[26/09/2022, 19:29:44] [Homebridge UI] Starting terminal session
[26/09/2022, 19:31:08] [Homebridge UI] Terminal session ended.
[26/09/2022, 19:32:05] [Homebridge UI] Changes to config.json saved.
[26/09/2022, 19:32:12] [Homebridge UI] Homebridge restart request received
[26/09/2022, 19:32:12] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[26/09/2022, 19:32:12] [Homebridge UI] Sending SIGTERM to Homebridge
[26/09/2022, 19:32:12] Got SIGTERM, shutting down Homebridge...
[26/09/2022, 19:32:17] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[26/09/2022, 19:32:22] [HB Supervisor] Restarting Homebridge...
[26/09/2022, 19:32:22] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[26/09/2022, 19:32:22] [HB Supervisor] Started Homebridge v1.5.0 with PID: 1681
[26/09/2022, 19:32:23] Loaded config.json with 0 accessories and 2 platforms.
[26/09/2022, 19:32:23] Loaded 0 cached accessories from cachedAccessories.
[26/09/2022, 19:32:23] ---
[26/09/2022, 19:32:24] [Homebridge UI] Starting terminal session
[26/09/2022, 19:32:24] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:32:24] Registering platform 'homebridge-config-ui-x.config'
[26/09/2022, 19:32:24] ---
[26/09/2022, 19:32:24] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:32:24] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[26/09/2022, 19:32:24] ---
[26/09/2022, 19:32:24] Loading 2 platforms...
[26/09/2022, 19:32:24] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[26/09/2022, 19:32:24] [BigAssFans-i6] Finished initializing platform
[26/09/2022, 19:32:24] [BigAssFans-i6] Executed didFinishLaunching callback
[26/09/2022, 19:32:24] [BigAssFans-i6] Init - initializing devices
[26/09/2022, 19:32:24] [BigAssFans-i6] Adding new accessory: Haiku Salon
[26/09/2022, 19:32:24] Publishing bridge accessory (name: Homebridge 300E, publishInfo: {
username: '0E:19:56:99:AE:83',
port: 51144,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://0024U0YX4GXPG
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 824-60-360 │
└────────────┘

[26/09/2022, 19:32:24] Homebridge v1.5.0 (HAP v0.10.4) (Homebridge 300E) is running on port 51144.
[26/09/2022, 19:32:24] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - product type: Haiku H/I Series (0x48, 0x61, 0x69, 0x6b, 0x75, 0x20, 0x48, 0x2f, 0x49, 0x20, 0x53, 0x65, 0x72, 0x69, 0x65, 0x73)
[26/09/2022, 19:32:24] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - firmware: 3.1.0

Step 2) Removing fan configuration, downgrading to version 0.4.3
[26/09/2022, 19:44:19] [Homebridge UI] Homebridge restart request received
[26/09/2022, 19:44:19] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[26/09/2022, 19:44:19] [Homebridge UI] Sending SIGTERM to Homebridge
[26/09/2022, 19:44:23] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[26/09/2022, 19:44:28] [HB Supervisor] Restarting Homebridge...
[26/09/2022, 19:44:28] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[26/09/2022, 19:44:28] [HB Supervisor] Started Homebridge v1.5.0 with PID: 2247
[26/09/2022, 19:44:29] Loaded config.json with 0 accessories and 2 platforms.
[26/09/2022, 19:44:29] Loaded 1 cached accessories from cachedAccessories.
[26/09/2022, 19:44:29] ---
[26/09/2022, 19:44:29] [Homebridge UI] Starting terminal session
[26/09/2022, 19:44:30] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:44:30] Registering platform 'homebridge-config-ui-x.config'
[26/09/2022, 19:44:30] ---
[26/09/2022, 19:44:30] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:44:30] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[26/09/2022, 19:44:30] ---
[26/09/2022, 19:44:30] Loading 2 platforms...
[26/09/2022, 19:44:30] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[26/09/2022, 19:44:30] [BigAssFans-i6] Finished initializing platform
[26/09/2022, 19:44:30] [BigAssFans-i6] Loading accessory from cache: Haiku Salon
[26/09/2022, 19:44:30] [BigAssFans-i6] Executed didFinishLaunching callback
[26/09/2022, 19:44:30] [BigAssFans-i6] Init - initializing devices
[26/09/2022, 19:44:30] [BigAssFans-i6] -------------------------------------------
[26/09/2022, 19:44:30] [BigAssFans-i6] Init - no fan configuration found
[26/09/2022, 19:44:30] [BigAssFans-i6] Missing fans in your platform config
[26/09/2022, 19:44:30] [BigAssFans-i6] -------------------------------------------
[26/09/2022, 19:44:30] Publishing bridge accessory (name: Homebridge 300E, publishInfo: {
username: '0E:19:56:99:AE:83',
port: 51144,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://0024U0YX4GXPG
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 824-60-360 │
└────────────┘

[26/09/2022, 19:44:30] Homebridge v1.5.0 (HAP v0.10.4) (Homebridge 300E) is running on port 51144.

Step 3) Adding fan configuration and restart (The fan appears in HomeKit and can be control by Home app)
[26/09/2022, 19:47:11] [Homebridge UI] Terminal session ended.
[26/09/2022, 19:47:56] [Homebridge UI] Changes to config.json saved.
[26/09/2022, 19:47:59] [Homebridge UI] Starting terminal session
[26/09/2022, 19:48:09] [Homebridge UI] Terminal session ended.
[26/09/2022, 19:48:09] [Homebridge UI] Homebridge restart request received
[26/09/2022, 19:48:09] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[26/09/2022, 19:48:09] [Homebridge UI] Sending SIGTERM to Homebridge
[26/09/2022, 19:48:09] Got SIGTERM, shutting down Homebridge...
[26/09/2022, 19:48:15] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[26/09/2022, 19:48:20] [HB Supervisor] Restarting Homebridge...
[26/09/2022, 19:48:20] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[26/09/2022, 19:48:20] [HB Supervisor] Started Homebridge v1.5.0 with PID: 2390
[26/09/2022, 19:48:21] Loaded config.json with 0 accessories and 2 platforms.
[26/09/2022, 19:48:21] Loaded 1 cached accessories from cachedAccessories.
[26/09/2022, 19:48:21] ---
[26/09/2022, 19:48:21] [Homebridge UI] Starting terminal session
[26/09/2022, 19:48:22] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:48:22] Registering platform 'homebridge-config-ui-x.config'
[26/09/2022, 19:48:22] ---
[26/09/2022, 19:48:22] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:48:22] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[26/09/2022, 19:48:22] ---
[26/09/2022, 19:48:22] Loading 2 platforms...
[26/09/2022, 19:48:22] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[26/09/2022, 19:48:22] [BigAssFans-i6] Finished initializing platform
[26/09/2022, 19:48:22] [BigAssFans-i6] Loading accessory from cache: Haiku Salon
[26/09/2022, 19:48:22] [BigAssFans-i6] Executed didFinishLaunching callback
[26/09/2022, 19:48:22] [BigAssFans-i6] Init - initializing devices
[26/09/2022, 19:48:22] [BigAssFans-i6] Restoring existing accessory from cache: Haiku Salon
[26/09/2022, 19:48:22] Publishing bridge accessory (name: Homebridge 300E, publishInfo: {
username: '0E:19:56:99:AE:83',
port: 51144,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://0024U0YX4GXPG
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 824-60-360 │
└────────────┘

[26/09/2022, 19:48:22] Homebridge v1.5.0 (HAP v0.10.4) (Homebridge 300E) is running on port 51144.
[26/09/2022, 19:48:22] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - model: Haiku H/I Series (0x48, 0x61, 0x69, 0x6b, 0x75, 0x20, 0x48, 0x2f, 0x49, 0x20, 0x53, 0x65, 0x72, 0x69, 0x65, 0x73)
[26/09/2022, 19:48:22] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - firmware: 3.1.0
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0x90, 0x04] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0x98, 0x04] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa8, 0x05] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0xe8, 0x06] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - light detected
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - current relative humidity out of range: 1000, assuming no humidity sensor for model "Haiku H/I Series"
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa0, 0x05] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0x82, 0x0b] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0x8a, 0x0b] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0x92, 0x0b] === undefined
[26/09/2022, 19:48:22] [BigAssFans-i6] Haiku Salon - propertiesTable[0x9a, 0x0b] === undefined
[26/09/2022, 19:48:43] [BigAssFans-i6] Haiku Salon - propertiesTable[0x90, 0x04] === undefined
[26/09/2022, 19:48:43] [BigAssFans-i6] Haiku Salon - propertiesTable[0x98, 0x04] === undefined
[26/09/2022, 19:48:43] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa8, 0x05] === undefined
[26/09/2022, 19:48:43] [BigAssFans-i6] Haiku Salon - propertiesTable[0xe8, 0x06] === undefined
[26/09/2022, 19:48:43] [BigAssFans-i6] Haiku Salon - propertiesTable[0x90, 0x04] === undefined
[26/09/2022, 19:48:43] [BigAssFans-i6] Haiku Salon - propertiesTable[0x98, 0x04] === undefined
[26/09/2022, 19:48:44] [BigAssFans-i6] Haiku Salon - propertiesTable[0x90, 0x04] === undefined
[26/09/2022, 19:48:44] [BigAssFans-i6] Haiku Salon - propertiesTable[0x98, 0x04] === undefined
[26/09/2022, 19:48:44] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa8, 0x05] === undefined
[26/09/2022, 19:48:44] [BigAssFans-i6] Haiku Salon - propertiesTable[0xe8, 0x06] === undefined

Step 4) Upgrading to 0.5.1 and restart (The fan is still in HomeKit but no control via Home app)
[26/09/2022, 19:50:40] [Homebridge UI] Terminal session ended.
[26/09/2022, 19:50:44] [Homebridge UI] Running Command: sudo -E -n npm install -g<EMAIL_ADDRESS>[26/09/2022, 19:50:49] [Homebridge UI] Homebridge restart request received
[26/09/2022, 19:50:49] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[26/09/2022, 19:50:49] [Homebridge UI] Sending SIGTERM to Homebridge
[26/09/2022, 19:50:49] Got SIGTERM, shutting down Homebridge...
[26/09/2022, 19:50:54] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[26/09/2022, 19:50:59] [HB Supervisor] Restarting Homebridge...
[26/09/2022, 19:50:59] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[26/09/2022, 19:50:59] [HB Supervisor] Started Homebridge v1.5.0 with PID: 2518
[26/09/2022, 19:51:00] Loaded config.json with 0 accessories and 2 platforms.
[26/09/2022, 19:51:00] Loaded 1 cached accessories from cachedAccessories.
[26/09/2022, 19:51:00] ---
[26/09/2022, 19:51:01] [Homebridge UI] Starting terminal session
[26/09/2022, 19:51:01] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:51:01] Registering platform 'homebridge-config-ui-x.config'
[26/09/2022, 19:51:01] ---
[26/09/2022, 19:51:01] Loaded plugin<EMAIL_ADDRESS>[26/09/2022, 19:51:01] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[26/09/2022, 19:51:01] ---
[26/09/2022, 19:51:01] Loading 2 platforms...
[26/09/2022, 19:51:01] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[26/09/2022, 19:51:01] [BigAssFans-i6] Finished initializing platform
[26/09/2022, 19:51:01] [BigAssFans-i6] Loading accessory from cache: Haiku Salon
[26/09/2022, 19:51:01] [BigAssFans-i6] Executed didFinishLaunching callback
[26/09/2022, 19:51:01] [BigAssFans-i6] Init - initializing devices
[26/09/2022, 19:51:01] [BigAssFans-i6] Restoring existing accessory from cache: Haiku Salon
[26/09/2022, 19:51:01] [BigAssFans-i6] use of "whoosh" configuration attribute is deprecated, please use "showWhooshSwitch" instead
[26/09/2022, 19:51:01] [BigAssFans-i6] Haiku Salon- use of "fanAuto" configuration attribute is deprecated, please use "showFanAutoSwitch" instead
[26/09/2022, 19:51:01] [BigAssFans-i6] Haiku Salon- use of "lightAuto" configuration attribute is deprecated, please use "showLightAutoSwitch" instead
[26/09/2022, 19:51:01] [BigAssFans-i6] Haiku Salon- use of "ecoMode" configuration attribute is deprecated, please use "showEcoModeSwitch" instead
[26/09/2022, 19:51:01] Publishing bridge accessory (name: Homebridge 300E, publishInfo: {
username: '0E:19:56:99:AE:83',
port: 51144,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://0024U0YX4GXPG
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 824-60-360 │
└────────────┘

[26/09/2022, 19:51:01] Homebridge v1.5.0 (HAP v0.10.4) (Homebridge 300E) is running on port 51144.
[26/09/2022, 19:51:01] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - product type: Haiku H/I Series (0x48, 0x61, 0x69, 0x6b, 0x75, 0x20, 0x48, 0x2f, 0x49, 0x20, 0x53, 0x65, 0x72, 0x69, 0x65, 0x73)
[26/09/2022, 19:51:01] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - firmware: 3.1.0

Thanks!
It's interesting that things work with v0.4.3 of the plugin. but I don't know why it doesn't work with v0.5.1.
All the steps show "Publishing bridge accessory..." in the logs.  Does that mean the plugin is using a child bridge in these steps?
Can I see the config file as it stands now assuming it hasn't changed since Step 4.
Does the fan show up in the accessories section of the Homebridge UI?  If so can you control it from there?

Hello oogje,
I don't use any Child Bridge for step 1 to 4.
Here is the config file used in Step 4:
{
"bridge": {
"name": "Homebridge 300E",
"username": "0E:19:56:99:AE:83",
"port": 51144,
"pin": "824-60-360",
"advertiser": "avahi"
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"fans": [
{
"name": "Haiku Salon",
"ip": "Removed",
"mac": "Removed",
"fanModel": "Haiku H/I Series",
"whoosh": true,
"fanAuto": true,
"lightAuto": true,
"dimToWarm": false,
"ecoMode": true
}
],
"platform": "BigAssFans-i6"
}
]
}
At step 4, the fan is still in the accessory list but no control. Same thing for the Home app in iOS.

Would you install<EMAIL_ADDRESS>and add these attributes to your config for the Haiku Salon:
...
"dimToWarm": false,
"ecoMode": true,
"debugLevels": [
  ["network", 4],
  ["redflags", 1],
  ["characteristics", 3]
]
...

then restart and try to turn the fan on and off and show the logs?

Hello oogje,
The new config
{
"bridge": {
"name": "Homebridge 300E",
"username": "0E:19:56:99:AE:83",
"port": 51144,
"pin": "824-60-360",
"advertiser": "avahi"
},
"accessories": [],
"platforms": [
{
"name": "Config",
"port": 8581,
"platform": "config"
},
{
"fans": [
{
"name": "Haiku Salon",
"ip": "Removed",
"mac": "Removed",
"fanModel": "Haiku H/I Series",
"whoosh": true,
"fanAuto": true,
"lightAuto": true,
"dimToWarm": false,
"ecoMode": true,
"debugLevels": [
[
"network",
4
],
[
"redflags",
1
],
[
"characteristics",
3
]
]
}
],
"platform": "BigAssFans-i6"
}
]
}
Here is the result :
[27/09/2022, 15:32:00] [Homebridge UI] Terminal session ended.
[27/09/2022, 15:32:00] [Homebridge UI] Homebridge restart request received
[27/09/2022, 15:32:00] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[27/09/2022, 15:32:00] [Homebridge UI] Sending SIGTERM to Homebridge
[27/09/2022, 15:32:07] [Homebridge UI] Sending SIGKILL to Homebridge
[27/09/2022, 15:32:07] [HB Supervisor] Homebridge Process Ended. Code: null, Signal: SIGKILL
[27/09/2022, 15:32:12] [HB Supervisor] Restarting Homebridge...
[27/09/2022, 15:32:12] [HB Supervisor] Starting Homebridge with extra flags: -I -D
[27/09/2022, 15:32:12] [HB Supervisor] Started Homebridge v1.5.0 with PID: 21512
[27/09/2022, 15:32:13] Loaded config.json with 0 accessories and 2 platforms.
[27/09/2022, 15:32:13] Loaded 1 cached accessories from cachedAccessories.
[27/09/2022, 15:32:13] ---
[27/09/2022, 15:32:14] [Homebridge UI] Starting terminal session
[27/09/2022, 15:32:14] Loaded plugin<EMAIL_ADDRESS>[27/09/2022, 15:32:14] Registering platform 'homebridge-config-ui-x.config'
[27/09/2022, 15:32:14] ---
[27/09/2022, 15:32:14] Loaded plugin<EMAIL_ADDRESS>[27/09/2022, 15:32:14] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6'
[27/09/2022, 15:32:14] ---
[27/09/2022, 15:32:14] Loading 2 platforms...
[27/09/2022, 15:32:14] [BigAssFans-i6] Initializing BigAssFans-i6 platform...
[27/09/2022, 15:32:14] [BigAssFans-i6] Finished initializing platform
[27/09/2022, 15:32:14] [BigAssFans-i6] Loading accessory from cache: Haiku Salon
[27/09/2022, 15:32:14] [BigAssFans-i6] Executed didFinishLaunching callback
[27/09/2022, 15:32:14] [BigAssFans-i6] Init - initializing devices
[27/09/2022, 15:32:14] [BigAssFans-i6] Restoring existing accessory from cache: Haiku Salon
[27/09/2022, 15:32:14] [BigAssFans-i6] use of "whoosh" configuration attribute is deprecated, please use "showWhooshSwitch" instead
[27/09/2022, 15:32:14] [BigAssFans-i6] Haiku Salon- use of "fanAuto" configuration attribute is deprecated, please use "showFanAutoSwitch" instead
[27/09/2022, 15:32:14] [BigAssFans-i6] Haiku Salon- use of "lightAuto" configuration attribute is deprecated, please use "showLightAutoSwitch" instead
[27/09/2022, 15:32:14] [BigAssFans-i6] Haiku Salon- use of "ecoMode" configuration attribute is deprecated, please use "showEcoModeSwitch" instead
[27/09/2022, 15:32:14] Publishing bridge accessory (name: Homebridge 300E, publishInfo: {
username: '0E:19:56:99:AE:83',
port: 51144,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: 'avahi'
}).
Setup Payload:
X-HM://0024U0YX4GXPG
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 824-60-360 │
└────────────┘

[27/09/2022, 15:32:14] Homebridge v1.5.0 (HAP v0.10.4) (Homebridge 300E) is running on port 51144.
[27/09/2022, 15:32:15] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - product type: Haiku H/I Series (0x48, 0x61, 0x69, 0x6b, 0x75, 0x20, 0x48, 0x2f, 0x49, 0x20, 0x53, 0x65, 0x72, 0x69, 0x65, 0x73)
[27/09/2022, 15:32:15] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - firmware: 3.1.0
[27/09/2022, 15:32:15] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update fan auto: false
[27/09/2022, 15:32:15] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update FanOn: false
[27/09/2022, 15:32:15] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update RotationDirection: 1
[27/09/2022, 15:32:15] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update Whoosh:true
[27/09/2022, 15:32:15] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update Eco Mode:true

Thanks.  Now please change the ["network", 4] to ["network", 8] and restart.  I'd like to see the log file after that change but it will have some info like your MAC and IP encoded as hex numbers, so you might want to mail it to me rather than include it here.  Is so, you can send to<EMAIL_ADDRESS>

My bad, make that ["network", 11], please.

Logs sent to<EMAIL_ADDRESS>

Got it, thanks.

Can you (try to) turn the light off and on with Home app, and then the BAF app and send the log please.  Make a note of the time when you use the Home app, and when you use the BAF app, thanks.

With the Home app, there is no communication with the fan and therefore no logs and no response from the fan.
With the BAF app, the fan react to turning on and off the light but no log is generated.
In the homebridge's accessories section, there is no device.

Here is the result with the plugin version 0.4.3
Home app (Time : 18:40)
[27/09/2022, 18:40:02] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - Set Characteristic Light On -> false
[27/09/2022, 18:40:02] [BigAssFans-i6] dblog network(7/11) Haiku Salon - sending c0120712051a03a00400c0
[27/09/2022, 18:40:02] [BigAssFans-i6] dblog network(8/11) Haiku Salon - accessory client got: 127 bytes
[27/09/2022, 18:40:02] [BigAssFans-i6] dblog network(11/11) Haiku Salon - raw (unstuffed) data: 0xc0, 0x12, 0x79, 0x22, 0x77, 0x12, 0x03, 0xa8, 0x04, 0x00, 0x12, 0x03, 0xb0, 0x04, 0x00, 0x12, 0x03, 0xa0, 0x04, 0x00, 0x12, 0x04, 0xb8, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf0, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf8, 0x04, 0x8c, 0x15, 0x12, 0x06, 0xe2, 0x04, 0x03, 0x6e, 0x6f, 0x77, 0x12, 0x03, 0xe8, 0x04, 0x00, 0x12, 0x03, 0x90, 0x05, 0x00, 0x12, 0x07, 0x9a, 0x05, 0x04, 0x08, 0x01, 0x18, 0x01, 0x12, 0x03, 0xe0, 0x0a, 0x01, 0x12, 0x06, 0xf0, 0x0a, 0x80, 0xdd, 0xdb, 0x01, 0x12, 0x07, 0xe8, 0x0a, 0xff, 0xff, 0xff, 0xff, 0x0f, 0x12, 0x03, 0xf8, 0x0a, 0x00, 0x12, 0x03, 0xc0, 0x04, 0x01, 0x12, 0x04, 0xc8, 0x04, 0xd8, 0x04, 0x12, 0x03, 0xd0, 0x04, 0x00, 0x12, 0x04, 0xd8, 0x04, 0xa0, 0x38, 0x12, 0x03, 0xa8, 0x05, 0x01, 0x12, 0x03, 0xe8, 0x06, 0x00, 0xc0
[27/09/2022, 18:40:02] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa8, 0x05] === undefined
[27/09/2022, 18:40:02] [BigAssFans-i6] Haiku Salon - propertiesTable[0xe8, 0x06] === undefined
[27/09/2022, 18:40:04] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - Set Characteristic Light On -> true
[27/09/2022, 18:40:04] [BigAssFans-i6] dblog network(7/11) Haiku Salon - sending c0120712051a03a00401c0
[27/09/2022, 18:40:04] [BigAssFans-i6] dblog network(8/11) Haiku Salon - accessory client got: 127 bytes
[27/09/2022, 18:40:04] [BigAssFans-i6] dblog network(11/11) Haiku Salon - raw (unstuffed) data: 0xc0, 0x12, 0x79, 0x22, 0x77, 0x12, 0x03, 0xa8, 0x04, 0x28, 0x12, 0x03, 0xb0, 0x04, 0x07, 0x12, 0x03, 0xa0, 0x04, 0x01, 0x12, 0x04, 0xb8, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf0, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf8, 0x04, 0x8c, 0x15, 0x12, 0x06, 0xe2, 0x04, 0x03, 0x6e, 0x6f, 0x77, 0x12, 0x03, 0xe8, 0x04, 0x00, 0x12, 0x03, 0x90, 0x05, 0x00, 0x12, 0x07, 0x9a, 0x05, 0x04, 0x08, 0x01, 0x18, 0x01, 0x12, 0x03, 0xe0, 0x0a, 0x01, 0x12, 0x06, 0xf0, 0x0a, 0x80, 0xdd, 0xdb, 0x01, 0x12, 0x07, 0xe8, 0x0a, 0xff, 0xff, 0xff, 0xff, 0x0f, 0x12, 0x03, 0xf8, 0x0a, 0x00, 0x12, 0x03, 0xc0, 0x04, 0x01, 0x12, 0x04, 0xc8, 0x04, 0xd8, 0x04, 0x12, 0x03, 0xd0, 0x04, 0x00, 0x12, 0x04, 0xd8, 0x04, 0xa0, 0x38, 0x12, 0x03, 0xa8, 0x05, 0x01, 0x12, 0x03, 0xe8, 0x06, 0x00, 0xc0
[27/09/2022, 18:40:04] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa8, 0x05] === undefined
[27/09/2022, 18:40:04] [BigAssFans-i6] Haiku Salon - propertiesTable[0xe8, 0x06] === undefined
[27/09/2022, 18:40:04] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update Brightness: 40
BAF app (Time 18:42)
[27/09/2022, 18:42:01] [BigAssFans-i6] dblog network(8/11) Haiku Salon - accessory client got: 127 bytes
[27/09/2022, 18:42:01] [BigAssFans-i6] dblog network(11/11) Haiku Salon - raw (unstuffed) data: 0xc0, 0x12, 0x79, 0x22, 0x77, 0x12, 0x03, 0xa8, 0x04, 0x00, 0x12, 0x03, 0xb0, 0x04, 0x00, 0x12, 0x03, 0xa0, 0x04, 0x00, 0x12, 0x04, 0xb8, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf0, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf8, 0x04, 0x8c, 0x15, 0x12, 0x06, 0xe2, 0x04, 0x03, 0x6e, 0x6f, 0x77, 0x12, 0x03, 0xe8, 0x04, 0x00, 0x12, 0x03, 0x90, 0x05, 0x00, 0x12, 0x07, 0x9a, 0x05, 0x04, 0x08, 0x01, 0x18, 0x01, 0x12, 0x03, 0xe0, 0x0a, 0x01, 0x12, 0x06, 0xf0, 0x0a, 0x80, 0xdd, 0xdb, 0x01, 0x12, 0x07, 0xe8, 0x0a, 0xff, 0xff, 0xff, 0xff, 0x0f, 0x12, 0x03, 0xf8, 0x0a, 0x00, 0x12, 0x03, 0xc0, 0x04, 0x01, 0x12, 0x04, 0xc8, 0x04, 0xd8, 0x04, 0x12, 0x03, 0xd0, 0x04, 0x00, 0x12, 0x04, 0xd8, 0x04, 0xa0, 0x38, 0x12, 0x03, 0xa8, 0x05, 0x01, 0x12, 0x03, 0xe8, 0x06, 0x00, 0xc0
[27/09/2022, 18:42:01] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa8, 0x05] === undefined
[27/09/2022, 18:42:01] [BigAssFans-i6] Haiku Salon - propertiesTable[0xe8, 0x06] === undefined
[27/09/2022, 18:42:01] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update Light On: false
[27/09/2022, 18:42:04] [BigAssFans-i6] dblog network(8/11) Haiku Salon - accessory client got: 127 bytes
[27/09/2022, 18:42:04] [BigAssFans-i6] dblog network(11/11) Haiku Salon - raw (unstuffed) data: 0xc0, 0x12, 0x79, 0x22, 0x77, 0x12, 0x03, 0xa8, 0x04, 0x28, 0x12, 0x03, 0xb0, 0x04, 0x07, 0x12, 0x03, 0xa0, 0x04, 0x01, 0x12, 0x04, 0xb8, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf0, 0x04, 0x8c, 0x15, 0x12, 0x04, 0xf8, 0x04, 0x8c, 0x15, 0x12, 0x06, 0xe2, 0x04, 0x03, 0x6e, 0x6f, 0x77, 0x12, 0x03, 0xe8, 0x04, 0x00, 0x12, 0x03, 0x90, 0x05, 0x00, 0x12, 0x07, 0x9a, 0x05, 0x04, 0x08, 0x01, 0x18, 0x01, 0x12, 0x03, 0xe0, 0x0a, 0x01, 0x12, 0x06, 0xf0, 0x0a, 0x80, 0xdd, 0xdb, 0x01, 0x12, 0x07, 0xe8, 0x0a, 0xff, 0xff, 0xff, 0xff, 0x0f, 0x12, 0x03, 0xf8, 0x0a, 0x00, 0x12, 0x03, 0xc0, 0x04, 0x01, 0x12, 0x04, 0xc8, 0x04, 0xd8, 0x04, 0x12, 0x03, 0xd0, 0x04, 0x00, 0x12, 0x04, 0xd8, 0x04, 0xa0, 0x38, 0x12, 0x03, 0xa8, 0x05, 0x01, 0x12, 0x03, 0xe8, 0x06, 0x00, 0xc0
[27/09/2022, 18:42:04] [BigAssFans-i6] Haiku Salon - propertiesTable[0xa8, 0x05] === undefined
[27/09/2022, 18:42:04] [BigAssFans-i6] Haiku Salon - propertiesTable[0xe8, 0x06] === undefined
[27/09/2022, 18:42:04] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update Light On: true
[27/09/2022, 18:42:04] [BigAssFans-i6] dblog characteristics(3/3) Haiku Salon - update Brightness: 40

Thanks.  Version 0.4.3 and 0.5.x parse the messages from the fan in different ways.  At this point I understand 0.4.3 works but I can't really compare it to 0.5.x and see what's different because at a low level everything is different.
I think when you flip back and forth between 0.4.3 and 0.5.x it changes things like caches in HomeKit and it would be better if that didn't happen.
If you're okay using 0.4.3 that's fine.  At this point I don't have much of a clue what's going on with your setup.
If want to get to 0.5.x, I think we can eventually figure out why it's not working but it's going to be a lot of "change this config", "restart", "try to turn on the light", "send the logs", "repeat" to get to a solution.
If you want to keep working this, please clean the caches, persistence, etc, run the beta and send me the logs.  If not we can take a break and I'll work with the data I have from you so far.  Either way, I appreciate your help so far.

I'm lucky guy. There is a firmware update tonight for the fan and wall control 3.1.1. I have some communication between homebridge and the fan
[27/09/2022, 22:22:24] [BigAssFans-i6] dblog progress(0/0) Haiku Salon - firmware: 3.1.1

Lol, I have no idea what's going on.

Hello oogje,
I was trying a lot of things today to figure out the problem. I've always tested with my Haiku in the living room. I decided to test with the Haiku in my bedroom. It works with that Haiku and the plugin version 0.5.1! It seems that the problem is with my Haiku in the living room only... I will try a hard reset on that Haiku and will let you know...

If I put both fans in the configuration, everything stop to work...

I sent you the log by email for both fans.

Hello,
I haven't received the email with the log files.

I sent them to this email address<EMAIL_ADDRESS>Is this correct?

Yes, that address is correct.

I just received the with text "Logs with the fan in the bedroom working with plugin version 0.5.2-beta3".

OK I just send them again from another email account. Let me know.

You should receive the second one soon.

I see in the logs for the fan in the bedroom during startup, [16/10/2022, 22:40:40] Restoring existing accessory from cache: Haiku Salon but I presume the bedroom fan is "Haiku Chambre".
Each homebridge accessory must be registered with  unique identifier.  My plugin used the MAC address you specify in the config file as that unique ID.   The plugin should use the MAC address provided by the fan instead of relying on the user to provide it in the config file but that's more complicated for me to code so I rely on the config file.
In fact it doesn't matter what you enter in the config file for the MAC address if it's unique among the accessories, the plugin only uses that for the unique identifier and reports it as the "serial number" to HomeKit.
So, can you verify the MAC address in the config file for the two fans is different?
Next, I notice when you start the Haiku Salon the "persist" and "accessories" are removed.  Can you do that also when you start the Haiku Chambre?
Going forward could you send the config file along with the logs in email with the MAC un-redacted?
The next question is how do you determine when a fan is working?  Are you changing a setting in the Home app to see if it responds?  Or are you making a change with the remote or BAF app to see if the Home app shows the change?  Whatever the method, could you note what you did at the appropriate time in the log file?
Thanks!

For your information, yesterday I noticed that when I configure the Haiku fan that is working properly with the plugin, the CPU of the Raspberry Pi is around 3 to 6% load. With the Haiku fan that is not working, the CPU load is like 30%. There is no other plugins configured when I'm testing.

I got your configs and logs for the two fans.  Perfect, thank you.
Comparing the configs I notice each of the fans uses a different bridge username and port.  Can you make so the "bridge" configurations for the two fans are identical.  Use the configuration that works ("xx:xx:xx:xx:xx:D1"

I got your configs and logs for the two fans. Perfect, thank you.
Comparing the configs I notice each of the fans use a different bridge "username" and "port". Can you make it so the "bridge" configurations for the two fans are identical? Use the working bridge configuration for both fans (the one with "pin" ending in "788").
The only things that should be different between the two config files are the "name", "ip", and "mac" values for the fan.
Can you rerun the test with the "Haiku Salon" and email the config file and results please?

I sent the logs by email a few minutes ago.

I received the logs, thank you.
Can you log into your raspberry pi and operate in the command line?

Yes. What do you need?

I'd like to bypass Homebridge UI.
Is the config file currently set up up for Haiku Salon or Haiku Chamber?

Haiku Chambre

Control working with Accessories in Homebridge UI and HomeKit

Control working with Accessories in Homebridge UI and HomeKit

I don't understand.

Haiku Chambre is working in Homekit right now. I can configure with Haiku Salon it takes 2 minutes.

Sorry for the confusion

Great.

Change "Haiku Chambre" to "test fan".
Change the IP to <IP_ADDRESS>
Change the MAC address to "AB:CD:EF:01:23:45"
save the changes,
start homebridge from the command line by (i'm guessing the path):
/usr/local/lib/node_modules/homebridge/bin/homebridge -I -D
It should output the logs to your window.

Yes, I will send you the new log by email.

email sent

I received it.

I assume it (test fan) still does not show up in the Home app on you iPad?

I have Haiku Chambre and Haiku Salon but both have the warning "No answer". Nothing about "test fan"

kill the homebridge process (cntrl-C in the window you started the command in).  You should get a shell prompt.
remove the caches
rm /var/lib/homebridge/persist/*
rm /var/lib/homebridge/accessories/*

restart
/usr/local/lib/node_modules/homebridge/bin/homebridge -I -D
Anything change in the Home app?

Sorry in a meeting. I will get back to you in a few minutes

No problem.

Done. No change in the Home app in iOS.

Now can you go into the Home app and in the Haiku Salon accessory settings drill down to the bridge and remove it. I would think that would also remove both the Haiku Salon and Haiku Cambre accessories.
If so, go ahead and kill and restart homebridge from the command line and let me know if anything changed in the Home app - like the appearance of the “test fan”.

Now the Haiku Chambre and Haiku Salon are removed. I try to add the bridge to HomeKit but I just have a spinning wheel.

It just timed out. Accessory not available.

Now I need to step away for an hour or so. Sorry.

No problem

Okay, would you edit the name, ip and mac in the config file to the values for the Haiku Chambre,
remove the caches:
rm /var/lib/homebridge/persist/*
rm /var/lib/homebridge/accessories/*

and kill and restart homebridge from the command line.
Can you add the homebridge to the Home app now or does it still time out?

No problem at all.

I'm back sorry. I added the bridge successfuly with the QR code in the Home app. The fan Haiku Chambre is also working.

Do you need the log?

No need for the log, thanks.  Now would you edit the name, ip and mac in the config file to the values for the Haiku Salon,
kill homebridge from the command line,
remove the bridge from the Home app through the Haiku Chambre accessory settings,
remove the caches:
rm /var/lib/homebridge/persist/*
rm /var/lib/homebridge/accessories/*

and restart homebridge from the command line.
And try to add homebridge to the Home app again.

Modifications done.
Trying to add the bridge to the Home app with QR code. Spinning wheel again.

Timed out. Accessory not available.

Before I saw the spinning wheel, I saw the usual message that the accessory is not certified.

If I remember correctly you have a wall controller.  Does it have an IP  address?

Yes

How about adding the Haiku Chambre to the config file as an additional fan, before the Haniku Salon entry.  All parameters the same but ip, mac and name.
kill/restart
Can you add there bridge to the Home app with that configuration.

I just add the wall control related to Haiku Chambre and it's working. I'm able to control the light.

Trying now for Salon

okay

With the wall control related to Haiku Salon, I have the same spinning Wheel.

Timed out

How do you add a wall control?

I just replaced the name, the IP address and the Mac address. I kept the "fanModel" as "Haiku H/I Series",

It's working for the one in the bedroom but not the one in the living room.

I have a feeling that It behaves like a relay

Interesting, I didn't know that would work.
I don't think I ever got a look at the log files when you have both fans configured at the same time.  Can you add the Haiku Chambre to the config file as an additional fan, before the Haiku Salon entry. All parameters for the two fans the same but ip, mac and name.
kill/restart
And email the config and log output.

OK I will do that after dinner

Thanks.
I'm at loss to why the living room fan isn't working with the plugin.  I don't think there's any problem with your fan itself and I don't think there's any problem communicating with your fan.  But I don't have any ideas left now.   I'll give it some thought and reach out to homebridge discord over the next days.

Hello oogje,
Email sent with the new configuration file and the log. Thank you very much for your help and your patience.
Let me know if I can help further. In the meantime, I will use plugin version 0.4.3. Both fans are working fine with that version.

I received the email.
And thank you for your patience.

One last thing, I installed the version 0.4.3 of the plugins with both Haiku fan. In the log I see that part for the Haiku Chambre
[22/10/2022, 12:42:48] [BigAssFans-i6] Haiku Chambre - light detected
That part is missing for Haiku Salon. But it's possible to control the light even if the light seems to be undected in the log.
The CPU load is at 2%

I noticed that because with the plugin version 0.5.x, the light are detected for Haiku Chambre but not for Haiku Salon.

In Homebridge.ui "Accessories" section, the accessories for both fan are created and are working.

Another clue.  Thanks.

After a restart,
[22/10/2022, 13:42:36] [BigAssFans-i6] Haiku Salon - light detected

Fascinating.

On Oct 22, 2022, at 1:45 PM, thicla01 @.***> wrote:
After a restart,
[22/10/2022, 13:42:36] [BigAssFans-i6] Haiku Salon - light detected
—
Reply to this email directly, view it on GitHub https://github.com/oogje/homebridge-i6-bigAssFans/issues/16#issuecomment-1287867735, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKLWWFTFG5D6YVY764FSK3WEQRZ3ANCNFSM6AAAAAAQU3SURU.
You are receiving this because you commented.

I think I found the problem.  Please try<EMAIL_ADDRESS>at your convenience.

Hello oogje,
Good news!
[24/10/2022, 16:12:28] [BigAssFans-i6] Haiku Salon - downlight detected
[24/10/2022, 16:12:28] [BigAssFans-i6] Haiku Salon - no uplight detected
It's working! Accessories created and I have communication with both fan. It's working also with Home app.
I reconfigured everything from scratch and same results, it's working.
Thank you very much.
By curiosity what was the problem?

That's great.  The problem was in parsing the messages from the fan.  That functionality is very different between v0.4.x and v0.5.x and in retrospect it was the obvious place I should have immediately looked at.  But it was the inconsistent "light detected" messages that got me to focus on that part of the code.
The plugin ignores "scheduling" messages from the fan, but it didn't ignore them properly, leaving extraneous data in the message buffer that I then tried to parse which produced seemingly unpredictable behavior.
Thank for sticking with it.

It's was a pleasure to be able to help you. That plugin is really helpful for me :)
Thanks for your great work.


Add Kotlin coroutine based postfix solver

The issue was closed due to the lack of evidence over the benefit to the performance.


How do i add query parameters too OAuth2Authenticator?

RequestParameters.Add() crashes since RequestParameters is not initialized.
i simply need to add promp=none to my request.

@dannyratna562
If you debug the Xamarin.Auth you will see that ctor does initial requests to autorization and token endpoint. This means custom parameters must be passed to ctor and this is what I'm investigating right now (on vacation) -  what is needed to add custom params to the API.
See my investigation and roadmap based on that:
https://github.com/xamarin/Xamarin.Auth/blob/master/docs/details/roadmap.md#11custom-parameters
Basically - working on that.

I'd like to see this implemented.
Currently, the Microsoft Azure workflow requires a custom parameter. When you don't provide the (optional) prompt parameter set to login, if a user has already logged in to a Microsoft account, it will proceed directly to calling the callback URL with that account's information. You have to provide either login or perhaps select_account as a value for that parameter. (I've tested with login, haven't made it to select_account yet.)
I'm frustrated I have to derive a new type from OAuth2Authenticator for this.

We can do the work of populating our own query parameters if this could get implemented in OAuth2Authenticator.GetInitialUrlAsync()? :
if (string.IsNullOrEmpty(queryString))
{
url = this.authorizeUrl;
}
else
{
if (this.authorizeUrl.AbsoluteUri.Contains("?"))
{
url = new Uri(string.Concat(this.authorizeUrl.AbsoluteUri, "&", queryString));
}
else
{
url = new Uri(string.Concat(this.authorizeUrl.AbsoluteUri, "?", queryString));
}
}
Just slap the OAuth parameters on the end if there are already parameters in the URL.


feat: add back gestures for iOS

I've noticed when using the app on iPhone that the back gesture don't work for most screens, this is an effort to make sure it does.

I've noticed when using the app on iPhone that the back gesture don't work for most screens, this is an effort to make sure it does.

I'm not sure why it was disabled in the first place. any clue @UncleSamtoshi ?


add enrich family of functions

Just a bunch of stuff that makes it easier to incrementally create environments.
I'm not too keen about adding zio as a dependency to core. Do we want to split it into its own module?
On the other hand this makes user experience worse 🤔
Do we want an explicit import for the implicit syntax?
Another question is whether we want to overload >>+ or add different symbols for the different cases.
Probably should also add some more docs for it...
/cc @ioleo

@jdegoes if you have an idea for a better / non-colliding symbol, we could change that easily, I plan to have 0.5.0 released at Berlin hackathon, until then this functionality is not yet publicly available

It's kind of similar to @@ in ZIO Test, in the sense that it "augments" the provided left hand side value (the ZIO effect) with additional features.

@mschuwalow WDYT about switching to @@?
// example how it would look like
(ZIO.succeed(new DefaultRuntime {}.Environment)
  @@ enrichClock
  @@ enrichClock
  @@ enrichClockM
  @@ enrichClockManaged
  @@ enrichClock
  @@ enrichBlocking
  @@ enrichBlockingMWithDeps)

@mschuwalow WDYT about switching to @@?
// example how it would look like
(ZIO.succeed(new DefaultRuntime {}.Environment)
  @@ enrichClock
  @@ enrichClock
  @@ enrichClockM
  @@ enrichClockManaged
  @@ enrichClock
  @@ enrichBlocking
  @@ enrichBlockingMWithDeps)

Yeah lets do this. I see you already merged this, so I'll change this in another pr


Add an option to clone webhooks across organizations

@svenkapudija-close are you still looking for a review on this? (I'm just cleaning up some stale PR review requests)


Dropdown inside modal bootstrap4

Hi, I have to use Tokenize inside a modal and I've come across an issue where the dropdown is not shown when Tokenize is used inside a modal.
This can be fixed by adding z-index: 1051; for Bootstrap4 a6.
The problem is that dropdown is hidden under the modals backdrop div which has z-index of 1050.
Is there any way that you could improve on this solution? Or maybe add it so other people have less of an issue with this. If you want I can add the z-index to tokenize2.css and submit a pull request but I think it might be better to see if there are other solutions since my solution could break expected behavior on other projects.

Hi, I've implemented a new feature that set automatically the z-index to the dropdown, there is a new option "zIndexMargin" that you can set the margin, for example in your case, the auto z-index will be 1050 + zIndexMargin, by default it's 1050 + 500 = 1550.
Enjoy !


[New device request] Fairland Full Inverter Pool Heat Pump

Hi,
The heat pump for 15-30m3 pools - Fairland Inverter Plus 6,5kW IPHCR15
https://sklepbasenowy.pl/produkt/fairland-iphcr15/
All options work. Please add this to integration:
https://pastebin.com/kss3N846

This config is almost identical to the GardenPAC config except hvac_action is changed to hvac_mode.  Actually it is a bit strange that the pool heatpumps supported so far have read-only status that can indicate heating or cooling modes, but only an on/off switch, no way to explicitly control the heating or cooling state.  I suspect that all the madimack/gardenpac/fairland heatpumps are actually controllable through dp 105, just that users until now have only been interested in using them to heat.

It says 105 is read only but you can change it without a problem. This config I provided works 100%.All options are working.

Included in 0.19.0 release

Please fix:
- id: 106
name: temperature
type: integer
mapping:
- constraint: temperature_unit
conditions:
- dps_val: false
range:
min: 60
max: 115
range:
min: 12
max: 45
min should be 12 (now it is 16) and it is not possible to set temp in range 12-16.


请问如何将得到的tflite模型进行android的部署

我已经得到了yolov4的tflite模型，并且已经配置好了android studio（android虚拟机），我是应该用android studio去打开项目中的android文件夹吗，具体操作麻烦有大神可以指点一下

https://andy6804tw.github.io/2021/09/02/android-tflite-regression-model-deploy/

@mengxiangqiqin Hi, to deploy the model to android platform, you could follow these steps:

Clone this repo to your local
Install Android Studio
Inside the Android Studio, click "file" --> "open", to open this android project. You should open the "android" directory.
After that, change the model path and label path, set isTiny = true
Done

If the app crash when you started it, see the Logcat in Android Studio, and figure out the error msg.


More prominently feature setup instructions

I spent about 30min trying to figure out how to get the assembly linked into my project. Can you tell users that they need to set the installation namespace and also click the tickmark to install it? Did I miss that somewhere?

Welcome everyone who is willing to provide clearer steps in our documentation!

Can you tell users that they need to set the installation namespace

They don't need. Because they can freely use anything including global. Thus for convenience it will even activate an actual namespace in selected project by default. That's why it can be used without any changes in most cfg.

and also click the tickmark to install it?

Yes, to install you need to click install.

Did I miss that somewhere?

For the mentioned things we have this today:

wiki: https://github.com/3F/DllExport/wiki/Quick-start
screencast: Various cases in a few steps

Feel free to improve our wiki or open PR.
Please don't forget that different configurations are required in different cases. Therefore I'd recommend only clarify your case for common use.
Thanks.

Thanks for the response. Do you mind if I prepare some small instructions to add to the main README? I checked the wiki and examples however none of them referenced the configuration GUI. I understood what most of the settings do but kept missing the tickmark next to the entire lower section that made sure the assembly would be installed into the project.
Putting it somewhere prominent is most helpful.

I think it will be nice to improve exactly the existing 'Quick-start' page in wiki because this page is referenced in many places as a starting point. And this is a good point to explain there some steps in details. Or better new page in addition to Quick-start (just to keep this page short to begin with)

I understood what most of the settings do but kept missing the tickmark next to the entire lower section that made sure the assembly would be installed into the project.

This is a good moment to suggest your ideas into our GUI part. Just open PR and we'll consider it together!


Applying themes?

How does one apply the themes that are in the repo? I can't seem to find the instructions anywhere - I've even tried dropping some less/css into my Atom Stylesheet - but that didn't change anything.
Thanks!

@pierrenel You can apply themes in one of two ways:

Navigate to the Terminal-Plus settings (Preferences > Packages > Search 'Terminal-Plus') and choose one of the built-in themes under the Theme dropdown.
Use the template provided in the README to create your own theme.

Yay thanks so much for the info, all better now.

No problem. Hope you like Terminal-Plus.


Wierd CHarackters

The Chars in the Words "Input" and "Output" are very wierd

Do you mean the font? That's intentional


Training does not result good on RTL languages

Hi @Shreeshrii and others,
I'm trying to train on Arabic dataset and the results get worse after training:

make training GROUND_TRUTH_DIR=data/gt/arabic-dataset/ \
START_MODEL=ckbLayer MODEL_NAME=ckbLayer2 MAX_ITERATIONS=1000 \
LANG_TYPE=RTL BUILD_TYPE=Layer

I tried different start models as well, like ara.traineddata from best and fast repos but no luck.

in the image's gt.txt I have:
محمد عبد الله ريشم خان
This is what in the box file is:

م 0 0 1728 220 0
ح 0 0 1728 220 0
م 0 0 1728 220 0
د 0 0 1728 220 0
  0 0 1728 220 0
ع 0 0 1728 220 0
ب 0 0 1728 220 0
د 0 0 1728 220 0
  0 0 1728 220 0
ا 0 0 1728 220 0
ل 0 0 1728 220 0
ل 0 0 1728 220 0
ه 0 0 1728 220 0
  0 0 1728 220 0
ر 0 0 1728 220 0
ي 0 0 1728 220 0
ش 0 0 1728 220 0
م 0 0 1728 220 0
  0 0 1728 220 0
خ 0 0 1728 220 0
ا 0 0 1728 220 0
ن 0 0 1728 220 0
	 0 0 1728 220 0

Result from the original model: محمد عبد اللە ۔ ر یشم خان
Result from the model trained for 1000 steps: يا لي ن دع ر
Remember when I train an English model on the English dataset, I see improvements on 1000 steps or even lower. Can you guide what is the issue?

I fixed the issue myself, the issue is the box files are reversed for the RTL languages, so you need to reverse the box files again to match LTR. Here is the script I made for this: https://github.com/faizan1041/tesstrain_helpers/blob/main/reverse_box_files.py

If any one facing the same issue, please refer to the script above.

Anyone facing the same issue can generate the box files and run the above script, which will replace the box files content in the revered order.


feature request: able to mark images as sensative/whatever

Cheep Bots Toot Sweet allows you to either hide or show your images via tags, both for the overall bot, and for individual images.
i see that this feature is also available in bluesky, and it would be nice to be able to do so with tags in bot code as well.
(chap bots toot sweat uses {hide} and  {show} before the image)

(having something similar to this text on the edit page for a bot on Blue Bots would be super handy as a reference, btw)

I'm not entirely sure this would work as intended on Bluesky.
First, "sensitive" is not really a binary value on Bluesky, there are different types of sensitive media and when marking a post as sensitive you have to specify which label to add. A simple {hide} would therefore not be enough information for the bot, as it would need to know WHY the post should be marked as sensitive. Adding an attribute, e.g. {hide nudity}, would make this possible, but if the purpose of the change is to make it easier to reuse Mastodon bots, I would also have to have something happen when someone enters {hide} without the attribute, so then the question is which label to add.
Second, even though a post is marked as sensitive it doesn't mean it's hidden to all users. So {hide} wouldn't actually mean hide, which could be confusing.
However, the suggestion is good, so I'm adding it to the todo-list. It won't be a priority, as especially the {show} part would involve a lot of work (to override the default, that means there'd have to be a way to set the default, too, so that's an extra database column to keep track of that).

Huh, there’s no generic reasoning at all? How odd, on mastodon people can hide media for many different reasons, which is usually listed in the content warning label if necessary,
So on bluesky you can ONLY hide nudity? What do you do if you have a lot of followers with eating disorders and need to hid pictures of food to help them avoid triggers?
Or if you like cool bugs but are followed by a lot of arachnophobes?

I mean adding a reason shouldn’t be TOO hard, just at the moment my Remedios Varo bot has a handful of images with bare breasts that may get it into trouble if someone gets persnickety so it would even be an ‘approved’ reason

Bluesky uses what they call "stackable" moderation services. They have a small selection of global moderation settings such as nudity, porn, graphic or suggestive, but you can also (with a TON of knowhow) create your own moderation service, that anyone can subscribe to. For example, I subscribe to a labeler that hides all AI-generated images, and there are a ton of labelers out there, but they're not available in your bluesky settings until you actually find them and subscribe to them.
Also, as a regular user, when you create a bluesky post, you can only choose one of the global labels. So if I upload an image containing porn, I can mark it as porn, but if I upload an image that is AI-generated, I cannot mark it as AI-generated. Only that labeler's moderators can do that.
When generating posts using the API, like BlueBotsDoneQuick does, it appears to be very easy to add any custom labels. However, the user who doesn't want to see food images would still need to find a labeler that hides all food images for them, they can't just add "food" to a moderation list themselves. And of course, since regular users have no "this is a food image" button, food images will only be filtered if they have been seen by that labeler's moderator, and that's assuming such a labeler exists in the first place. But in general, most labels are added by the various moderators out there, not by the users themselves.
I'm guessing a {hide [reason]} would be very easy to add to a bot, just beware that for most people on Bluesky the image wouldn't be hidden at all unless that reason is one of the globals.

that seems unnecessarily complicated and restrictive.
but, yet another reason why I prefer hanging out on Masto.
I don't have to wait for someone else to make a complicated thing for me to block whatever content need or for my friends to be able to warn me about potentially triggering stuff.

Okay, how about this:

If you add {hide} or {label} to a post, it will be marked as "Suggestive". "Label" makes the most sense to me, but "hide" should be an alias.
To add another label, you add a parameter to the tag: {hide suggestive}, {hide nudity}, {hide porn} or {hide graphic}. I don't think I have a practical way of adding other labels than the global ones.
 To override this for a single post, you can add {show}.

that sounds reasonable,
cbts uses hide, so anybody porting over won't have to go through and change things, but also allowing for adding tags means we can more accurately label our content if we need.
a default setting is good too, especially with the {show} override.


Please consider to publish the API reference on Web

Currently, the API reference needs to be generated using doxygen by users himself.
But, It is feels very inconvenient.
Please consider to publish the API reference on Web (GitHub Pages, Intel Web Sites, or other).
Thanks,

Hello @UnaNancyOwen,
I will send your request to the RealSense team for their consideration.
Regards,
Jesus
Intel Customer Support

Hi @UnaNancyOwen
The doxygen output is now published here

@dorodnic It's good news! I've been looking forward to it for a long time. 👍
I will share it with everyone. Thanks,


improve gradle support

and investigate the tips from here:
https://github.com/junit-team/junit5/issues/1355#issuecomment-378001522

gradle support is pretty good now


Add Genio Wi-Fi Dimmable Warm White BC 9W LED GLS Bulb - brightness

Add I002333, which should be nearly identical to an I002334.
Only mode supported for this one.

nice


starting point/new release

this project in combination with apko looks pretty interesting, but I'm not sure about the best point where to start:

dev is fast moving
but latest release is from the beginning of June https://github.com/chainguard-dev/melange/releases
in commit history, there are many red cross commits https://github.com/chainguard-dev/melange/commits/main
from the same person some commits were signed, others weren't

could you give any advice?
Is there a new release on the way? Is starting with code from main a good idea?
Looked also into list milestone, but it seems not be in use

A new release is coming, probably next week.  The red cross commits are because I do not use gitsign as it introduces too much friction with my setup.

sounds great, looking forward to this!

melange 0.2 was shipped since this bug was opened, and melange 0.3 is due out this week.


Reporting a vulnerability

Hello!
I hope you are doing well!
We are a security research team. Our tool automatically detected a vulnerability in this repository. We want to disclose it responsibly.  GitHub has a feature called Private vulnerability reporting, which enables security research to privately disclose a vulnerability. Unfortunately, it is not enabled for this repository.
Can you enable it, so that we can report it?
Thanks in advance!
PS: you can read about how to enable private vulnerability reporting here: https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository

Hey @igibek !
I'm doing well, thank you, what about yourself?
First of all, thank you for reaching out! The effort is already appreciated.
I'll talk with the team about enabling this feature, thanks for letting me know.
In the meanwhile, would you please be so kind to check the following page for us? 🙏🏻
https://www.giantswarm.io/responsible-disclosure
That way you can already report the issue without having to wait for the feature!


Fix gff3 exporter

Merge frederic's branch.

Hi @fredeBio , how can I test the fix works as intended?

Hey Carsten,
I just changed one value in the gff3 file. The start of the genome annotation is now always set to one.
Cheers,
Frederic
----- Original Message -----
From: "Carsten Fortmann-Grote" @.>
To: "mpievolbio-scicomp/rarefan" @.>
Cc: "Frederic Bertels" @.>, "Mention" @.>
Sent: Wednesday, October 4, 2023 5:38:50 PM
Subject: Re: [mpievolbio-scicomp/rarefan] Fix gff3 exporter (Issue #62)
Hi @fredeBio , how can I test the fix works as intended?
--
Reply to this email directly or view it on GitHub:
https://github.com/mpievolbio-scicomp/rarefan/issues/62#issuecomment-1747064934
You are receiving this because you were mentioned.
Message ID: @.***>


Presence app process unexpectedly terminates

At a infrequent period the Presence app process is now longer running!
To Reproduce
hard to define - just start it and leave running for a day or two or more... then it just terminates unannounced and unexpectedly.
Expected behaviour
To remain running all the time and only exit /end when asked to or rebooted.
Further details

OS: [e.g. Win10 20H2]
PresenceLight App Type (Desktop)
PresenceLight Build (Nightly)
PresenceLight Version (<IP_ADDRESS>)

thoughts/ideas on how to help troubleshoot.

I have wired up additional diagnostic logging, please let me know next time this occurs

@sborg-ms is this still happening?

@sborg-ms is this still happening?

hey @sborg-ms can you give the latest nightly a shot and let me know if you still have this issue?

hey @sborg-ms can you give the latest nightly a shot and let me know if you still have this issue?

still having the random terminations and still cannot see a new nightly build when trying to install...

Closing as this is now resolved


System.Configuration is not referenced when building .NET 4.7.2 targeting code

When targeting net472 - code dependent on System.Configuration such as ConfigurationManager does not get properly compiled as System.Configuration is not among the references when compiling project.

Closing as I was using microsoft.netframework.referenceassemblies.net472 1.0.0-alpha-5 NuGet package and obviously this is incorret place to report the issue


Edit command not found

This issue caused by uninstalled extensions.

Install those extensions and it'll work!


Change the primary branch from "master" to "main"

Note from @johnwalicki
For Open-Sentencing-* repos that have completely merged branches, its easy to rename master to main
As of 12-08-20, I see that I can rename the top level and aggregrator repos but the UI and Model repos have open branches. Renaming master to main before those PRs are merged will cause some merge confusion.
I'll rename the first two and work with the teams on the others

This is issue is to address the legacy of racialized slavery and oppression attendant to the term "master". Beyond creating a branch named "main", there are some technical steps that must be taken to change some git (and github) defaults that refer to "master". @johnwalicki can be referred to for more details on those issues.

This is issue is to address the legacy of racialized slavery and oppression attendant to the term "master". Beyond creating a branch named "main", there are some technical steps that must be taken to change some git (and github) defaults that refer to "master". @johnwalicki can be referred to for more details on those issues.


Plan for migrating helm chart?

Whats your plans for migrating the helm chart from opendistro-es ?
Or are there things about it you're unhappy with, so you'd rather "have something else" ?
Can I help - f.ex. by taking a stab at migrating helm chart and https://github.com/opendistro-for-elasticsearch/opendistro-build/pull/693 ? or is opensearch a bit from "being ready for first runnable release" ?

@bbarani I took a stab and was able to spin up OpenSearch cluster using the helm chart. The only issue I am facing is that the cluster is not going green. I will raise a PR of the chart I have created. We can take it forward from there.

@KlavsKlavsen We have merged the initial version of Helm chart via this PR. Please provide your feedback after trying it out. I am closing this issue now, feel free to re-open it if you have any further questions.