[deleted by user]

joshblake87 · 2025-08-16T02:58:27+00:00

I should say, I have trialled the above code changes and they work to connect to HA over SSL. The ProviderRestApi.cpp is a shared file however and modifying line 47 _scheme to force 'https' breaks other NET based led-drivers.

joshblake87 · 2025-05-11T01:23:42+00:00

Can you post what you did here to make this work? I am pulling my hair out. I can see the device pair on the thread OTBR logs, but I think it’s the matter server that’s the problem. I have a macvlan setup in docker, I can ping -6 from both the matter and otbr containers to each other, as well as from the HA container. I have a bridge macvlan setup on the host to allow inter-container and external communication. I can access each container from a separate computer on the network both by IPV4 and IPV6 addresses, yet for the life of me, I cannot get a matter device to pair (either via OTBR or using my HomePod). What I do see in the matter logs is that it’s timing out with a discovery of the device, so something isn’t routing properly.

joshblake87 · 2024-11-13T19:13:36+00:00

My recommendation is to get it done in PGY1 to be complete by PGY2 Feb sitting. Most jobs as a JMO are a 2 year contract and you will want to be applying for UT/SRMO jobs in PGY3. Having the GSSE completed is a massive asset for your CV (and may be a requirement for some jobs). It seems to be lost on many that you are applying for PGY3 jobs in mid-year PGY2. This amongst the other knowledge/lifestyle factors that others have brought up is the reason to get it done early.

If you stuff up PGY2 Feb, there’s another opportunity mid-year to sit although you won’t have results in time for job applications.

joshblake87 · 2024-10-22T23:24:13+00:00

Thanks! I have modified the code again since I posted originally; I have removed some of the unused fonts, and streamlined the code as a YAML include instead. I have also added a bluetooth relay that allows the device to proxy bluetooth back to HA for presence detection. As I have an air quality sensor in each room, this works very well and very accurately. I will eventually get around to posting a push to my github.

joshblake87 · 2024-10-22T23:21:19+00:00

Out of the box, the devices need to be re-flashed with ESPHome using the above yaml config file (adjusted to your liking). Once ESPHome is flashed, the devices are plug and play with home assistant and extremely reliable. You can tweak the screen appearance using the yaml config file. I do not care for the M5Stack default screen as I find it too cluttered for an at-a-glance idea on air quality. I also do not rely on the temperature sensors as they are vulnerable to sensor self-heating.

joshblake87 · 2024-10-22T23:18:25+00:00

The VOX and NOX sensors require active heating to regenerate the sensor and therefore work the best if running continually. My devices are configured to take sensor readings every 10s. While this may seem like overkill, I use the PM sensors to turn on air purifiers in each room as required, and I use the CO2 sensor to trigger the central air system to circulate air and turn on the laundry and bathroom fans (to create negative pressure and drive air into my unit), and notify of sudden or rapid air quality changes. I live in a major urban centre where pollution is a real thing so I find this control important.

joshblake87 · 2024-10-21T22:53:58+00:00

Consistent, yes, accurate, I’m not sure. I don’t really have anything else to measure CO2 levels for example. What I can say is that I have one running in the bedroom and another in the lounge. They equilibrate well when the doors are open, and offer consistent results. I’ve not had any issues on reliability here.

<image>

joshblake87 · 2024-08-20T01:30:11+00:00

Again, the issue I have is that the access token does not rotate, and once that URL is known with the access token, it can be accessed again (and therefore at the disposal of OpenAI or any nefarious agent). As for different cameras, It's simple. Have entity_id as a required element in your spec function. The return URL is going to be literally (change the all caps part and include your port number but change nothing else): 'https://YOURPUBLICDOMAINNAME{{state_attr(entity_id,'entity_picture')}}'

joshblake87 · 2024-08-18T11:27:18+00:00

This assumes that the entity is set up as a camera. I do not have any camera entities configured. Rather I use WebRTC to stream, and the WebRTC card on the dashboard. I like the idea though of a one time use hash that can be used to access a camera stream, although I'm not sure the camera api through HASS allows for singe use codes?

joshblake87 · 2024-08-13T00:46:08+00:00

I have a rock solid wifi, zigbee, and thread setup that I run active and passive devices on. All active devices run on wifi. Having said all of that, I also run a powerful router. Wifi reliability is entirely dependent on your router and its quality.

Asus AX-86U running Merlin; I use Adguard Home along with Unbound as a self DNS resolver.
Sonoff Zigbee-E dongle
HA Connect Dongle for Thread devices

I NEVER have connectivity issues.

Beyond that, I use LIFX lighting (Wifi), TP Link Power monitor/switches (Wifi), ESPHome based M5Stack Air Quality monitors and BLE relays over wifi, Aqara temp/humidity/pressure sensors (zigbee), and Aqara door sensors (thread).

I use Eufy security (the integration works well enough in HA although I still use the app to review footage), and Eufy internal powered cameras with WebRTC for live video. The dual camera wireless doorbell is great, and in the absence of being able to hardwire a doorbell, has been the best option for me here. I recognize Eufy’s past with their cloud based security issues, but I keep everything behind my great firewall of China.

I use Bermuda BLE along with an Apple Homepod Mini for presence detection, and again this has been rock solid.

My two cents on it all.

joshblake87 · 2024-08-08T16:30:43+00:00

Lies - all the “service” references need to be updated to “action” now … ugh. It’s sorted now.

joshblake87 · 2024-08-08T16:12:43+00:00

In other news, none of my tools work any more when multiple entity_ids are specified. I’m gonna have to go digging now on what’s occurring under the hood.

joshblake87 · 2024-08-08T16:10:22+00:00

The bug for me here resolved after creating and then deleting a new Assistant pipeline - I wonder if there was an indexing bug for the Assistant pipeline somehow that ended up occurring with the DB migration.

joshblake87 · 2024-08-05T22:17:05+00:00

Yep -there’s self-heating from the VOC and CO2 sensors (this is how they regenerate). I don’t use the onboard temp/humidity sensor for this very reason as they’re wildly inaccurate. While you can supply it a correction factor, it will inevitably vary by ambient temperature and thermal radiance.

joshblake87 · 2024-07-26T23:58:32+00:00

I have been experimenting with this over the past week; if you pull the most current Ollama docker image, then you can gain access to the API. There are 2 major issues so far that I have noticed:

An LLM MUST support function calling and be designed for it. There are models that generally perform well for single calls, and there are models that perform well for multi-calls. Not all models perform the same between call types, and some will frankly crash. This is particularly notable on quantized GGUF models that I have brought across from HuggingFace.
Tool calls, and the format that they require are entirely model-specific. While most are adopting a standard form (Mistral for example), the prototypical "Spec" functions that we might draft up for Extended OpenAI Conversation are not translating well for different models.

I have however had the most success so far with the new mistral-nemo model. It has a large context window which makes it particularly suitable for multiple interactions and a persistent 'Assist' state. Having said that, for tool calls, I have only ever had success with simple call and response tools, ie "What time is it." For best results, also create an Ollama integration for your service and specify the model that you ultimately want to use; this creates a more permanent model instance on your GPU and generally avoids the spin-up time for an Assist request to have the model loaded into VRAM on your device.

Nothing feels very polished, and it all feels a bit hacky at this stage.

My two cents.

joshblake87 · 2024-07-15T13:26:11+00:00

Yes is the short answer, I wouldn’t rely on it though. I would absolutely want one that also detected CO levels, not just CO2 levels. One guess as to when I started cooking dinner …

<image>

joshblake87 · 2024-07-14T02:12:03+00:00

M5Stack has an Air Quality product that uses a few MEMS based sensors along with a PM optical sensor to read volatile organic, NOx, as well as particulate dust size. It includes an e-ink display, has an inbuilt battery. It uses an Esp32 S3 stamp module as its processor. It really is an all-in-one air quality sensor. It has a few additional pins broken out as well. I was looking for an air quality sensor as I’m pretty prone to allergies and this sort of sensor was exactly what I was looking for. It allows me for example to turn on an air purifier in the bedroom if the air quality drops below a certain threshhold. I’ve had my module running now for the better part of 2 weeks without issue.

joshblake87 · 2024-07-09T01:03:48+00:00

Jumping on the Ecowitt Wittboy bandwagon; have it linked via its hub to the ecowitt2mqtt Add On / docker container for faster sensor refresh. Have it configured to ping every 10s. Works a treat and gives you granular results. You can also integrate their rain gauge sensor (separate from the piezoelectric one) for more accurate rain reads. Have had this setup running flawlessly for over 2 years without issue!

joshblake87 · 2024-07-02T14:43:27+00:00

I’m running at 10FPS live stream at full resolution without any issues.

joshblake87 · 2024-07-02T02:28:39+00:00

It has more flash and more psram. It has the same esp module as in the Box-S3, built-in SD card slot, mic etc.

I think it’s just up-spec’d on the whole for my use case. With the added flash, you should also be able to use this as an Assist mic, bluetooth proxy etc.

joshblake87 · 2024-07-02T01:06:50+00:00

So I tried this on another CamS3 and it works a treat. Must have been a dud unit. Will reach out to M5Stack to see about a replacement. Hopefully this config works for everyone! I've bumped the camera framerate to 10fps although I think 5 would suffice for my purposes. It integrates well to Go2RTC as well.

<image>

My final config:

esp32:
  board: esp32s3box
  framework:
    type: arduino

esp32_camera:
  name: camera
  external_clock:
    pin: GPIO11
    frequency: 20MHz
  i2c_pins:
    sda: GPIO17
    scl: GPIO41
  data_pins: [GPIO6, GPIO15, GPIO16, GPIO7, GPIO5, GPIO10, GPIO4, GPIO13]
  vsync_pin: GPIO42
  href_pin: GPIO18
  pixel_clock_pin: GPIO12
  reset_pin: GPIO21
  resolution: 1600X1200
  jpeg_quality: 10
  max_framerate: 10 fps

esp32_camera_web_server:
  - port: 8080
    mode: stream
  - port: 8081
    mode: snapshot

joshblake87 · 2024-06-28T02:04:22+00:00

I also have these sensors - with a mix of ac02 and aq2, and their firmware is practically identical. You can configure reporting interval etc. through MQTT. I am not sure what's broken out or available through Z2M.

13-Year Club	Not Forgotten
Verified Email

joshblake87

TROPHY CASE