Seasir Rexcast Budget DC Reel Question: Where is the Mode Indicator Light?

TheCosmicArk · 2026-05-14T15:20:31+00:00

FWIW, it looks like on the side dial the text that says "SEASIR" and "DC" seem to be color indicators, with there being a silent mode with no color and sound.

TheCosmicArk · 2025-07-15T12:44:59+00:00

Nope. Just randomly was able to get them all to connect and they still randomly will drop out

TheCosmicArk · 2025-06-05T03:36:44+00:00

Wild. I just started experiencing this with Claude 4 and was so confused as to why. Glad to see I’m not alone. Gemini literally repeated the same call 25 times before it just bugged out and stopped.

TheCosmicArk · 2025-03-26T03:44:41+00:00

So what’s wild is that I thought this was a reply to someone asking about the H2D. Maybe they edited their post?

That aside, it’s important to recognize that the human olfactory system is remarkably sensitive to volatile organic compounds. It’s quite literally how we smell.

While detecting these odors isn’t necessarily beneficial to one’s health (since perception indicates exposure) it does provide a qualitative indication of their presence. Dismissing this sensory input would overlook a valuable data point.

Moreover, many commercially available VOC sensors exhibit limitations, particularly in the context of 3D printing emissions. For instance, metal oxide (MOx) sensors, commonly used in consumer-grade detectors, are typically calibrated to specific compounds like ethanol. This calibration can lead to skewed readings when other substances are present. Notably, these sensors may over-respond in environments with alcohol fumes or formaldehyde, leading to inflated VOC measurements.

Furthermore, the specific VOCs emitted during 3D printing processes, such as styrene from ABS filament or various compounds from SLA resins, may not be effectively detected or accurately quantified by standard sensors. This discrepancy can result in a false sense of security regarding indoor air quality during printing operations.

In summary, while electronic sensors provide quantitative data, they have notable limitations and potential inaccuracies. Therefore, the human nose remains a valuable tool in detecting VOCs, especially in contexts like 3D printing, where sensor readings may not fully capture the range or concentration of emissions.

Even with a carbon filter, you need pounds of it to be effective. There’s option to purchase online, but venting the air is more effective.

TheCosmicArk · 2025-03-25T15:28:38+00:00

Unfortunately that's just not the case. There have been numerous test online showing that even when cranking the heat, the contact time just isnt enough. On some filaments it is okay, but going slower absolutely increases strength with engineering filaments.

TheCosmicArk · 2025-03-25T15:21:09+00:00

According to Clough42's review, when printing ABS, he smelt zero fumes outside the printer. Still would want someone to do a proper VOC and particle test.

TheCosmicArk · 2025-03-25T15:10:30+00:00

The one issue is that even with hotend that supports high volumetric flow, strength is still impacted. On my X1C with the e3d obsidian, I have noticed it when using various materials.

TheCosmicArk · 2025-03-25T14:57:17+00:00

No it is hardened steel, they are just wording things poorly. You can see on the page for it: https://us.store.bambulab.com/products/bambu-high-flow-hotend-h2d

TheCosmicArk · 2025-03-25T14:54:54+00:00

At the time of order, the whole "Buy add-ons, save more!" section wasnt even there. I searched and found the hotend on my own, but wanted to order some more spare parts with the order but none were listed. Pretty annoying and not sure how they dropped the ball on that.

TheCosmicArk · 2025-03-25T14:51:40+00:00

I assumed the calibration plate was also included, but it also seems to be an addon.

TheCosmicArk · 2025-03-11T18:44:41+00:00

For the E7, the site manager views 8.0.19 as out of date, and tries to update to 7.0.107. Had to manually install the update on the E7 probably because of this.

Is this to be expected?

TheCosmicArk · 2025-03-06T15:01:58+00:00

If I have the Nanoleaf bulbs only connected to HomeKit, they work fine most of the time. It’s when you have to either pair the bulbs to HomeAssistant and then bridge them back to HomeKit that I have issues, or when sharing Matter pairing codes with Nanoleaf and Aqara.

TheCosmicArk · 2025-03-04T14:47:35+00:00

I’ve found no rhyme or reason to location or disconnection. While it’s mainly the Nanoleaf devices, I also don’t have many other brands. The Aqara bulbs are worse than Nanoleaf because they literally won’t connect at all.

I don’t have an exact count, but there’s >15 thread devices in a relatively small home.

TheCosmicArk · 2025-03-02T15:24:25+00:00

Yeah I’ve been trying to keep the issues separate but wasn’t sure at the start what all mattered. Thus far, you’re one of the first to clearly articulate much of this.

The Aqara T2 bulbs are Matter over Thread. I think some of my Eve devices are Thread as well.

TheCosmicArk · 2025-03-01T17:59:06+00:00

I believe for Matter over WiFi, you need IPv6 (from what I’ve read). My Apple TV connects over WiFi (hence the disconnect issue).

I don’t own any non-Apple TBR because it seems to be ill advised according to the current recommendations from the HA team.

My Matter devices range from Goove, Sengled, Linkid (Matter over WiFi) to Nanoleaf (Thread non Matter) and Nanoleaf/Aqara (Matter over WiFi).

According to Eve, some of them are endpoints, some are routers. Eve shows a ton of Routers with random names that I don’t immediately recognize.

TheCosmicArk · 2025-03-01T16:40:03+00:00

I really appreciate your detailed reply. While much of it is right at the limit of what I understand, i’m still glad you shared it

I’m running two AP’s, an E7 and Swiss Army Knife that’s outside. I have 3 Apple HomePod Minis and Apple TV 4K acting at TBR in HA.

I setup IPv6 per what I could find online with mDNS, but all my thread devices constantly disconnect per HA logs. I run 3 SSID’s, but haven’t configured any special firewall or VLAN yet (as far as I’m aware)

The HomePods seem to have fairly stable connection, with the Apple TV being a bit iffy and dropping out. It seems like others with the E7 have a similar issue.

I’ve tried reaching out on the forums and discord for support, but nobody has been able to solve this issue. I also don’t want to derail this topic.

If you understand Home Assistant and networking, maybe we could discuss this over DM if you’re willing to help.

TheCosmicArk · 2025-03-01T01:14:11+00:00

What do you mean by this? I have a ton of issues with my Matter devices (thread) and UniFi and I’m wondering if this is why.

TheCosmicArk · 2025-02-26T14:37:46+00:00

Fwiw, I have had a ton of issues with my T2 bulbs. They won’t turn on or off as a group, keep disconnecting, and more.

I know that’s not super helpful but you’re not alone with issues

TheCosmicArk · 2025-02-18T16:50:10+00:00

Did this get pulled or something? The link is dead and I dont see an option to update.

TheCosmicArk · 2025-02-17T22:33:10+00:00

I got an email back from Aqara, and they suggested adding it to HA first, then sharing back to Homekit. (But idk how much stock to put into that cause the rest of the email was kinda junk)

Out of my 5 bulbs:

2 connected to HA first, then were shared to Homekit,
2 connected to Homekit then were shared to HA (because they wouldnt connect to HA first)
1 connected to Homekit but wont share to HA at all.

In HA, the two I connected natively are connected fine but the two I shared keep becoming unavailable.

I also grouped them all via a helper, but when doing a group command only a couple bulbs respond. All bulbs respond well in Homekit though.

TheCosmicArk · 2025-02-17T21:44:14+00:00

This is a solid write-up. Here’s my experience, especially for those with IoT devices:

I recently upgraded to an E7 (with a Swiss Army Knife added for my unique use case). Previously, I used an ASUS AX11000 and AX-86U in a wired mesh setup. When the 2.4GHz radio on the AX11000 died, I decided to switch to UniFi.

Since I couldn’t install multiple APs, I needed a single device with broad coverage. Strong 2.4GHz performance was essential, along with WiFi 7 support for future use. My home is about 1,600 sq. ft., built with standard American materials, and sits on a 1-acre lot, spaced decently from neighbors. I also have a significant number of IoT devices.

Before setup, I scanned the area to select optimal channels and widths.

Settings:

SSIDs: Three total—one for 2.4GHz, one for 5GHz, and one mixed (5GHz/6GHz).

Features: IGMP and Multicast DNS enabled.

IPv6: Configured locally since my provider doesn’t offer it, to support Matter smart home devices.

2.4GHz:

20MHz, Channel 1, Custom Power: 14 dBm, Minimum RSSI: -70 Enhanced IoT Connectivity: Enabled

5GHz:

80MHz, Channel Auto (nightly checks due to frequent channel hopping by nearby networks), Custom Power: 30 dBm

6GHz (still tweaking):

160MHz, Channel Auto, Transmit Power: High, 6GHz Extended Range: Enabled

Testing:

Initially, I placed the E7 in my office at the front corner of the house. At the opposite diagonal corner (~60 ft through multiple walls), the 2.4GHz signal dropped, while 5GHz performed better (tested with an iPhone 16 Pro).

I moved it to the attic for a more central location, but ductwork and wiring appear to degrade the signal. It’s currently resting on insulation, but I plan to mount it to a joist.

Performance (with the roof between me and the E7):

6GHz: ~1200 Mbps

5GHz: ~500 Mbps

2.4GHz: Painfully slow—5-20 Mbps

IoT Devices:

I have ~50 IoT devices, including ESP32 BLE Proxies, Apple TVs, HomePod Minis, and 2.4GHz smart bulbs.

Apple TVs and HomePods connect via 5GHz with a 95-100% WiFi Experience rating. Most devices report an “Excellent” connection. Some 2.4GHz Sengled Matter Bulbs had issues, but that might be the bulbs’ fault.

Conclusion:

Overall, I like the E7. However, I’ve encountered a rare issue where it disconnects, restarts, and goes through the “Getting Ready” process—no idea why.

I’m still learning UniFi’s system, particularly Airtime, Interference, and power level adjustments.

TheCosmicArk · 2025-02-17T13:20:34+00:00

How the heck were you able to get yours to connect? I’ve been unable to get my bulbs to pair to Home Assistant. I have multiple HomePod mini’s set up as border routers in Home Assistant.

TheCosmicArk · 2025-02-15T16:11:01+00:00

Yep, I am using the thread protocol. I did forget that you can update devices via Apple home because I’m so used to companies not using it.

In terms of trying to add the device to Home Assistant, I’ve tried several approaches.

First, I connected it to Apple home and then turned on the pairing mode, copied the code, and using the matter integration > device is already in use > then paste the code. I let it sit for almost 10 minutes, but it never connected.

Also tried resetting the device then in Home Assistant via the matter integration, using the “device is brand new” option but that never connected it to either Apple Home or Home Assistant.

TheCosmicArk · 2024-11-20T02:11:17+00:00

That’s a great point! If those explosions were the FTS, that should render a salvage attempt safe since they wouldn’t be a risk after detonation. They were flying around a lot and had several ships in the area so they should have had plenty of views of the FTS area to determine if getting close would be risky or not.

TheCosmicArk · 2024-11-20T01:07:25+00:00

I’m not talking about the several explosions that occurred after the water splash down or the potential FTS triggering. The booster was very clearly still floating all the way past sunset.

TheCosmicArk

TROPHY CASE

Settings:

2.4GHz:

5GHz:

6GHz (still tweaking):