Hello - I’ve been using Bruh’s multi sensor perfectly OK for several months. After leaving the sensor unplugged for several week (was renovating a room), I decided to plug it back in, with no results in HA.
After weeks of not caring much about it, I decided to redo my HA config. Installed a fresh instance of Hass.IO and everything seems to be working quite well, except for this multi sensor.
I have re-done the setup at least 5 times, reloading the code to the NODEMCU. I’ve also tried 2 different boards, with no luck.
The state values in HA come up as unknown. The strange thing is, I can “somewhat” control the LED. The physical LED turns on BLUE when I plug in the sensor. HA shows the LED as off. When I click it ON, the light changes to WHITE and HA shows it is off however HA allows me to adjust the brightness of the WHITE light.
PIR, Temp/Humidity all show as UNKNOWN.
My SETUP is HASS.IO
- using the MQTT Add On, I have a cloud.conf file in the share/mosquitto folder for CloudMQTT/Owntracks
config.yaml:
mqtt:
broker: 172.17.0.1
MQTT Add On shows the following in the logs:
1507831655: New client connected from 192.168.1.137 as sensor1 (c1, k15…
I named my sensor sensor1
I’ve tried connecting it to CLOUDMQTT with no luck, and I read online on some forum that the OTA setup could be causing an issue. Someone commented it out, and got it working.
I’ve, triple checked the max packet size 512 setting in pubsubclient.h file.
I feel as though this could be something very simple or very complicated. Either way, I’m out of idea but continuing to fiddle around with settings.
Any help would be greatly appreciated.