You should see two switch attributes. As each device can only have one switch the state of the second switch is only available through the customAttribute.
If you are saying that you are not seeing a state change within the driver for the second switch the most likely cause is that you have not done a tasmotaInjectRule which configures the Tasmota to call Hubitat whenever there is an action of interest,
I'm using ESPHome and the drivers and app presented here at @jonathanb github page. There is a multi switch driver that allows the yaml config to address multiple switches. I do not see how tasmota would be invoked.
The switches are added in as child devices and those come up with the 'Generic Component Switch' driver preselected. The ON/OFF controls work, but there is no current state in HE.
@jonathanb Should the child devices for Multi Switch Driver have the 'Current State' shown? Have I missed something in my yaml config file?
You must not be using my driver as it does not have a parent device. Sorry I cant help you.
I believe that was my error, I've just updated the driver and I think it should now pass the state to the child device. Let me know!
So much appreciated! State showing in all aspects, device, log, webcore.
Thanks again!
Can we use the mmWave devices with these drivers? I'm assuming that you can do all the advanced config and settings in ESPHome and in Hubitat it just displays as a motion sensor with present or not?
Yes, as a bare minimum implementation you could expose a binary sensor from ESPHome (for detection) and re-purpose the example motion sensor driver I provide but you could expose additional sensors such as distance, presence, direction or whatever else the mmWave provides and expose those as custom attributes too by just adding some code into the driver to publish those events.
Any way to implement the smart dry ESP home implementation. Keeping your SmartDry dryer sensor operational
This has the instructions to set up. I have it working in home assistant but would prefer everything in Hubitat. Using your instructions I can connect to the ESP 32 module, but no sensors are showing up. Hoping you might be able to help.
@jonathanb I hate to bother you, but I recently tried to add another esphome sensor in HE (motion entity). However, this time the Entity never show up in the driver.
Yaml code:
esphome:
name: esphome-sensor
esp8266:
board: nodemcuv2
# Enable logging
logger:
# Enable Home Assistant API
api:
ota:
# Set Static IP
manual_ip:
static_ip: 192.168.xx.xx
gateway: 192.168.xx.xx
subnet: 255.255.255.0
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Esphome-Sensor Fallback Hotspot"
password: "FPEGdlL5WsY5"
captive_portal:
web_server:
port: 80
version: 2
binary_sensor:
- platform: gpio
pin: 4
id: pir_sensor
name: "PIR Sensor"
device_class: motion
internal: false
It shows up in logs (debug):
dev:27232023-01-21 03:44:59.316 PMdebugESPHome send msg type #8 with [:]
dev:27232023-01-21 03:44:54.866 PMdebugESPHome received: [type:state, platform:binary, isDigital:false, key:3061631947, state:false, hasState:true]
dev:27232023-01-21 03:44:54.813 PMdebug[D][binary_sensor:036]: 'PIR Sensor': Sending state OFF
dev:27232023-01-21 03:44:51.713 PMdebugESPHome received: [type:state, platform:binary, isDigital:false, key:3061631947, state:true, hasState:true]
dev:27232023-01-21 03:44:51.658 PMdebug[D][binary_sensor:036]: 'PIR Sensor': Sending state ON
dev:27232023-01-21 03:44:01.744 PMdebug[C][api:143]: Using noise encryption: NO
dev:27232023-01-21 03:44:01.678 PMdebug[C][api:139]: Address: esphome-sensor.local:6053
dev:27232023-01-21 03:44:01.622 PMdebug[C][api:138]: API Server:
dev:27232023-01-21 03:44:01.556 PMdebug[C][ota:090]: Address: esphome-sensor.local:8266
dev:27232023-01-21 03:44:01.497 PMdebug[C][ota:089]: Over-The-Air Updates:
dev:27232023-01-21 03:44:01.426 PMdebug[C][mdns:101]: Hostname: esphome-sensor
dev:27232023-01-21 03:44:01.335 PMdebug[C][mdns:100]: mDNS:
dev:27232023-01-21 03:44:01.263 PMdebug[C][web_server:126]: Address: esphome-sensor.local:80
dev:27232023-01-21 03:44:01.188 PMdebug[C][web_server:125]: Web Server:
dev:27232023-01-21 03:44:01.041 PMdebug[C][captive_portal:088]: Captive Portal:
dev:27232023-01-21 03:44:00.971 PMdebug[C][gpio.binary_sensor:016]: Pin: GPIO4
dev:27232023-01-21 03:44:00.866 PMdebug[C][gpio.binary_sensor:015]: Device Class: 'motion'
dev:27232023-01-21 03:44:00.741 PMdebug[C][gpio.binary_sensor:015]: GPIO Binary Sensor 'PIR Sensor'
dev:27232023-01-21 03:44:00.649 PMdebugESPHome received: [type:state, platform:binary, isDigital:false, key:3061631947, state:false, hasState:true]
Does it show up in the drop down menu in the configuration section of the driver that says motion entity? It needs to be selected there to know which sensor to use.
no, that is the problem. ive tried 10 different compiles and restarted hub. no matter, only this 'nodemcu' does not present entity. I have 10 others running great and they were set up straight away into HE.
@jonathanb Do you think its a problem with HE version 2.3.4
log shows:
dev:27262023-01-21 08:13:26.249 PMerrorjava.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI on line 1231 (method parse)
@jonathanb Thanks for your help!
BTW: anyone else new to HE esphome, beware of duplicate IP addresses. HE need to get mDNS setup too.
I am looking to monitor current draw in circuits in my house with two Emporia Vue boxes, flashed to ESPHome. I'd like to bring this data to a central location like Hubitat for processing and output.
Has anyone connected this type of setup together, or is an expert and can give pointers? The Emporia Vue looks like the ideal hardware solution to power monitoring. Cheers
Hello, i just stumbled across this thread out of curiosity..since i have Konnected alarm panel.. and they sent an email saying that they will make esphome firmware for esphome for the Konnected panel.. this made me search for esphome with hubitat..and was pleasantly surprised...
I am hoping This would allow me to use my Konnected alarm panel with hubitat and home-assistant directly.. (don't know yet if i can connect to both HA and Hubitat at the same time or not)
I took a quick look at the GitHub repo.. but could not find any smoke or CO device drivers.. is that in the future roadmap? Also what about Sirens/alarm bells?
I have other esp32 devices as well.. but i run them with home assistant and use maker API and HADB.. and so far has been working good..
As like having esphome.. as it has lot of community support.. and with this driver/app.. being able to use esphome devices in hubitat would be great.
Thanks for the drivers/app !!
Hello,
I have emporia Vue.. and have connected it to home-assistant with custom firmware on the emporia Vue ... I had it pass from HA to hubitat using HADB.. but unfortunately the emporia Vue send away too much data (16 circuits , 4-5 params EVERY SECOND) Which bogs down the hubitat hub.. so i disconnected it.. i would assume it would be the same if you connect it directly to hubitat..
My Hubitat hub is normally loaded to 1%.. went to 50-60% constantly.. which made all the other automations etc latent...
So that's why I pass them and monitor them thru a decent hardware in Home assistant.. and use Maker API to get devices into HA..and control automation in HA.. specifically those needing automation related to the power monitoring..
Hope it helps
Download the Hubitat app
