Leaderboard

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.

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.

Likely unpopular opinion, but thank you!

I'm out of town right now but let me just state that I totally get the folks that are upset. Honestly, writing blogs is pretty stressful for me as we constantly are working on moving targets and I stress over communicating about things that are still in flux and getting the words right. Tbh, I stress over comms in general. It's nerve wrecking. It's why I am earmarking funds this year to bring someone in to handle this for us. I just didn't want to spend any money on non dev/support resources until we got to 1.0. Again, I get it and I am not gonna make any excuses for it, so if you want to be mad, please direct that anger at me, not my team. They are busting their butts to get this thing polished and rolled out.

I have just recently added a To GPU to the NAS to help with Plex, would be nice to have statistics for it on the main dashboard page. Also might be nice to have a settings page that allowed you to select to use it.

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.

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

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.

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

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

Are there any plans to implement Passkeys?

+1 for Paperless NGX for document management.

Someone copy and pasted from an AI ;-). UPS support is definitely something we want to do, but will likely come after the 1.0 release.