Open dooniem opened 6 months ago
Thanks for reporting your issue. Unfortunately I don't have time to deep dive very soon. It looks from your log like Homey can't resolve the mDNS address to an IP:
2024-02-08T19:33:10.399Z epo:client error: { '$__type': 'Error', data: { message: 'getaddrinfo ENOTFOUND sensor2-fc3950.local', code: 'ENOTFOUND', stack: 'Error: getaddrinfo ENOTFOUND sensor2-fc3950.local\n' + ' at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:66:26)' } }
Could you verify that this also happens in the listed supported firmware versions, or only with 1.1.9?
Hmm. I will try to install an earlier version. But I dropped my Presence One on the floor yesterday. So after creating the issue, I opened the casing and pushed the mmSensor a few millimeters in to its slot. Now Homey report it as connected. But I can't read any values yet. 5 minutes in. There's still a red light flashing on the sensor....So maybe it's a bit hard for you to deep dive...
I have 2 sensors, and both have always been hard to discover on my Asus network. So it can be network related too as you mention. My second sensor is running on MQTT on a custom firmware from ages ago. But eventually I guess I'll have to test with that one to confirm the other is not broken...
I downgraded by just flashing the 1.1.6 firmware and entering my wifi in the yaml before upload. [I][app:102]: ESPHome version 2023.10.6 compiled on Feb 8 2024, 21:39:23 [I][app:104]: Project Everything_Smart_Technology.Everything_Presence_One version 1.1.6
Now Homey can't find any devices to add. The log says it's connected to my Wifi.
Not sure if much can be seen in the app-log, but here's the key: dc54f8c9-48f0-48c7-835d-2ab0350324a9
Hm no sorry, the log is pretty empty. Hard to troubleshoot remotely, but my first guess would a local (m)DNS issue on your network.
Hi! Could you have a look and see if your implementation can handle V1.1.9? My Homey 2019 can find it, but it lists as offline.
705235f2-37e4-495d-8256-9af979f858b5