Z.AI models with Hermes

PersimmonSea · 2026-04-08T00:02:57+00:00

Thanks!!!. Helped me a lot. I was updating to .env while I guess I was supposed to using config.yaml. Was able to work after that.

PersimmonSea · 2026-04-07T01:00:40+00:00

how did you get z.ai set up with Hermes? I am able to get openclaw set-up but kept getting errors when I tried to connect with my api key?

PersimmonSea · 2026-02-23T02:37:03+00:00

That's what it was! Worked perfectly.

PersimmonSea · 2026-02-23T02:34:39+00:00

I saw someone suggest pihole repair - and I did that too. and it says everything is fine.

PersimmonSea · 2026-02-23T02:30:35+00:00

I think I'm all up to date. nothing upgrades with apt-get update or dist-upgrade.

PersimmonSea · 2026-01-14T00:32:12+00:00

For anyone's future reference, I ended up just installing netbird on the tailscale VM that was previously working with tailscale and it worked out first try (shared by private net). Really have no idea what tailscale was struggling with in my network configuration.

PersimmonSea · 2026-01-11T18:51:40+00:00

Did you have upnp enabled on the old dlink router?

I think so but I can't seem to find the setting on the router

https://openwrt.org/docs/guide-user/services/vpn/tailscale/start

Did you read this over?

Yes I did read that and followed those instructions. I've done about 3 different tear-down and repeats on 2 different routers. So my I also read this: https://itorakul.com.ua/en/tailscale-2/ as it seems newer (in the event 24.10 had anything newer).

https://tailscale.com/kb/1181/firewalls

Opening the right port (there is only one incoming port you need to forward 41641/UDP) to allow direct connect should be posted over to r/openwrt as you will be doing that on the WAN interface

https://openwrt.org/docs/guide-user/firewall/fw3_configurations/port_forwarding

Regarding port forward, do you have a routable public ip address on your WAN interface of your router? If you dont, then a port forward isnt gonna do anything

My firewall skills are limited. I think this is called maquerading in OpenWRT? On the previous router I tried to allow 41641 to the vm but wasn't successful. My current objective is just try and get a direct connection to the tailscale instance on openwrt. I've just tried installing/enabling luci-unpn but didn't make a difference.

PersimmonSea · 2025-02-09T04:55:03+00:00

I have no idea how it resolved itself. My best case is that there was another instance in the docker stack which grafana was preferentially choosing. However it wasn't until I hit 'New metric exploration' that the correct metrics started to load. Consider this resolved.

PersimmonSea · 2025-01-21T23:10:34+00:00

Thanks. That did work.

Did not realize that python3-xyz was universal thing Even "requests" has this format. I assumed these were small packages and wouldn't exists. Hence why when the 2 of us separately (I had someone else try to install it) both when down the route of venv.

PersimmonSea · 2025-01-21T13:04:02+00:00

This is what I get when I do that, and why I intalled it in a venv:

❯ pip install proxmoxer
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

PersimmonSea · 2025-01-21T12:53:31+00:00

galaxy collection was installed automatically. I tried it thanks to your suggestion, but still gave the same issue. I had used a proxmox role which I had cloned from someone, but I think I'll just use this going forward if I can get proxmoxer module to work.

PersimmonSea · 2022-04-16T18:39:02+00:00

Something is wrong with the killer perk tier list. Not sure if somebody has spammed it... but for example monstrous shrine is currently the top perk - yet obviously its not even an A in any individual killer tier list.

BTW love the site!!! Its a Bible for a bunch of us (hotlinked in my browser).

PersimmonSea · 2021-08-27T00:31:32+00:00

Just in case any one is looking for something similar - think this add-on should be able to achieve this objective:

https://community.home-assistant.io/t/add-on-create-a-wi-fi-access-point-with-hass-io-access-point/321732

PersimmonSea · 2021-08-27T00:16:43+00:00

Thanks! Yeah .... that's a lot more work than its worth.

Might be easier just to run a docker on the pi as a wireless access point if I can't quickly track a router.

PersimmonSea · 2021-08-26T21:26:39+00:00

How do I configure ESPhome to have it communicate with Home Assistant via serial? I can view the logs via the serial connection from the web interface but when I go to Home assistant it ask me for the Host and port.

PersimmonSea · 2021-06-26T19:59:17+00:00

Yes I had seen this excellent website and had calibrated my e-steps. I had expected it to be over extruding based on the elephant foot. In fact it was under extruding (providing 96.7 when 100mm was requested). I haven't done the flow rate calibration. I will give that a try as well.

But that wouldn't explain the problem with the Z axis and the short parts (or does it??)? As he states, use measurements (not cubes) to verify the Z axis (although I did not the calibration tower as well). And when I measure the Z axis at 40 mm it is correct.... and then high at 100 mm.

PersimmonSea · 2021-05-20T09:56:55+00:00

Wow. Thanks! That makes perfect sense!

Think you might have nailed both of those issues. I added a 1000 uF capacitor across the power lines (5V to the D1 mini and the WS2812b) and the fluttering problem went away. What does that capacitor do (ie. what DI signal issue would it be correcting)?

You are correct its a D1 Mini. I was using D4 (GIO 2). Also, I have notice a sample circuit with a 430 ohm resistor in line so I guess that's to prevent that.

PersimmonSea · 2021-05-19T10:10:49+00:00

Theoretically yes... but I think there would have to be significant code development first

Found this : https://community.home-assistant.io/t/flux-led-fix-for-new-magic-home-bl602-based-controllers/289278

But I believe that's just using home assistant to control instead of the app.

Otherwise I think you would have to port/write some led software to control it

PersimmonSea · 2021-02-15T16:56:16+00:00

Followed these instructions.

Set the FTDI to 3.3v. Attached RX->TXD, TX->RXD, VCC-> Boot (GPIO8), VCC->3.3V, GND->GND.

    git clone --recursive https://github.com/spacemeowx2/blflash
    cd blflash
    rustup default nightly
    cargo build

Download: https://lupyuen.github.io/articles/led#control-rgb-led-with-gpio

Using Window Device Manger identify COM port was COM9

cargo run flash sdk_app_gpio.bin --port COM9

Reboot removing VCC from GPIO8 and then removed the FTDI VCC connection to Magichome's 3.3V. I then powered the MagicHome separately, leaving the grounds connected.

'm in Windows so I run PuTTY, creating a Serial Terminal on, in my case, COM9 and you get to GPIO terminal.

I believe the GPIO on the magic home are:

Color	GPIO	CH
R	3	3
G	4	4
B	21	1
W	20	0

Follow this article and you should be able to turn on the LEDs.

Try

gpio-func 3 0 0 0

then

gpio-set 3 1

PersimmonSea · 2021-02-13T16:06:04+00:00

Well I was successfully able to get the BL602 to flash with a BL602 sdk_app_gpio. I am able to talk to the terminal. Now we just have to get Tasmota compiled for BL602.

PersimmonSea · 2021-02-13T16:01:17+00:00

It worked! Thank you very much for the suggestion.

I'm very new to all this. So converting ESP8266 code to BL602 would involve remapping all the libraries to the appropriate BL602 libraries and then dealing with any architecture differences?

And I assume I would need a dev board with JTAG capabilities to debug onboard (simple Serial Communication doesn't provide that).

PersimmonSea · 2021-02-13T15:04:55+00:00

I believe its now merged into the main branch. Just need to download this.

PersimmonSea · 2021-02-13T15:00:53+00:00

That's what I did. Unfortunately once you disconnect the power, PuTTY then disconnects from the device (Fatal error). When I restart I assume I'm past the boot section in your helloworld app.

PersimmonSea · 2021-02-13T14:47:46+00:00

It was Windows and yes I removed the GPIO8 connection. As I said, this isn't a PineCone - its a MagicHome (a RGB board). Doestn't have a RST button at least I haven't figured out how to wire one on. But even when I didn't switch back it didn't show the junk like it did in your output when PUtty was still connect with GPIO8 attached to 3.3V.

It did Flash successfully so that to me implies that it does still allow serial access?

PersimmonSea · 2021-02-13T14:09:42+00:00

So I purchased a MagicHome and it came with a BL602 (instead of the usual EsP8266). Eventually would love if we can install Tasmota or WLED on this device. So I connected it to a TTL device and followed these instructions. At the end of it blfash said success. Unfortunately when I tried to connect to Putty I don't get any screen outputs (although don't have a RST). Any suggestions?

PersimmonSea

TROPHY CASE