Looks very good so far. I saw your note in the docs “In the future, this integration will be expanded to support reading RSSI values and hopefully support lots more devices like tracking smartphones and reading temperature values from BLE sensors.”
I’d love to put an ESP32 outside to drive a drip irrigation valve and be able to read (Bluetooth) miflora values and publish it on MQTT for HA to use.
Yeah sure it’s on my list, but that list is quite long… The problem is that I don’t own any BLE sensors (which send temperature values) and they seem quite expensive. Do you know of any cheap BLE-enabled sensors (~10$)? I’m thinking of maybe buying one as BLE is an interesting standard
Thank you! Just ordered one from eBay (I’m not a big fan of AliExpress) and will try to add support for it when it arrives - Gotta say that one @Petrica posted really looks quite dope (from a design perspective). So I’m already excited to have it arrive
@OttoWinter is there any chance of including control for digital LED’s? I found this earlier today as linked from another thread on this forum and thought it would be a nice addition to your awesome work to have digital LED control since the NodeMCU’s make such a neat little controller for this type of thing
yep, thats what I was thinking of… you already have it sorted, although to have more effects would be sweet, any chance of including these? (I’m just now reading up on how to do this from your page but it seems way above my skill level)
Man, This Thing is Great.
You have no Idea how much easier it has made implementing home automation.!! Actually, I’m guessing you do
I have a small Issue tho. The OTA update wont work using the Hass.io web interface. It tries to upload to sensorname.local . I have an internal DNS namespace called internal.local (imaginative I know).
The HASS Server quite happily resolves sensorname.internal.local but it cant resolve sensorname.local.
I tried to Cheat and named my sensor something.internal, so then it tried to connect to something.internal.local but you cant have a fullstop in the sensor name.
Any idea’s on where I can make the software append the correct DNS suffix?
To do this, first plug in the USB cable of the ESP into a USB port of the device esphomeyaml is running on and wait until you see a “Discovered new serial port” message (in some cases you need to restart the add-on). Select the upload port in the top navigation bar and press the big “UPLOAD” button
so, i disconnect my nodemcu of my PC, and connect it again on USB of my RPI… and…
This is a great easy to understand project… I’ve got the basics working… however I am running into a problem that should be easy to solve but I can’t seem to get this working…
I am trying to control an active low relay. With the default GPIO switch config I have everything working… however on is off and off is on… and a reboot of the ESP8266 NodeMCU V2 defaults the relay to an on state…
This is my config…
With that config… homeassistant seems to keep the switch always on (i.e. if I toggle to off in UI, it just toggles back on")
I think I need to use the following config to set the mode of the D1 pin on startup, but I can’t figure out where to do this in the YAML to have it default the pin to high (i.e. relay off) on startup?
mode: INPUT_PULLUP
Any help in getting this working properly with active low relays would be very appreciated!