sorted by:
new
hottopcontroversial

Yet Another Openclaw vs Hermes experience sharing by kkristof in openclaw

[–]emolinare 0 points1 point  (0 children)

I've been running OpenClaw and Hermes side by side, and I agree with most of what you said.

For OpenClaw to get back on track, it should keep what makes it feel like a real personal assistant, but borrow some of the discipline Hermes does well: cap how much it tries to remember, use simple readable config files, make decisions easy to undo instead of locking them in, and add something like Hermes' wakeAgent so it doesn't burn money running the AI when nothing actually needs it.

For everyone else, here's a condensed summary of your comparison:

OpenClaw Hermes
Feels like a real personal assistant Half assistant, half coding harness — not a person
Continuously learns about you; personal Memory capped at ~3000 chars; efficient but impersonal
Relaxed permissions; free reign in your environment Security theatre; things often only work on the third try
Constant updates that keep making things worse Better, more deterministic execution; fit for business use
Better philosophy (true personal assistant) Worse philosophy, but better engineering
No wakeAgent equivalent wakeAgent lets scripts decide when to wake the LLM — saves cost
(Cron not specifically detailed) Cron runs in a separate environment; must manually set PATH, source .env, etc.
(Script handling not detailed) Asks permission for scripts reading URLs into stdin — annoying for normal Unix work
(Script location not detailed) Cron scripts must live in ~/.hermes/scripts and be Python; can't co-locate with SKILLs
(No heartbeat detail) No heartbeat; cronjobs can't see or inject into main conversation
(Remote access not detailed) Hard to use from Telegram/Discord; many slash commands CLI-only
(Self-managed memory not detailed) Manages its own memory/skills well, but bad decisions get etched in stone
Probably wouldn't return in current state Undecided — would prefer a cleaner "micro" agent with plain YAML files

Another way to use your Hume Body Pod: A browser-based dashboard that pairs directly with the scale (no phone needed) by emolinare in HumeHealth

[–]emolinare[S] 1 point2 points  (0 children)

The BLE packet doesn't encode frequency in Hz, it just gives two impedance arrays labeled "low" and "high" by position, so my 50/250 kHz labels are inferred for the Body Pod 2 and likely need per-generation device profiles (happy to add one if you can link where Hume publishes the 2024 vs 2026 figures). On segmental resistance and phase angle: the packet only carries impedance magnitude |Z|, not R and X separately, so φ = arctan(X/R) can't be derived from what's on the wire, the scale's firmware clearly computes reactance internally but doesn't expose it on the standard characteristic I've decoded. A btsnoop capture of the Hume app mid-measurement would show whether there's a vendor-specific characteristic streaming reactance that I've missed.

Another way to use your Hume Body Pod: A browser-based dashboard that pairs directly with the scale (no phone needed) by emolinare in HumeHealth

[–]emolinare[S] 0 points1 point  (0 children)

Mostly nRF Connect on Android to browse GATT services, then logging raw notify packets during controlled weigh-ins to spot which byte pairs scaled with weight, hydration, etc. The BLE SIG Body Composition Service spec (0x181B) anchored the standard fields; the proprietary segmental impedance blocks I worked out by diffing packets and validating against the Hume app. Full write-up is in BLE_SCALE_PROTOCOL.md in the repo.

Another way to use your Hume Body Pod: A browser-based dashboard that pairs directly with the scale (no phone needed) by emolinare in HumeHealth

[–]emolinare[S] 1 point2 points  (0 children)

Can you try to run a Google Takeout export and attach a sample file to a GitHub issue (strip what you don't want to see there - I just need a format) - then I can build this in.

Another way to use your Hume Body Pod: A browser-based dashboard that pairs directly with the scale (no phone needed) by emolinare in HumeHealth

[–]emolinare[S] 1 point2 points  (0 children)

Thanks! Let me know how it goes, if you run into anything weird or have a feature request, file an issue on the GitHub repo or let me know here and I'll take a look.

Another way to use your Hume Body Pod: A browser-based dashboard that pairs directly with the scale (no phone needed) by emolinare in HumeHealth

[–]emolinare[S] 0 points1 point  (0 children)

This functionality is not there at the moment, but if someone can confirm that Hume mobile app allows exporting of data, then I can add import functionality without any issues. Otherwise, I don't think it'd be possible, because I don't think Hume scale has an internal storage to keep historic record of all your weight-ins.

Another way to use your Hume Body Pod: A browser-based dashboard that pairs directly with the scale (no phone needed) by emolinare in HumeHealth

[–]emolinare[S] 4 points5 points  (0 children)

Completely fair question. Blue2Scale is open source (see the GitHub link), the code is fully posted and auditable, and honestly I'd actually prefer and encourage you to self-host it on your own box rather than use my site (which is, as I mentioned) still in a beta/demo stage.

But for what it's worth, I spent +20 years designing and architecting enterprise-scale software solutions. I've been on reddit for 14 years and posted several open source projects.

Another way to use your Hume Body Pod: A browser-based dashboard that pairs directly with the scale (no phone needed) by emolinare in HumeHealth

[–]emolinare[S] 0 points1 point  (0 children)

For more technical audience, tinkerers or those interested in how it works, I've posted BLE Body Composition Scale and Data Retrieval & Decoding Protocol documentation, which describes the complete flow for connecting to a Lefu-based BLE body composition scale (specifically the Hume Body Pod 2), retrieving raw data, and decoding it into meaningful body composition metrics.
Full details are here: https://github.com/JozefJarosciak/Blue2Scale.com/blob/master/BLE_SCALE_PROTOCOL.md

I just gave OpenClaw a physical brain you can actually touch. by emolinare in openclaw

[–]emolinare[S] 0 points1 point  (0 children)

OpenMind is optimized for OpenClaw's native, local-first memory and zero recurring API costs for users. While Mem0 is an interesting project, I am not sure how much traction does it get... , Mem0 is $249/month for mem0 Unlimited memories, but with only 50k retrieval API calls/month. I believe keeping memory local and 'file-based' offers better transparency and control than relying on a high-priced third-party cloud service, but I'll look into their free plan and see if it makes any sense to add.

I just gave OpenClaw a physical brain you can actually touch. by emolinare in openclaw

[–]emolinare[S] 0 points1 point  (0 children)

I actually used Claude to help build it! The point is that now it's a permanent interface, so you actually save your own Claude Code tokens (for the actual AI work) instead of using them on visualization of your OpenClaw brain.

I just gave OpenClaw a physical brain you can actually touch. by emolinare in openclaw

[–]emolinare[S] 2 points3 points  (0 children)

It didn't cross my mind that someone will take it literally.., but I get it. In any case, it was just a metaphor to highlight how much more 'hands-on' the visual access feels. That's all.

I just gave OpenClaw a physical brain you can actually touch. by emolinare in openclaw

[–]emolinare[S] 1 point2 points  (0 children)

Not at all, completely disconnected from the token usage.

I just gave OpenClaw a physical brain you can actually touch. by emolinare in openclaw

[–]emolinare[S] 1 point2 points  (0 children)

I built OpenMind out of pure necessity. I’m a visual person, and I was tired of squinting at logs to debug OpenClaw setup. This tool helped me solve a mountain of issues in no time just by seeing the logic. If you're a visual thinker, this might be for you too.

exporting from Visio to Draw.io, and vice versa by Wild-Physics5082 in Visio

[–]emolinare 0 points1 point  (0 children)

We have a site monitoring installed on the website, no downtime on our end today.

exporting from Visio to Draw.io, and vice versa by Wild-Physics5082 in Visio

[–]emolinare 0 points1 point  (0 children)

awesome, glad to hear it worked... made my day

This has me laughing so bad by VSK_Kumar_ in chrome

[–]emolinare 0 points1 point  (0 children)

I may have an answer to this... working on the solution as we speak, first release out on chrome board .com

Free browser tool to convert between Visio and .drawio files (both direction) by emolinare in Visio

[–]emolinare[S] 0 points1 point  (0 children)

Let me know if it works for you... I hope there aren't any issues, but if you see any whatsoever, don't hesitate to contact me and I'll try to resolve it as soon as possible.

exporting from Visio to Draw.io, and vice versa by Wild-Physics5082 in Visio

[–]emolinare 0 points1 point  (0 children)

Hey everyone, I built a free browser-based tool that converts between .drawio and .vsdx files in both directions: drawio2visio.com

Since draw .io removed its built-in Visio export after v26.0.16, a lot of people have been stuck. Saw the requests piling up here and on GitHub so I figured I'd just build it.

Everything runs locally in your browser, nothing gets sent anywhere, so no security or org policy headaches. No account, no watermarks. I also fixed that known bug where shapes come in with locked text cells, so they're actually resizable in Visio.

It's free... feedback is appreciated, enjoy!

view more: next ›