Home assistant not showing?

[Rabbit1543]

Question on what to expect in home assistant if the device is not yet hooked up to an Daikin unit. Via MQTT Explorer I can see the topics for the 2 faikins esps I'm testing in to root, but they do not show anything under the home assistant topic.

[revk]

My sure as I have not tried that, but may be very limited.

[wurmtal868]

My remaining modules arrived yesterday and I tried configuring one of them with lab-bench supply.
I was able to set up WiFi and MQTT and after a reboot the module showed "MQTT connected" and "System is offline".
Nothing is visible in Home Assistant. I can only see one topic being sent through MQTT:

Now comes the strange part. Even when I plug this module into my indoor unit, I get this:

And when I try to update the FW I get an OTA error:

I'm not sure if this related to the set up, but it is very strange.
MQTT is connected but the module can't connect to the update server?

4 other modules, which I set up connected to an indoor unit, are working fine. Only the module below shows "System is offline" and can't update via OTA?

[revk]

System off line could simply be a faulty module I guess, though I do check them before they are shipped.

The failure to update is rather odd. Can you confirm date/time when it tried and I'll check the web server logs. Ideally what IP you would be coming from as well, if you can.

[wurmtal868]

How can I get to the web server logs?

[revk]

I mean I would check my web server logs for your Faikin trying to access the update, and see if anything looks odd.

[wurmtal868]

My IP was 92.192.130.223 when sending the OTA request.

[wurmtal868]

VS-Code is installing

[revk]

But given no serious error from serial, it either should be on wifi and so available on a web config, or not, so making an access point. It should be possible to get it on MQTT from either.

[wurmtal868]

I don't see an AP nor is the module connecting to my WiFi. I guess something is completely messes up in the ROM. Probably the package was x-rayed while shipping form amazon-uk to Germany.

[wurmtal868]

When I run idf.py monitor I get an an error:

[revk]

You did a --recursive clone, yes?

If not, try make update

[wurmtal868]

I did just git clone htpps: ...
trying again with recursive....

[wurmtal868]

Where do I get partition_table, ota_data_initial bin and build/Faikin.bin?

[revk]

I said the Faikin.bin will be the S3 one in the realise. The others should be there, or a make should create them.

[wurmtal868]

Tried this command
esptool.py -p /dev/ttyACM0 -b 460800 --before default_reset --after hard_reset --chip esp32s3 write_flash --flash_mode dio --flash_size keep --flash_freq 40m 0x0 release/Faikin-S3-MINI-N4-R2-bootloader.bin 0x8000 build/partition_table/partition-table.bin 0xd000 build/ota_data_initial.bin 0x10000 release/Faikin-S3-MINI-N4-R2.bin

[revk]

Did that now work.

If not, try idf.py erase_flash

Then flash it again.

[wurmtal868]

It's working :-) :-)
I could not find because it remained the WiFi credentials and picked up an IP which I which I thought was assigned to different module. My router even named it after the other module.

Thanks for helping me with fixing the module

[revk]

Just to be clear, this normally "just works". I am really puzzled how anything from your IP would try to get Faikin-8266 as that is not something that should ever try to upgrade from my server, not even the 8266 build (which someone else has made). Not being on WiFi and not doing an AP is not normal either, but no obvious error from the serial log. Almost like it has been flashed with some wrong code somehow. Having to "recover" is not something normally needed.

If all else fails, I'll try and sort a full binary image and a simple esptool command to flash from scratch. A recovery mode of sorts. That should be doable. But probably won't be until morning.

But may not reply much until then.

[wurmtal868]

Wait there is one thing that could cause the ESP8266 request.
Before I got the first module from amazon-UK I was playing with the ESP8266 fork on a Wemos-D1mini. Maybe this module was trying to use your OTA server. I forgot about his module and it was still plugged into my system until I used the cable to debug the bad module.

[wurmtal868]

After fixing the module, I checked again if it gets detected in Home Assistant without being connected to an AC unit.
The result is same as before, Home Assistant will not detect the MQTT device until it was successfully connected to an indoor unit.

[revk]

Ok that is not surprising to be honest. The settings it offers HA all depend on what it "sees" as available via the S21 link to the aircon.

So, all good now?

[wurmtal868]

I'm all good now.
Thanks a lot.

BTW: You just triggered another 50€ invest in BLE sensors, as I saw that you added locking of heat/cold modes :-)
You even showing it as automatic mode in Home Assistant and BLE temperature

Thanks for the great support!

[wurmtal868]

FYI I powered up my D1-mini. If you see now see incoming ESP8266 OTA request you should contact the owner of the 8266-fork.

[revk]

Yeh, may have to have a word over their defaults!

[revk]

And well done, sorting things!

[wurmtal868]

That was me, I will retire the module now, as it caused a lot of confusion when debugging the other module.

[wurmtal868]

Again thanks a lot for helping me fixing my module!
I will recommend your modules to my friends.
There are at least 10 more units that are waiting to be freed from the Daikin Cloud :-)

Having the auto mode with remote sensing is a lot better than anything Daikin has to offer with their cloud!

[revk]

Stock on Amazon is OK, but planning on sending a load more next week.