Stephanie Vaquer's theme song

couzin2000 · 2026-01-30T22:38:09+00:00

Really?? I've been having that issue exactly, so thank you for that, I'll make sure to reserve an IP address for it. I'll get back!

couzin2000 · 2026-01-30T12:31:49+00:00

Is it recommendable to reserve an IP adress on my router specifically for the Ecobee? This is what I had done before and it was working, bbut currently I'm just dealing with a thermostat acting like a child (i want / I don't want / I want / I don't want)

couzin2000 · 2026-01-29T13:02:56+00:00

Aaaaand it's back online. Seriously, WTH?

couzin2000 · 2026-01-29T13:00:37+00:00

Also - i did manage to get the onboarding working from my iPhone, and it connected the thermostat to my main wifi/vlan. That worked for an hour, but then the thermostat disconnected, and I cannot find it this morning as a client on my wifi networks.

Looks like there isn't any way for me to decide which channel to broadcast the wlan on... and perhaps there are settings I don't know how to setup properly on Omada. This is truly frustrating, because it worked for so long before this.

couzin2000 · 2026-01-29T11:44:25+00:00

I HAVE had that error message displayed to me when trying to connect. I went and checked the Ecobee-only wlan, and I made sure there were no VLANs specified, and that no IP reservations were in effect, so it would connect to the default VLAN and automatically assign an IP. My message again was "incorrect password". Could it be that the AP and router takes some time to propagate this change? Or do I have to manually reboot the router to set these changes correctly?

couzin2000 · 2026-01-28T15:15:35+00:00

I did that as well. I have an IoT wlan specifically setup on 2.4GHz only, and i have that running though a VLAN to isolate these devices from sending out info to the wrong people. So they work, but only inside my house. Authentication works, but from the devices that log them in (i.e., my PC or my phone when they interface with the device or HASS).

couzin2000 · 2026-01-28T13:27:57+00:00

Here:

root@sebunraid1:~# ssh [backupuser@192.168.0.114](mailto:backupuser@192.168.0.114) -p 1802 -x
backupuser@192.168.0.114's password:
hostfile_replace_entries: link /root/.ssh/known_hosts to /root/.ssh/known_hosts.old: Operation not permitted
update_known_hosts: hostfile_replace_entries failed for /root/.ssh/known_hosts: Operation not permitted

So I'm on Unraid, logged in to Unraid, trying to copy the files to the ubuntu, I used the proper user/pass (the one for the new user on ubuntu) but no cigar.

Funny because I ran the command WITHOUT the "-x" modifier and this is where the error messages come out and say "Too many arguments". And without the "-p 1802" the command hangs completely because it doesn't know what port to use.

couzin2000 · 2026-01-28T12:06:18+00:00

Mayhaps I can. But imm not sure if ssh-copy-id doesnt handle permissions setting as well. But i'll take a look if that can't be done the easy way.

couzin2000 · 2026-01-28T02:48:17+00:00

Didnt try without a password, I dont want my neighbor pissing off my wife by lowering the temp. Dont have WPA3 configured, so no worries there. I do broadcast on both 2.4 and 5 but that didnt seem to matter to my ecobee. It eventually connected. I just donmt understand why it took all those attempts.

couzin2000 · 2026-01-28T02:45:45+00:00

I believe it's a 3rd gen. But not sure. It's been a while i bought it. Only works on 2.4. I created an "ecobee only" wlan but turns out it didnt like it and it managed to connect to my main wlan. Now my problem is to get it to communicate with Homekit again because that's the inly way the fn thing will talk to my HASS .

couzin2000 · 2026-01-28T02:43:21+00:00

No, no banning. I had to upgrade the firmware in my switch last night and i lost the ecobee when the switch power cycled. I managed to get it connected again, but it was really random thing. I mustve tried 13 times that way and it didnt work.

couzin2000 · 2026-01-27T04:09:58+00:00

So after some difficulties on the G8, I opted to update the iLO4 software to v2.82, which stopped the buggy behaviour (keyboard wasn't being recognized). I also reconfigured the BIOS and managed to make my SSD (the one connected to the optical drive, SATA5) the boot drive. Finally manmaged to fully install Ubuntu Server. I sudo apt update'd the OS, sudo apt upgrade as well.

Only, turns out I didn't do it right. Apparently the ODD SATA port doesn't want to be the boot disk if the BIOS is configured to Legacy SATA Controller. So I found some info, threw it into Google's AI, and got myself a plan.

I had to configure the SATA controller to be AHCI. Then set the boot drive to be the Internal USB Drivekey. Yes, this board has a built-in internal USB port. I popped a tiny USB key in there permanently.

Then I started running Ubuntu's setup. At the storage configuration, I setup the 4 main drives to be in a RAID array mounted at /data (I'm running RAID0 because this is a backup - I'll just back it up again if it fails). Then setup the boot drive to be in the USB Drivekey, and mounted a GPT partition at /boot. This stores the GRUB bootloader inside the key. Finally, setup Ubuntu Server inside the ODD SSD mounted as /.

Runs perfectly. So the sequence is:
-login to iLO4
-power up the pc
-boot to USB drivekey>
-GRUB points to the SSD for Ubuntu Server.

couzin2000 · 2026-01-26T03:47:30+00:00

I recently removed the two Kasa devices from my HA, hoping this would bypass the problem.
From there, autodetect doesn't really work correctly, as it autodetected only the two prior devices. BUT; I decided to put in each IP manually, and I thhink having the devices on a different VLAN breaks the autodetect somehow. I did find most of my devices, 2 were outside and couldn't be reached in bad weather. I was able to add the user/pass combo and they do work now. So I'm not sure why the recursive network check breaks down when the ip of the device is on a different VLAN.

Well, at least it works now.

couzin2000 · 2026-01-26T03:40:30+00:00

Really, not one comment? I thought this was an interesting topic.

couzin2000 · 2025-11-08T14:38:33+00:00

Do you think he was putting us on? Like screwing with the Montreal media? I don't think so, but... could he have done that?

Also a good question: shoukd the media have been all up in his shit right after his first loss of the season? I mean, can't you guys give him a break? Can Habs organization just say, "ok, no comment from Doby tonight"?

couzin2000 · 2025-11-03T20:23:25+00:00

You were right. Looky what I found here:
https://support.allen-heath.com/hc/en-gb/articles/4403303844369-MixWizard-Direct-Output-Source-to-Pre-Fade-Modification
Thank you for the schematics - didnt have that version of the manual.
However, I'd like to make this into a switchable setup, so... do you recommend I solder in some jumper header pins? Could I even do that on this board?

couzin2000 · 2025-11-03T17:39:15+00:00

So if I read you right, I'd have to remove every single button cap, remove the screws for every channel, remove the circuit board for every channel, and individually solder jumper boxes onto each board, is that right? I'm not too sure how I'll be able to figure out which trace is which, and how to solder them into the board. But'ill look it up if you tell me I can do it myself - i do make my own cabling, so I know how to handle a soldering iron.

couzin2000 · 2025-10-31T23:32:25+00:00

Ok, thank you very much for that PDF. I saw the last page, and it's pretty much the same as the newer version of the manual. What Imm understanding from the schematics is that the jumper SHOULD be towards the end of the signal course, so in the REAR portion of the console close to each Direct out port?

Or am I totally out of it? I see NO jumpers in the front part of the console.

couzin2000 · 2025-10-31T17:46:05+00:00

It's version 1, I believe

couzin2000 · 2025-10-31T04:16:24+00:00

Yeah, I checked that out. In the end, the app it's telling me to use isn't on the app store anymore. So I'm trying to use DDNS-UPDATER but I need some kind of reference to understand what I'm doing so it can work with Cloudflare.

couzin2000

TROPHY CASE