pnht

I've printed about 4 kg of filaments with my KE. Worked flawlessly until last Friday. Suddenly it isn't extruding enough. things that should be "solid" (like the brim, and the first few layers of a cylinder with 100% infill) have probably 0.1 or0.2 mm of empty space between the lines.

I tried cleaning out the nozzle, no change.

I replaced the nozzle with a brand new one, no change.

I started a print and "adjusted" (via the creality touch screen), the flow. at 120 to 140% it got solid, but seems inconsistent (as to whether or not 140 is too much or 120 is too little, it wouldn't stay "just right" with any setting).

Any ideas? No noises from the extruder (such as slipping or clunking).

I followed a guide for firmware upgrade to Alex's firmware fron voxellab's aquila firmware.

I have a G32 chip original Aquila.

The controller board firmware update seems to have worked well. The display also seems to take the upgrade (comes up blue then turns red). But after the restart the display is still all jumbled.

Has anyone done this upgrade and know a version of the display firware that works? I've flashed the display with these:

1. DWIN_SET (Voxelab Red)
2. DWIN_SET (Voxelab Original Light)
3. DWIN_SET (Original)

the firmware shows this filename for the firmare in each directory:

"T5UIC1_V20_4页面_191022.BIN"

None of them change the scrambled display.

I want to have tuya devices work when the internet is down. Like freezer refrigerator temp especially).

No matter what I do, I cannot get tinytuya or tuya-cli to work.

tinytuya scans for devices and finds none.

tuya-cli link returns "Error: permission deny"

I've set up and re-setup my project and app on iot.tuya.com multiple times. But their website doens't match any of the instructions exactly, so I may be doing it wrong.

Does anyone know of instructions that are recent and match the current website?

I really want to have devices still work when the internet is down. And I've run into devices saying "T & H Sensor (unsupported) (x3o8epevyeo3z3oa)".

I'm running HA on bare metal, and using HACS.

I've tried to use a few of the "local" integrations for Tuya, and all of them fail at either "scan for devices" (to then get their keys), or at "link device to your iot.tuya.com account". The iot.tuya.com site is now so complicated that I can't find one that let's me bind devices to a project. I can bind my samrtlife app to the account, but, well, nothing seems to work (the regular Tuya integration works except for the "T & H Sensor (unsupported) (x3o8epevyeo3z3oa)" problem (and that I want to

I bought a USB Advantage360. It arrived today. I think I like it, but it won't enter remap mode or macro mode. Anyone else had this problem?

I am doing it right, I tried multiple different machines, so it isn't a bad USB port.

Trying to find the part number for the w541 backlight inverter. If it makes a difference, mine has the 3K (2880x1620) screen.

It is really weird. On wall power the whole screen is uniformly backlit. But, even on a fully charged battery, the left half of the screen is much dimmer. Hoping a $20 inverter board is the fix, but can't find one for sale anywhere.

Closest I've gotten is a w530 inverter board, which, in the one picture I found doesn't look quite right, but I've not disassembled my w451 to verify.

Thank you! pnht

When my phone is locked, and an alarm (standard "Clock" app) goes off, it used to (~6 weeks ago, and the previous 5 years..) pop up a notification on the lock screen and I could tap or swipe to stop the alarm.

Now no notification on the lock screen (although there is a alarm clock icon showing when the next alarm will go off!!).

I have:

1. Cleared clock app cache.
2. Cleared clock app storage.
3. Rebooted phone a dozen times just today.
4. Set Clock app notifications to all be on.
5. Set Notifications to show sensitive content on lock screen (I cnanot leave it that way, and it was set to Not show sensitive content when the alarm used to notify on the lock screen; but I enabled it anyway t

I've had my TCL 65R455 since August 20. Everything was great. Audio to my surround sound receiver was via HDMI using ARC.

Starting 2 weeks ago, most of the shows that I watch (mainly Plex off my own in house Plex server) the audio is lagging probably 0.2 seconds (believe me, 0.2 seconds is a LONG time for lip sync). I've tried everything. I bought an optical cable, same problem. If instead of using the TV's builtin Roku, I plug one of my Roku devices into the TV, there is no audio sync problem.

Anyone else having audio sync problems in the last few weeks. It seems, from posts on the net, that 11.0.2 came out October 2, my TCL updated to 11.0.2 on Oct 4. and all my problem started "ab

On a recent trip, 2 of the feet on one of my Advantages came off (in my luggage) and were lost.

Kinesis does not sell feet. I bought quite a few online and finally found one that is almost an exact match.

The critical part is that it should fit entirely within the depression in the case where it is supposed to go, And, be as big across as possible to have the most contact surface. I found a lot that were just a smidge bigger than the depression. They all fell off within a day or two.

I finally found this assortment on Amazon. The strip of 22 feet at the top of the main pictures are the ones you want. They are almost perfect replacements. Exact same shape and dimensions, except that

TL;DR - My question:

• How for a device to present obstacle distance, closure rate, and impact imminent information to a blind dog such that he can understand? Or, alternatively, what terms would I use to search for research or data for myself?

I don't understand the psychology(?) of training/learning, especially as it applies to dogs (no understanding of complex speech); so, I'm looking for help figuring this out.

And, now, the rest of the story.

My dog has gone blind. I've developed a system using laser/led distance sensors that can provide up to three different pieces of information:

• distance to obstacle
• closure rate (as either the dog, the obstacle of both could be moving)
• i

I recently got a SimplyNuc Ruby (model CBM1r8RB).

Everything runs great.

Except for fan control...

fan noise is not a problem for me, BUT... a fan that revs way up for 5 seconds and then back down, then 10 seconds later revs way up for 5 or 8 seconds and then spins back down... repeat ad nauseum...

lm-sensors finds nothing about the fan.

find /sys | egrep 'rpm|fan|speed'

Doesn't show anything useful either.

Any pointers what to look for in dmesg, /sys? lspci, lshw, lsusb didn't reveal anything either.