jpmens/homie-ota

V2 (beta) homie - device not registering

Closed this issue · 7 comments

I've just been playing with homie, and to that end installed homie-ota.
The server is up and running and I connect to it with a browser.

I had the understanding that running device would show up in the site. Is that correct?

if your homie-ota is configured correctly and is watching the right base topic, and your devices are configured with the same base topic, then yes you should see the devices appearing in the homie-ota web UI.

So here's my device:
sensors/d1mini/mqtt-test/
The base topic is sensors/d1mini - mqtt-test being my first device.

Ahh found it, right down the bottom of the ini wat the topic base of devices.....Showing up now.

Though I can't update, device gets a WDT reset and locks up....wondering if there's something weird with the physical connection to the DHT22 sensor I;m running (not a shield)

Not sure if a new issue or not, but similar.
I had some homie-python scripts https://github.com/jalmeroth/homie-python and they were not showing up. These were on sensors/bluemaestro//temperature and sensors/dht//temperature

When I altered the homie-ota.ini and set the ota path/mqtt path to sensors (from sensors/d1mini) the bluemaestro one turned up and I see this:
2017-11-15 11:25:59,321 DEBUG CONTROL sensors/bluemaestro/$uptime 180
2017-11-15 11:25:59,324 DEBUG CONTROL sensors/bluemaestro/$signal 61

But the DHT ones don't seem to:
2017-11-15 11:35:37,932 DEBUG SENSOR sensors/dht/brmaster/$uptime 0
2017-11-15 11:35:37,936 DEBUG SENSOR sensors/dht/brmaster/$signal 67

Is there something in the path I have wrong for the subscribed message for figuring out is a "device" is homie or not?

It must be the length of the path
The working one is 3 to the $signal/update, the non working is 4 to $signal/update. But I can't see where in the code that is the issue.

Can we close this?

Given no activity, may as well.