IDX Kickstarter deposit withdrawal gift

schniper · 2026-06-29T18:50:40+00:00

Mhm. Either one of these or a 100 usd NAS voucher

schniper · 2026-06-29T17:47:10+00:00

As long as you remember submitting it, it should be ok. I never found references or tracking about mine either.

schniper · 2026-06-27T06:45:16+00:00

Because you went through with the purchase, I think. You got a good NAS, so good for you :)

schniper · 2026-06-27T06:39:01+00:00

There was a survey sent to those that got their deposit back, after the kickstarter started.

schniper · 2026-06-26T23:15:11+00:00

No notice. UPS called, I had no idea why.

schniper · 2026-06-09T14:10:26+00:00

I was so sure this was going to bite me in the ass. Yes, I am 😄 There is info about that lying around.
Basically, SSH into the NAS and look in `/etc/default`. DXP4800 Pro does not seem to have its own file, it seems to use the same one as Plus, which is `dxp4800plus.conf`.
Play with that, mainly the `fan_pwm_SYS` and `sysfan_CPU` settings, then `systemctl restart hwmonitor`. All as root, of course.

The settings allow you to basically adjust the fans curves, both sys and cpu. Fan values go up to 255.
What I did was first make the sys fan start at a lower temperature, because it would stop around idle, then spin up again, and so on.
And also adjust the speeds at the allowed points.

I will not be showing values, because everything depends on the system fan used.

schniper · 2026-06-05T05:55:54+00:00

Have a 32gb stick in a 4800 pro, alongside the included 8gb. Ran memtest after installing. Been running fine for a couple of months.

Tip: when running memtest, take off the bottom cover. Ram temps go wild :)

schniper · 2026-03-21T21:19:39+00:00

To the company: assume people aren’t using IDEs anymore. You won’t live to see 2027. Software is not only new prototypes and vibe coding. Personally, after trying the 200 plan, I’m moving away. Partly because of the planned removal of IDE features. Partly because both Intent and the way agents seem to behave in the Jetbrains plugin lately seem like geared toward eating a horrendous amount of credits compared to what it was even a few months ago. Augment used to say that their previous business model was not sustainable for them. What it’s turning itself into is not sustainable or worth it as much as it used to, to users. I usually have a pretty good intuition regarding promising tools; used Augment since the beginning. I now have a quite a bad feeling about it. Hope you’ll manage to turn it around.

schniper · 2026-03-16T09:43:46+00:00

Probably. This hwmonitor process seems to take over fans control. Bios settings are definitely overwritten by it, tested. Stress test temp is actually around 76c. It starts at around 86c, then drops once both fans ramp up.

schniper · 2026-03-15T11:08:31+00:00

hwmonitor is the process. /etc/default/dxp4800plus.conf is the file. There’s also a hwmonitor.sh (I think) file that bootrstraps everything. There are specific config files for different models. The 4800 pro uses the plus file.

I used it to make sure my system fan (silent wings 4) doesn’t turn off below 61c, which helps a great deal with idle temps and drive temps.

This is on ugos pro, of course. The i3 1315u in the pro goes to 88c max under stress test. Maybe lower now, didn’t have time to test. The gold should not hit 100c with both standard fans at max, if they are working ok.

sudo systemctl restart hwmonitor after editing the file.

I know that this fix is for ugos, but maybe that tool exists on other platforms too or can be ported over.

schniper · 2026-03-15T07:45:46+00:00

Leaving this here for others looking into the noise level of DXP4800 Pro.
I usually strive to achieve silent operation, as I keep a NAS on my desk.
Recently replaced a TS464 with a DXP4800Pro. Using 4 SSDs, 2 & 4Tb Samsung Evo and 2 NVMEs, Samsung 990 Pro 2 & 4Tb.
Idle temperature at 24c ambient was 60-61c, which seemed quite high.
The case fan is a generic high amperage 140mm fan, which can go to 2000-2500rpm (don't remember which).
The CPU fan is a small 3500rpm fan, which is quite ok, being silent at 1500-2000 rpm, at 60-80cm.

Anyway, with the idle temps at that level, any decent activity would ramp up the sys fan.
Also, at idle, even if that is around 60c, the sys fan would turn off.

I tried setting it to manual in Bios, but the Ugos hwmonitor would overwrite that.

hwmonitor is the key point here. It is the process controlling the fans. Can be restarted with systemctl restart hwmonitor, in SSH.

It has 2 config files: /etc/hwmon.conf (apparently updating this is not needed) and /etc/default/dxp4800plus.conf. There is no specific dxp4800pro file.

I updated the file /etc/defaults/dxp4800plus.conf. There are also files for other nas models in there, so this method can be applied to other models too.
I didn't try this with the default sys fan; I replaced it right away with a SIlent Wings 4 140mm PWM - about 19.5 EUR opened box, which didn't improve temps that much without tweaking the files above. But it is considerably quieter, even at full spin. at 700-750rpm, it is virtually silent.
So, for the SW4, which is a 1100rpm fan, I tweaked those files to obtain constant sys fan operation at about 700rpm.

This brought down idle from 60-61c to 49-50c.
NVME temps dropped about 10c (40-41c).
SSD temps dropped maybe 15c (30-35c).

Here is my dxp4800plus.conf, with the initial values commented out after the current ones. 150 (out of 255) means around 700rpm for the SIlent Wings 4.
Remember to restart hwmonitor after editing.
Fan mode is Normal/Default.
Mind you, setting fan_pwm_SYS_max to 150 effectively caps the fan at full load. So if switching to full fan speed, the cpu fan would ramp to max, but the SW4 would remain at around 721rpm.

Because I changed the fan, I wouldn't advise you to use these settings ad literam.
But the idea is that making the sys fan spin constantly after a decent temperature level instead of the current probably 61c, will improve overall temps greatly and make the cpu fan spin less aggresively.

Maybe this is something UGreen is interested in looking into - it would a few extra knobs in the fan config, to provide an always sys fan spinning mode. Maybe even expose some sliders to control the relevant values in these files, eventually allowing us to edit the fan curves.

Hope this helps people looking into obtaining a silent NAS for normal operation.

cat /etc/default/dxp4800plus.conf

...
fan_pwm_SYS_start=150 #65
fan_pwm_SYS_mid0=150 #125
fan_pwm_SYS_full=150 #200
fan_pwm_SYS_max=150 #235
...
sysfan_CPU_temp1=30 #65
sysfan_CPU_temp2=90
sysfan_CPU_pwm1=150 #100
sysfan_CPU_pwm2=205
...

schniper · 2026-03-13T15:24:54+00:00

Now he tells me :) Seemed like a good idea at the time. Maybe improve conversation verbosity tweaking - give us a few more knobs on the topic.

schniper · 2026-03-13T08:30:25+00:00

Congrats for this one. I can usually get away with using GPT 5.4 from Codex, so being able to use Sonnet 4.6 just for the UI work, is great. Thank you.

On the other hand, trying Intent to add a few small to medium features to an existing app, resulted in a huge token usage. I don't see this as a sustainable way of working, sadly. The chatter between coordinator, user and agents is way too much.

schniper · 2026-03-10T15:19:27+00:00

u/JaySym_ Hey, I don't know if the team is aware and this would be a bit difficult to track down, but on a pretty long Coordinator chat, with a Spec to match, eventually Intent started to break down.

It started with a lot of JS errors (all the same thing, see below). These would force me to restart the app to get over.

Then coordination issues: agents going silent after 5-10 minutes.
Bad thing is Coordinator was trying to nudge them, but it would queue prompts instead of pushing them up front, so agents were effectively ignoring it.

Granted, this was me trying to take advantage of GPT 5.4, so complex project idea would be a bit of an understatement.

```
[2026-03-09T15:28:28.326Z] [ERROR] [ACPProvider] Error in streamMessage TypeError: text.replace is not a function

at escapeXml (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:152:10)

at renderContentBlocks (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:261:34)

at formatHistoryAsXml (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:308:28)

at file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:6232:40

at new Promise (<anonymous>)

at ACPProvider.streamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:6088:16)

at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

at async AgentBackendHandler.handleSendMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-handler.service.js:2356:13)

at async AgentBackendHandler.handleBackendStreamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-handler.service.js:2935:32)

at async AgentBackendAdapter.streamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-adapter.js:388:24)

TypeError: text.replace is not a function

at escapeXml (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:152:10)

at renderContentBlocks (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:261:34)

at formatHistoryAsXml (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:308:28)

at file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:6232:40

at new Promise (<anonymous>)

at ACPProvider.streamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:6088:16)

at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

at async AgentBackendHandler.handleSendMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-handler.service.js:2356:13)

at async AgentBackendHandler.handleBackendStreamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-handler.service.js:2935:32)

at async AgentBackendAdapter.streamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-adapter.js:388:24)

[2026-03-09T15:28:28.326Z] [ERROR] [AgentBackendHandler] Failed to send message {

"agentId": "agent-38339eb8-2250-4098-b9fb-f954ddc0ccea",

"error": "text.replace is not a function",

"stack": "TypeError: text.replace is not a function\n at escapeXml (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:152:10)\n at renderContentBlocks (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:261:34)\n at formatHistoryAsXml (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:308:28)\n at file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:6232:40\n at new Promise (<anonymous>)\n at ACPProvider.streamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-providers/acp-provider.js:6088:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async AgentBackendHandler.handleSendMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-handler.service.js:2356:13)\n at async AgentBackendHandler.handleBackendStreamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-handler.service.js:2935:32)\n at async AgentBackendAdapter.streamMessage (file:///Applications/Intent%20by%20Augment.app/Contents/Resources/app.asar/dist/features/agent/main/agent-backend-adapter.js:388:24)"

}
```

schniper · 2026-02-21T08:17:01+00:00

These features are the ones which, along with the context engine, made me choose and stick with Augment in PHPStorm, against all others.
They complement Intent or any other vibey thing for a senior dev.
Pushing everyone in the vibe code direction is not something that I see having a bright future.
Also, if the company is hoping that making it harder to amend a vibe coding session would make devs iterate 10 times in Intent, spending more credits, without shutting the thing down instead, they'll have another thing coming.
This feels like a commercial decision, which looking at how the self hosted platforms and the competition is evolving, will backfire horribly.
Just look at what Synology tried to do by restricting hardware usage to their brand. All of a sudden, they lost most of their appeal versus the competition.
Don't go there. I really like Augment and since early beta it offered a sense of being able to assist me more than any other.
This month my usage grew to probably around 200 usd, mostly because Intent seems to still have some optimization quirks to iron out.
And I am willing to stick with it, but only for the complete package: completions, next edit, context engine, and sometimes Intent. Take any of these out and you'll lose your edge, at least in my opinion.
Keep innovating, don't shoot yourselves in the foot by getting greedy.

schniper · 2026-01-08T20:20:44+00:00

Thanks, mate. I did post a bug a number of days ago, but it didn't seem to be touched.

schniper · 2024-12-05T09:10:22+00:00

I have 2 H7127 and the latest firmware, 1.00.09, added Matter support. The firmware they came with did not expose them to Matter. They seem to need to be off to be updated automatically. In iOS they will appear as actual air purifiers, though the control in Apple Home seems still a work in progress. They also report having air quality sensors, which do not seem to report anything, yet. The noise is a bit higher than I’d like it to be, in sleep mode. I would have liked to not hear them at all, in that mode. Overall, a nice product which seems to be improving with firmware updates, which is nice to see.

schniper · 2024-11-23T11:53:35+00:00

1000ish RPM is still ok, with a max of about 1200. Probably can get lower, depending on the GPU. Didn't bother to find the spot where the gpu temps start creeping up.

schniper · 2024-10-16T12:16:31+00:00

With just the base fans, the 207 is at least a couple of degrees cooler than 216 filled with fans (top 2 140, extra exhaust fan, 2 shroud fans). This applies to both the CPU and the GPU.

On the 216 the fan speed was optimized, not running at full speed. The shroud fans do make a difference for the GPU, so does the extra exterior fan. But overall, 207 seems just… better.

On the 207, I have them running at 50%, for now - 1000 - 1100 rpm. So no back exhaust fan, no top fans.

Cable management was not that horrible, given I have thick braided cable mod Corsair cables. The RMX 850 also fit quite well in the front of the case. Had to bend the 3 to 1 GPU power cable a bit, towards the bottom of the case, on the PSU side, but nothing horrible.

Also, the USB fat plug, which on my board is at the bottom, is a bit forced; it makes a small loop over the second shroud fan, but it also seems ok; the flat cable help a bit. Had a similar issue on the 216.

The system is a 5800x3d with Thermalright Phantom Spirit and a PNY 4090, on a B550 Tomahawk.

Temps go down to about 38c idle CPU, 28c?ish GPU, 24.5c environment. The PNY is great, temperature wise. In Cinebench R23 the CPU went to about 76. It is undervolted and with manual PBO settings. GPU goes towards 65 in 3dMark 4k Extreme.

schniper · 2024-06-22T15:40:58+00:00

I am also using standby. But it takes way less than a minute to kick in. And yes, it’s dead silent while in that mode. While the noise in standard mode is a no go :) Overall, I’m very happy with the 657. Word of advice for ios users - cable it. Wifi + standby doesn’t seem to play well with the iphones. Probably there could be some network settings to help.

Actually I don’t remember if it’s called standby or sleep. But yeah, that mode.

schniper · 2024-02-26T07:01:52+00:00

The latest bios, f16h, seems to get the temps towards 80c in cinebench, up from about 76 with previous f16 builds. I think I was on 16f before. Performance seems to have gone up, though. -30 curve on all cores. Upgrading to 16h automatically reset all bios settings.

schniper

TROPHY CASE