All Activity

I am a purple and gold guy

I got this working by doing a manual install of the docker compose file found here: https://docs.coolercontrol.org/installation/docker.html To manually install it, in TrueNAS go to Apps, Discover Apps, then click the three dots in the top right corner and load Yaml. You can leave the compose as is and it will work. You need to follow the guide below to setup the hardware for it. Specifically for TrueNAS that is running this command in shell and following the prompts: sudo sensors-detect To setup everything prior to that follow the guide here: https://docs.coolercontrol.org/hardware-support.html

The nuance I see is: Guesstimate for initial release, end of 2025. Oh shit, people want a local UI? Guess that's fair but that's a tone of extra work... but here's hoping... (I like many assumed the local UI was a part of the original plan) End of 2025: So it turns out the local UI was a tone of extra work, but we have a better guesstimate, Q1 2026. 1 Week before the end of Q1: Ok beta-beta release, If this goes flawlessly we might just make it... End of Q1: So transitioning X all at once is a massive migration that you can't really test for that well, so we'll have to do it gradually so we can cater for the inevitable fallout. Maybe we can do that over a month? Obviously I'm completely guessing (see, lack of communication) and could be completely wrong, but the general rule I've seen is go off the magnitude of the guesstimate, the longer the period the less accurate it is.

So just to be clear... The initial deadline (end of 2025) got delayed. The self imposed new deadline (Q1 2026) got delayed. The blog post about the delay got delayed (and still not out). The extent of the communication in the meantime on they delay is a random comment buried in a random forum thread. Radio silence on the official comms (reddit, twitter, newsletter). Hard to see how that could be considered acceptable / consistent / reliable. What's the level of goodwill here to assure that even end of April release will be met? The track record so far now is the opposite - the self imposed deadline means nothing.

Yeah they work for a display card. I have a 1080 in mine and its fine. Immich seems to be able to use it for some things. 🤷

Don't get me wrong, the communication is at what i would call a minimum, any less and I'd guess it was abandoned. But, it's a consistent and reliable minimum so far. I check the forum every other day, so would i appreciate more details, definitely. But would i trade anything for that outcome, probably not. So with the minimum communication and knowledge of the software development process patterns, I'm content enough. But that's not an expectation for others I have either. If you'd trade a license for that outcome and the team decide that they should improve communication because of it, hey, that's good too,

The people saying everything is fine have got to be software developers who see this only from one perspective. Hate to break it to them, most people we'd expect soon to pay full license fee to keep the project going aren't, and those are exactly the potential customers we'd lose with this laid back mindset to weak areas of this project. Those won't be beta expectations anymore and there will be a lot to prove to doubters of this project to justify the price. Imho plex & immich was genuinely exciting to watch grow naturally, and backing them early felt like a bargain especially towards stable launch. Was it perfect? No, there were delays too. But none I recall having such communication meltdowns close to stable release. I'll be honest, some of the responses here concern me as much as the delays and comm issues themselves. Some say I knew it's part of the process "when I read Q1 2026 I think Q3 2026" maybe, but not this far into this beta with no updated written delay comms. Others react confused when I try to hold the team to their own deadlines. 'I'm glad they're not communicating, that means time is much better spent on making the software...' really? Good teams do both and I'm not asking for daily extensive blog posts of what and why went wrong, just a sentence update across all hexos communication channels setting new expectations. I recall people on this very forum calling out poor communication back in July and October, and the team acknowledging it and promising to improve. Yet here we are. Traveling or not, I still don't understand how the whole team forgot the most anticipated day of their own project, or couldn't break the news of a delay at least the night before. Now whether April Fools or not, yesterday would've been the first day after stable launch with customers paying $300 for a license, needless to say the most expensive nas os on the market. At this point, if the team still offers a refund option, I'd happily take it.. this just isn't for me anymore

Can I still use the 680 or 1080 as just a display card until I get a compatible card? cheers for the replies. I’ll get an intel NIC and just go SATA drives. ill also look into jellyfin as well. cheers guys

The teams working as hard as they possibly could on this and when participating in a beta delays, bugs and broken updates are to be expected. Personally I would prefer delays over broken updates.

Well @vogam7did you get what you wanted? If you have read these forums there are more than enough accusations of terrible or completely lacking communication. I have been jousting with this windmill since shortly after the initial deployment. I've even talked about to many methods of communication that left each incomplete. I got a similar response it would be looked into. and I can say this was the only answer you could have expected. They are probably still a small team primarily of coders. There had been talk months ago of no marketing team, no support team, and only initial talks of ongoing funding. If we are thinking this communication level is the biggest issue we are going to face before this project stabilizes, we are seriously kidding ourselves. That LTT video is more of a curse than blessing because this project isn't ready for that kind of attention. This team isn't going to acknowledge they are having trouble. They just won't say anything, again. And there is nothing any of the paying beta customers can do about it. Watch and wait or don't watch, what's the difference now. It's to late to change the approach the team took, even if they have found that. And there is now reason to assume that's true. Did they take the right path to this development? Did they build the right team with the right leadership? Well, if you have a better plan then share it. If you don't like this approach how would you fix it? Communication alone means very little. Missing deadlines is a much bigger deal that not mentioning there are problems. And honestly, do you think this would be simple and smooth? Yeah right.

Mil reached out and we got the issue resolved. Turns out I'm an idiot and entered an incredibly old mailadres during purchase. One I did not consider checking for a confirmation.

Not a great look to be honest. And I say this as someone whose already paid and I'm using (even daily driving) Hexos. It's meeting my current needs for Jellyfin and rhe Arrs but only because I needed to go into the truenas interface and use AI help to get out setup. I need frigate and cameras in the next couple of weeks, want to setup VMs, want to host freshRSS etc. Currently not doing it because I want to see what 1.0 brings and was just a matter of a few days away...except now its a month away again. I get wanting to let em cook, but at some point just release already! The market is already quite different from when hexos was first announced. What was the point of emphasising in the last two (not one but two) blog posts that they're pushing back from end of 2025 to Q1 of 2026 if it's going to be delayed again. Literally from the last blog post: "And finally, mark your calendars: HexOS 1.0 is coming in Q1 2026." Except don't mark your calendars because actually we'll just delay again? Again, I say this as a customer whose already paid (so it's not like I'm hoping for them to fail but likewise I do expect to receive the product as advertised and for when advertised when I already paid for it). 1.0 has really got to come out asap and actually have a sizeable scope, many more one-click apps and working out of the box, otherwise truenas on it's own or other solutions are better value.

According to this picture found at https://nascompares.com/2024/10/04/jonsbo-n5-review/ , it seems like he has added the 4 SATA cables and 1 SATA Power cable to the board, no MOLEX. My best bet is that you can either use MOLEX or SATA Power, but don't need both.

You aren't able to add Gluetun to a HexOS app, or a regular TrueNAS app. You have to either install the Dockge app in TrueNAS and then install the Arr apps through Dockge. Or you have to install them as a custom app in TrueNAS. I do hope HexOS will get a good way of routing app networking through a VPN, but I expect it won't happen soon. @Isaac7ski

"Working on a blog post with an update. We had to push back to April due to some issues with our health system that we've been tracking down since February. The plan is to both begin the rollout of HexOS Local and complete the health system upgrades and then release 1.0 by end of April. I was hoping to get a blog up today with all of this information, but it just didn't come together fast enough." -JonP "I am traveling today but I will be working on getting this blog post up tomorrow (April 2nd). I'm also planning to hire someone to take over marketing/comms this year as a full time position." -Jonp Link to discussion

They just posted in another thread. Saying it will be delayed until end or April. Blog post coming tomorrow (April 2nd)

I have the same issue with my APC UPS. From some previous investigation on that topic, I found that the issue might be caused by the Network UPS Tool driver, and a new version might fix the issue. The NUT version in TrueNas is linked to the Debian version, and Debian Trixie upgrades the driver to 2.8.1-5 Should be available in Truenas Halfmoon (26.04)

This one is entirely on me. I am traveling today but I will be working on getting this blog post up tomorrow (April 2nd). I'm also planning to hire someone to take over marketing/comms this year as a full time position.

Oh, that's unfortunate... Thanks for the info, will try

well 4 are connected but is there a way to fix it

Hey, yes unfortunately this seems to be normal for BX APC UPS. Those UPS are not the best ones and the driver does not work very well with them. The problem seems to be that the USB part of the UPS keeps disconnecting and reconnecting every couple of seconds leading to this messages. It's a known problem. My advice would be, if you can still return it, do so and try looking for an Eaton UPS or similar. https://forums.truenas.com/t/back-ups-bx1600m-false-battery-replacement-alerts/50688

Hello there I just hooked up my APC bx750 via USB to my NAS. I was pleasantly surprised to get email notifications from hexos (see attachment), however I am unsure if it is reading the values correctly: - why is it telling me i need a battery replacement, it is brand new - why is it taking me battery is low while also reporting 100% charge Any inputs are welcome 😊

It seems to have happened after the latest HexOS update. This is what the UI looks like here. It's the same for General, Access, Options and Encruption. I've tried to clear the browser cache. I'm running Microsoft Edge.

@Okibblewhite you may know the answer to this question. With the boards in the N5, Do I need both the sata and molex power connected? or would just the sata be enough? I am only using the small 4 bay atm, mainly because my PSU does not have enough plugs for the sata and molex for the main rack. Have not been able to find a clear response anywhere. The NSAcompare article said that either sata or molex would be fine.

Another month, huh? The least you could do is respect the people waiting with some communication ahead of time. Instead it's silence all day on release day and a last-minute delay notice as if it wasn't clear days ago this could happen. You created this self-imposed deadline,, nobody forced it. A delay with advance communication - fine. But the silence until 9 PM? That's just pure disrespect