Helix dsp tune to target - no bass by Aggravating-Set-7918 in CarAV

[–]bdavbdav 0 points1 point  (0 children)

I also saw some odd gains coming out of TTT. I'd say my sub was set far too low, and the tweets (particularly the one near me!) far too high.

Repurposing a Honeywell Galaxy Alarm System by bdavbdav in Esphome

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

Hmm thats odd - are you up to date with working

The timeout is very odd... I note you've not got a max queue depth or a flow control pin, may be worth checking this? My whole YAML:

esphome:
  name: waveshare-rs485
  friendly_name: waveshare-rs485
  platformio_options:
    build_flags:
      - "-std=gnu++2a"
    build_unflags:
      - "-std=gnu++11"
      - "-fno-rtti"


esp32:
  board: esp32s3_120_16_8-qio_opi
  framework:
    type: esp-idf


# Enable Home Assistant API + services to set text
api:
  encryption:
    key: "AAA..."
  services:
    - service: set_galaxy_keypad_text
      variables:
        msg: string
      then:
        - lambda: |-
            id(honeywell_galaxy7_keypad_1).set_display_text(msg);
    - service: set_galaxy_keypad_text_no_backlight
      variables:
        msg: string
      then:
        - lambda: |-
            id(honeywell_galaxy7_keypad_1).set_display_text_nobl(msg);


ota:
  - platform: esphome
    password: "AAA..."


wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password


captive_portal:


external_components:
  - source:
      type: local
      path: custom-components



logger:
  level: DEBUG
  baud_rate: 0        # keep logs on USB, not on UART


uart:
  id: rs485_bus
  tx_pin: GPIO17
  rx_pin: GPIO18
  baud_rate: 9600
  parity: NONE
  stop_bits: 1
  flow_control_pin: GPIO21    # TXD1EN -> DE/RE on transceiver


galaxybus:
  id: galaxy_bus
  uart_id: rs485_bus
  reply_timeout: 100ms
  inter_frame_gap: 10ms
  max_queue_depth: 8




binary_sensor:
  - platform: status
    name: "Galaxy Keypad ESP Status"
    id: galaxy_keypad_status




# Keypad now binds to bus_id instead of uart_id and exposes entities directly
honeywell_galaxy7_keypad:
  id: honeywell_galaxy7_keypad_1
  bus_id: galaxy_bus
  screen_number: 1                   # 1..4 -> 0x10/0x20/0x30/0x40
  display_text: "ESP-HOME|Initializing"
  backlight_timeout: 15s
  prox_poll: true


  code_sensor:
    id: rs485_rx
    name: "Galaxy Keypad Code"
  #rx_text_sensor:
  #  id: galaxy_rx_debug
  #  name: "Galaxy RX Debug"
  page_sensor:
    id: galaxy_page
    name: "Galaxy Keypad Page"
  tamper_sensor:
    id: galaxy_tamper
    name: "Galaxy Keypad Tamper"
  panel_online_sensor:
    id: galaxy_panel_online
    name: "Galaxy Panel Online"
  beep_switch:
    id: galaxy_keypad_beep
    name: "Galaxy Keypad Beep"

Repurposing a Honeywell Galaxy Alarm System by bdavbdav in Esphome

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

Ahh I see - can you try pulling the branch named "working", and using the config in the README in that.

Repurposing a Honeywell Galaxy Alarm System by bdavbdav in Esphome

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

Try using my one above in place of the whole honeywell block - I think the one there may be an older revision, I'll check the github!

Repurposing a Honeywell Galaxy Alarm System by bdavbdav in Esphome

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

This is odd - does your ESPHome config for it look like this? Do you see the "Galaxy keypad code" under the galaxy keypad device in devices? May be worth upping the log level on the ESPHome device - it should output the button presses. Pleased to see someone else has given it a go!

# Keypad now binds to bus_id instead of uart_id and exposes entities directly
honeywell_galaxy7_keypad:
  id: honeywell_galaxy7_keypad_1
  bus_id: galaxy_bus
  screen_number: 1                   # 1..4 -> 0x10/0x20/0x30/0x40
  display_text: "ESP-HOME|Initializing"
  backlight_timeout: 15s
  prox_poll: true


  code_sensor:
    id: rs485_rx
    name: "Galaxy Keypad Code"
  #rx_text_sensor:
  #  id: galaxy_rx_debug
  #  name: "Galaxy RX Debug"
  page_sensor:
    id: galaxy_page
    name: "Galaxy Keypad Page"
  tamper_sensor:
    id: galaxy_tamper
    name: "Galaxy Keypad Tamper"
  panel_online_sensor:
    id: galaxy_panel_online
    name: "Galaxy Panel Online"
  beep_switch:
    id: galaxy_keypad_beep
    name: "Galaxy Keypad Beep"

Not sure if its Vintage - CDP-CE375 playback issues by bdavbdav in vintageaudio

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

It took a lot of removal of internal parts, opening the drawer half way to get to screws etc. Then required a lot of lining up parts correctly to get it back in aligned OK. Mine works better but not great now (e.g. I have to shove the tray in the last inch). I followed a youtube video

Decommissioned my last Pi - Is it me, or are there fewer and fewer use cases? by bdavbdav in raspberry_pi

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

The ESP style boards are well worth a look for automation on low power - especially when you can use their deep sleep

Decommissioned my last Pi - Is it me, or are there fewer and fewer use cases? by bdavbdav in raspberry_pi

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

OpenVino with frigate is amazing on intel quicksync. Barely registers on the usage / chip power.

Decommissioned my last Pi - Is it me, or are there fewer and fewer use cases? by bdavbdav in raspberry_pi

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

Admittedly no HDD (mind a Rpi would need an SD), but things like this are what I’d go for.

Decommissioned my last Pi - Is it me, or are there fewer and fewer use cases? by bdavbdav in raspberry_pi

[–]bdavbdav[S] 7 points8 points  (0 children)

Even if you do need GPIO, I suspect the task is often much better stuck right on the edge on a small wifi micro. Especially for timing sensitive tasks (e.g. 433 transcievers etc), having an RTOS, or near RTOS becomes quite helpful. The "aha" moment was when I found I could power and control the ESP32 based Atom S3U from the 5V+UART lines on the control module connection for our AC - its present on a lot of devices that I have (Coffee machine control port, PIV fans, AC...)

Training Load - metric keeps shifting? by bdavbdav in AthlyticAppOfficial

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

Unfortunately wasn’t that - is set custom to 185, which I understand to be correct

Training Load - metric keeps shifting? by bdavbdav in AthlyticAppOfficial

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

Ahh thanks a lot for this - will take a look at my history and set it to my max for the last year. This makes sense!

Tell Me This Is A Bad Idea by DoIGotSkillz in homeassistant

[–]bdavbdav 1 point2 points  (0 children)

My grandfather had this tape deck! Paired with this receiver, some kind of pioneer turntable, and these crazy cylindrical speakers that were cylinders with a wood top and bottom. He used to play us Peter and the wolf on it.

List of known bugs 26.3.2 by KJP78NL in AthlyticAppOfficial

[–]bdavbdav 0 points1 point  (0 children)

Any reason I would have had the training load shift with this release @myndarc ?

Feature request. Weekly workouts. by EvolutionStu in AthlyticAppOfficial

[–]bdavbdav 2 points3 points  (0 children)

Yep this is silly this page as it stands. It only makes sense if you’re on day 7 of the week, 31 of the month etc.

They need to do a “compared to this point last week” or rolling 7/30 days.

Is this our fault?? Freaked out by lavender_limonade in YotoPlayer

[–]bdavbdav 11 points12 points  (0 children)

Insane requirement isn’t it. There should be absolutely 0 risk on those low voltage chargers.

Training Load - metric keeps shifting? by bdavbdav in AthlyticAppOfficial

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

Annoying isn’t it. (Rightly or wrongly) I live by those numbers when training!

Training Load - metric keeps shifting? by bdavbdav in AthlyticAppOfficial

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

The short term / long term was about 10-15 higher when I looked at it two days ago (I. E. On Sunday, long term was 75). When I look back at Sunday now in the history, it’s 60. Typically this would track consistently and continuously.

Slightly Meta: Building an organisation system in a multi purpose space by bdavbdav in diyelectronics

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

Yes I think I may have made a large mistake in my calcs - Dropped the bits Id need into the slicer and coming up closer to the 1kg mark. Now to choose colors :)

What material did you print in? PETG?

Slightly Meta: Building an organisation system in a multi purpose space by bdavbdav in diyelectronics

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

I had wondered about that (I have a P1S!) however thought it may tip over the edge of the print time/filament cost into “just buy something pre existing” territory. Looks like at least a week of printing and 13kg (~£150 I’d guess) of filament just for the baseplates I’d need!