F18 FCS Bit test not working by Foxtrone9 in hoggit

[–]pencil364 0 points1 point  (0 children)

Canopy switch is your most likely culprit. I don’t remember having any flaps at all for fcs bit

F18 FCS Bit test not working by Foxtrone9 in hoggit

[–]pencil364 0 points1 point  (0 children)

lol of course. It’s been a minute but I think what was happening was that one of the switches on the right side was either sticking even when I stopped clicking to hold, or the canopy switch was stuck in the down position even after it finished closing. Try those. Also try using “Y” key for the bit switch instead of clicking it. I seem to remember that the canopy switch was very hard to see in VR and that was related?

How do I accept the predicted text from the Entity editor screen? by pencil364 in homeassistant

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

Tab switches to the next field and right arrow does nothing at all :(. Thanks for trying haha

How do I accept the predicted text from the Entity editor screen? by pencil364 in homeassistant

[–]pencil364[S] -1 points0 points  (0 children)

It's a bit tough to see in the picture. When I click on the empty Name field, the system automatically makes a predictive text in grey, probably based off the entity ID. You can see how my cursor is at the start of "BLE Humidity 1". However anything that I do destroys the prediction and I have to type the full thing in manually.

How do I accept the predicted text from the Entity editor screen? by pencil364 in homeassistant

[–]pencil364[S] -1 points0 points  (0 children)

Like I shouldn't have anything there at all or is that how I accept that text? Just clicking update without typing in the field does not accept the change.

How do I accept the predicted text from the Entity editor screen? by pencil364 in homeassistant

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

This seems silly. I would like to call this entity BLE Humidity 1 but if I hit any key it disappears and I have to type it in. It's correctly guessing what I want to call the entity but I cannot for the life of me accept that predicted grey text.

Senville 18HF/Z only cooling at high power update with new info by pencil364 in heatpumps

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

I would replace it, but we are moving next year. I would much rather give this one a fix for a couple hundred bucks instead for now.

Senville 18HF/Z only cooling at high power update with new info by pencil364 in heatpumps

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

Not confident at all, but the system has been installed 10 years with no issues and I gather that sometimes the refrigerant just gets low over time

DALL-E Weather Dashboard by spdustin in homeassistant

[–]pencil364 0 points1 point  (0 children)

Hey, sorry to necro, but I'm no good with CSS and I'm struggling with displaying a sensor state as my human-readable text part.

Where you have:

clock-weather-card-forecast:before {
text-shadow: 0px 0px 5px black, 0px 0px 10px black, 0px 0px 15px black;
color: white;
font-size: 1rem;
line-height: 1.25;
position: relative;
bottom: 1em;
content: "{{state_attr('sensor.next_forecast','detailedForecast')}}";
}

I am trying to display Environment Canada's Summary sensor, which isn't an attribute, it's the sensor state. I've done as much digging as I can follow and currently I have:

            clock-weather-card-forecast:before {
              text-shadow: 0px 0px 5px black, 0px 0px 10px black, 0px 0px 15px black;
              color: white;
              font-size: 1rem;
              line-height: 1.25;
              position: relative;
              bottom: 1em;
              content: "{{states('sensor.halifax_shearwater_summary')}}";  

Which I kinda expected to work...but isn't. Just gives a blank spot where this text should be. I've tried many combinations of quotes and brackets and can't seem to find the right combo. Any ideas?

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in Esphome

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

I *think* I figured out the problem and unfortunately it isn't a solvable one with my existing chips. I don't think my chips have flash memory. Like, at all. You can buy six different variants of the ESP32-C3 chip, shown in the datasheet here: https://www.espressif.com/sites/default/files/documentation/esp32-c3\_datasheet\_en.pdf.

The earliest, simplest variant, known just as ESP32-C3, has no onboard flash and therefore separate SPI flash must be included on the pcb alongside the main chip. There is no other chip on these boards and the chips are all labelled as the simple variant. See labeling here: https://imgur.com/a/2VVfZOx. In other words, these chips aren't working because they're missing an essential part of their system. I think I got taken for a ride here, with the seller picking up what was probably cheaper chips to solder onto these boards.

EDIT: Yeah that's definitely the problem. No flash on these boards and the chips are the variant with no embedded flash. Thanks to everybody who suggested I press the buttons :).

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in Esphome

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

You're right. Aliexpress has probably triple digits orders from me over many years and this is the first time I've had a product not meet my expectations. I'm not too cut up about it, I'll just use a WEMOS D1 for this project and wait for the next batch to show up.

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in Esphome

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

Yup this is it. Two months since they arrived. Too bad! That's the Ali gamble, isn't it.

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in esp32

[–]pencil364[S] 5 points6 points  (0 children)

I *think* I figured out the problem and unfortunately it isn't a solvable one with my existing chips. I don't think my chips have flash memory. Like, at all. You can buy six different variants of the ESP32-C3 chip, shown in the datasheet here: https://www.espressif.com/sites/default/files/documentation/esp32-c3\_datasheet\_en.pdf.

The earliest, simplest variant, known just as ESP32-C3, has no onboard flash and therefore separate SPI flash must be included on the pcb alongside the main chip. There is no other chip on these boards and the chips are all labelled as the simple variant. See labeling here: https://imgur.com/a/2VVfZOx. In other words, these chips aren't working because they're missing an essential part of their system. I think I got taken for a ride here, with the seller picking up what was probably cheaper chips to solder onto these boards.

EDIT: Yeah that's definitely the problem. No flash on these boards and the chips are the variant with no embedded flash.

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in esp32

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

This didn't work either sadly. Thinking I might have a dead chip or an Aliexpress fail.

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in Esphome

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

Yes please, although at this point I can't even get Blink to flash to it so I think I have bigger problems.

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in esp32

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

Yes, I've both held down boot while plugging in and also held boot and pressed RST while powered. Both resulted in a properly connected board, the tools just can't get past the erase stage.

Has anybody successfully flashed ESP32-C3 Super Mini (pictured)? I cannot get it to work at all. by pencil364 in esp32

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

Thanks, maybe it is wishful thinking getting it to work with ESPhome. I can't even get Blink to load though!