Fresh Install - Integration not ready yet

[conshy]

Tailwind Hardware Rev: 1.2
Model/FW Ver: IQ3/9.97

Logger: homeassistant.config_entries
Source: config_entries.py:441
First occurred: 2:38:02 PM (1 occurrences)
Last logged: 2:38:02 PM

Config entry 'Tailwind iQ3' for tailwind_iq3 integration not ready yet; Retrying in background

Getting this error. Any ideas?

[farmergreg]

I had the same problem, but then I figured out that I had a firewall rule preventing home assistant from reaching the vlan that the tailwind is in.

[pauln]

@conshy I don't really have any ideas, sorry - other than checking that you've configured the correct IP address and local control key, and that your Home Assistant instance has network access to your Tailwind device (as per @farmergreg's comment).

[pauln]

@conshy I've just released v0.6.0, which removes the need for your Home Assistant instance to be able to perform a MAC address lookup, which had caused problems for some people based on their HA setup (#26). I'm not sure whether that's the underlying cause of your error, but it might be worth trying v0.6.0 to see if it makes a difference.

[Hauslato]

Having an issue adding Tailwind using this integration due to a MAC address lookup issue (tried v0.6.0 and v0.6.1). Confused why this happened considering @pauln last comment about v0.6.0 not requiring a MAC address lookup - any ideas?

P.S. Pretty sure the firewall is not an issue as other devices on the same VLAN as tailwind are working properly with this HA instance.

[pauln]

@Hauslato Since v0.6.x doesn't use a MAC address lookup any more, that does sound strange. How are you installing/updating, and what's giving you the impression that your issue is caused by a MAC address lookup failure?

[Hauslato]

@pauln Thanks a lot for your quick reply.

I receive the following error message: "IP address is invalid (MAC address could not be determined). Please correct it and try again." - this happens in two different HA instances, one was setup fresh. In both cases I first installed 0.6.1 and downgraded in the second step to 0.6.0 (and updated back to 0.6.1) always the same error msg. IP address is correct (Tailwind has a static IP address).

[pauln]

@Hauslato Ah, it looks as though I forgot to remove the bit about the MAC address from the error message. It's most likely that Home Assistant isn't able to successfully make HTTP requests to your Tailwind device for some reason, unless your device is running an unsupported firmware version.

[Hauslato]

Thanks again for your quick reply - that helps a lot and definitely resolves the confusion. Firmware is 9.97, could be a firewall issue, but was overly focussed on the MAC issue as I was sure that FW should be fine.

[pauln]

@Hauslato My Tailwind unit is also running firmware v9.97, so that should definitely be fine.

I suspect there's a new firmware update coming soon, though, as there's a new Tailwind integration set to land in HA 2024.1 (which took me by surprise - I spotted it in the RC release notes; it's based on a completely independent development with hardware sponsored by Tailwind), which requires firmware v10.10. Since I haven't got that firmware update yet, I can't test the new integration, but I wouldn't necessarily expect it to be able to cleanly take over from my custom component (this repo) - so once you've made sure that your HA instance can talk to your Tailwind device, you might want to hold off on setting it up in earnest so that you don't have too much to change to swap dashboards/automations/etc over to the new integration.

HA 2024.1 seems to be scheduled for release on the 3rd of January, but I'm not sure when we might see the firmware update - hopefully there's been enough collaboration between Franck and the folks at Tailwind that it'll be rolled out in concert with (or at least soon after) 2024.1 is released, but if they've got to wait for HomeKit approval before rolling it out, it might be out of their hands...

[pauln]

Now that HA 2024.1 has been released, I checked the Tailwind app (again) and found that it was offering a firmware update, so I went ahead and installed it. My iQ3 is now running v10.10, and I can confirm that the core integration can coexist with this custom one, as they have slightly different names (core is tailwind vs talwind_iq3) and generate different default entity names, so my suggested migration path would be:

• Update Tailwind firmware
• Update to HA 2024.1
• HA should discover your device via the core integration; go ahead and add it (you'll need your Local Control Key, but nothing else)
• Migrate all dashboards, automations, etc to use the new entities provided by the core integration
• Remove the custom integration once you're satisfied that everything's working as desired via the core integration

[Hauslato]

Thanks @pauln for your suggestion above.

Can confirm: FW 1.10 on Tailwind plus 2024.1 works and actually resolved the issues I had as described above (without changing anything else). I can also run both integrations in parallel.