Cigar Oasis - Third party integrations - Home Assistant Community = 40rem)" rel="stylesheet" data-target="desktop" /> = 40rem)" rel="stylesheet" data-target="chat_desktop" /> = 40rem)" rel="stylesheet" data-target="discourse-ai_desktop" /> = 40rem)" rel="stylesheet" data-target="discourse-reactions_desktop" /> = 40rem)" rel="stylesheet" data-target="poll_desktop" /> = 40rem)" rel="stylesheet" data-target="desktop_theme" data-theme-id="19" data-theme-name="scroll to top"/> Cigar Oasis Third party integrations image969 (James Scialdone) February 14, 2023, 8:24pm 1 Any possible chance there is integration for the oasis, humidor line to measure humidity? nickrout (Nick Rout) February 15, 2023, 5:04am 2 Do they have an API? Or do you just want to put a humidity sensor in a dumb box? image969 (James Scialdone) February 15, 2023, 11:55am 3 Cigar oasis smart humidor is the name of their app. So it’s a humidifier that already connects to wifi GaryK (Gary Kelley) February 15, 2023, 12:09pm 4 I wasn’t able to find one. Ended up with Wireless Sensor Tag. image969 (James Scialdone) February 15, 2023, 12:22pm 5 Hmm I dunno I only have a 120 count humidor and the oasis takes up enough room as it is lol do you consider this to be very accurate? Problem is while I have never ever had a problem with my humidifier. It’s a pain sometimes to lift the tray and check on it from time to time to make sure the humidity is good. They have their own app but what fun is that when I use Home Assistant? Lol. GaryK (Gary Kelley) February 15, 2023, 12:38pm 6 Accuracy is good. I use the tag to monitor a kegerator and cheese fridge. I monitor with this. The integration works well enough for temp/humidity. nickrout (Nick Rout) February 15, 2023, 7:08pm 7 How does the app communicate with the humidifier? if it is bluetooth, good chance of making it work via esphome perhaps. GA_00 (G A) August 12, 2026, 9:05am 8 Cigar Oasis → Home Assistant, fully local (no cloud API needed) The Cigar Oasis Wi-Fi module (Microchip WINC) has no local API, but it phones home over plain HTTP, which makes it interceptable. What it actually sends Roughly hourly it does a GET to production.marsint.com: /hw/p1/<DEVICE_ID>/c2/276/p2/699/p3/802/p4/0/p5/700/p6/0/... param meaning p1 device ID p2 humidity ×10 → 699 = 69.9 % p3 temperature in °F ×10 → 802 = 80.2 °F p5 setpoint ×10 → 700 = 70.0 % The server just replies {"status":"update,"}. How to intercept it Add a DNS host record on your router: production.marsint.com → your HA IP. Prefer this over a DNAT rule targeting the vendor’s IP — when the vendor repoints the name, a DNAT silently stops matching and HA freezes while the phone app keeps working, which is a horrible failure to debug. Run a small HTTP listener on :80 that parses the path, publishes to MQTT with HA discovery, and tees the request onward to the real cloud IP so the vendor app keeps working. The trap that will bite you The tee must dial the cloud by IP literal, never by hostname. If it resolves production.marsint.com it hits your own DNS override and loops into itself. Two practical notes The device legitimately skips cycles — I’ve measured 176-minute gaps while perfectly healthy. Don’t alert on staleness under ~3–4 h or you’ll get false alarms. Verify with a packet capture, not just “HA shows a number.” Confirm zero packets still reaching the vendor IP; a stale reading looks identical to a live one on a dashboard.