To avoid confusion this was my original idea: https://esphome.github.io/media-players/. To load this firmware onto the device and get it directly connected and managed in Home Assistant with ESPHome. This new device does not have a firmware for this purpose so I will for now use LMS and see how that works, just as you suggest 
@cOOLio thanks for your super precise review!
To answer to some of your questions :
-Black screen connector was hand re-worked on this batch because it was 3mm higher than the specification, so it was not fitting into the case anymore, althought it does not affect useability it will be fixed on the the production batch.
-The choice to leave a microphone extension port is for my secret plan to one day have the Home Assistant working as an open source vocal assitant.
-The IR and SD costs almost nothing to implement, and it could be usefull in some application other than Squeezelite, but I agree you only see SD on the cheapest mp3 players.
@sbarmen I plan that my intern will do a website where you can load all the last firmware for Squeezelite, HA and others using the Chrome browser.
Also Louis is currently working on adding Wifi Improv to Squeezelite to be able to set wifi credential from the Chrome bowser like the genius of HA did for their software.
My talented contacts at HA told me that they will add the MN cast soon in HA, but I have no date to give you.
1 Like
Ok so now I have tried to follow ur lead in the blog @cOOLio. Flashed the recovery, then the 1.x version and now the player connects and works with bluetooth. Still I cannot get the display to function, and it is unclear to me whether I should upgrade to the 2.x release again. You say the OTA upgrades works again, did you upgrade?
This is my display config in the NVEeditor:
I use V1. 32.1180
Display disappeared after upgrade (many NVS entries were lost) so I changed NVS to same setting as you use.
I found I had to reboot ESP32 for some changes to take effect.
I did a quick test of IR port (configured set_GPIO 12=ir) and I couldnât get it to work with a SB remote.
Boot log message show IR device is recognised but no log messages (e.g. message sent to LMS) shown when using remote.
current Squeezelite code I think only recognize NEC remote protocol, I have configured my Xiaomi phone that has a IR emitter to NEC and I think got some logs back when pressing the remote.
Sadly reboot does not help here. 
The README on the GIT hub sites says
âThe IR codes are send âas isâ to LMS, so only a Logitech SB remote from Boom, Classic or Touch will work.â
so I assume my SB3 (aka classic) and Boom remotes should work.
I shall look for other issues and see if I can get more log info.
What version of V1 - 32 vs 16 and build.
Can you export your NVS config and post/link it to check - in case there is some other difference - a number of NVS entries were lost in upgrade not just the display config but I canât remember which ones.
edit
My config
{
âa2dp_ctmtâ: â1000â,
âa2dp_ctrldâ: â500â,
âa2dp_dev_nameâ: âMuseâ,
âa2dp_sink_nameâ: âSMSL BT4.2â,
âa2dp_spinâ: â0000â,
âactrls_configâ: ââ,
âairplay_nameâ: âMuse-Airplay-xxxxâ,
âairplay_portâ: â5000â,
âap_channelâ: â1â,
âap_ip_addressâ: â192.168.4.1â,
âap_ip_gatewayâ: â192.168.4.1â,
âap_ip_netmaskâ: â255.255.255.0â,
âap_pwdâ: âmusemuseâ,
âap_ssidâ: âMuse-xxxxâ,
âautoexecâ: â1â,
âautoexec1â: âsqueezelite -o I2S -b 500:2000 -d all=info -C 30 -W -n âMuse-xxxxââ,
âbat_configâ: ââ,
âboutonsâ: ââ,
âbt_nameâ: âMuse-xxxxâ,
âbt_sink_pinâ: â1234â,
âbt_sink_volumeâ: â127â,
âbypass_wmâ: â0â,
âdac_configâ: âbck=5,ws=25,do=26,sda=18,scl=23,model=Museâ,
âdac_controlsetâ: ââ,
âdisplay_configâ: âI2C,width=128,height=64,address=60,driver=SH1106,rotateâ,
âenable_airplayâ: âNâ,
âenable_bt_sinkâ: âNâ,
âequalizerâ: â0,0,0,0,0,0,0,0,0,0â,
âeth_configâ: ââ,
âgpio_exp_configâ: ââ,
âhost_nameâ: âMuse-xxxxâ,
âi2c_configâ: âscl=23,sda=18,speed=400000,port=0â,
âjack_mutes_ampâ: ânâ,
âled_brightnessâ: ââ,
âlms_ctrls_rawâ: ânâ,
âmetadata_configâ: ââ,
âota_erase_blkâ: â249856â,
âota_prioâ: â6â,
âota_stackâ: â10240â,
ârel_apiâ: âhttps://api.github.com/repos/sle118/squeezelite-esp32/releasesâ,
ârelease_urlâ: âhttps://github.com/sle118/squeezelite-esp32/releasesâ,
ârotary_configâ: âA=32,B=19,SW=0,volume,knobonlyâ,
âset_GPIOâ: â12=irâ,
âspdif_configâ: âbck=5,ws=25,do=4â,
âspi_configâ: ââ,
âstatsâ: ânâ,
âtargetâ: ââ,
âtelnet_blockâ: â500â,
âtelnet_bufferâ: â40000â,
âtelnet_enableâ: âDâ,
âwifi_smodeâ: âfâ
}
Thanks, there are differences for sure!
nosb@no-osl-stba diff % diff -y nvs_config_Yamaha-Muse_1664970559982json.txt bpa.txt
{ {
"a2dp_ctmt": "1000", | âa2dp_ctmtâ: â1000â,
"a2dp_ctrld": "500", | âa2dp_ctrldâ: â500â,
"a2dp_dev_name": "Muse", | âa2dp_dev_nameâ: âMuseâ,
"a2dp_sink_name": "SMSL BT4.2", | âa2dp_sink_nameâ: âSMSL BT4.2â,
"a2dp_spin": "0000", | âa2dp_spinâ: â0000â,
"actrls_config": "", | âactrls_configâ: ââ,
"airplay_name": "Yamaha-Muse-Airplay", | âairplay_nameâ: âMuse-Airplay-xxxxâ,
"airplay_port": "5000", | âairplay_portâ: â5000â,
"ap_channel": "1", | âap_channelâ: â1â,
"ap_ip_address": "192.168.4.1", | âap_ip_addressâ: â192.168.4.1â,
"ap_ip_gateway": "192.168.4.1", | âap_ip_gatewayâ: â192.168.4.1â,
"ap_ip_netmask": "255.255.255.0", | âap_ip_netmaskâ: â255.255.255.0â,
"ap_pwd": "musemuse", | âap_pwdâ: âmusemuseâ,
"ap_ssid": "Yamaha-Muse", | âap_ssidâ: âMuse-xxxxâ,
"autoexec": "1", | âautoexecâ: â1â,
"autoexec1": "squeezelite -o I2S -b 500:2000 -d all=info -C | âautoexec1â: âsqueezelite -o I2S -b 500:2000 -d all=info -C 3
"bat_config": "", | âMuse-xxxxââ,
"boutons": "", | âbat_configâ: ââ,
"bt_name": "Yamaha-Muse", | âboutonsâ: ââ,
"bt_sink_pin": "1234", | âbt_nameâ: âMuse-xxxxâ,
"bt_sink_volume": "127", | âbt_sink_pinâ: â1234â,
"bypass_wm": "0", | âbt_sink_volumeâ: â127â,
"dac_config": "bck=5,ws=25,do=26,sda=18,scl=23,model=Muse", | âbypass_wmâ: â0â,
"dac_controlset": "", | âdac_configâ: âbck=5,ws=25,do=26,sda=18,scl=23,model=Museâ,
"display_config": "I2C,width=128,height=64,address=60,drive | âdac_controlsetâ: ââ,
"enable_airplay": "1", | âdisplay_configâ:
"enable_bt_sink": "1", | âI2C,width=128,height=64,address=60,driver=SH1106,rotateâ,
"equalizer": "00,00,00,00,00,00,00,00,00,00", | âenable_airplayâ: âNâ,
"eth_config": "", | âenable_bt_sinkâ: âNâ,
"host_name": "Yamaha-Muse", | âequalizerâ: â0,0,0,0,0,0,0,0,0,0â,
"i2c_config": "", | âeth_configâ: ââ,
"jack_mutes_amp": "n", | âgpio_exp_configâ: ââ,
"led_brightness": "", | âhost_nameâ: âMuse-xxxxâ,
"lms_ctrls_raw": "n", | âi2c_configâ: âscl=23,sda=18,speed=400000,port=0â,
"metadata_config": "", | âjack_mutes_ampâ: ânâ,
"ota_erase_blk": "249856", | âled_brightnessâ: ââ,
"ota_prio": "6", | âlms_ctrls_rawâ: ânâ,
"ota_stack": "10240", | âmetadata_configâ: ââ,
"rel_api": "https://api.github.com/repos/sle118/squeezelite | âota_erase_blkâ: â249856â,
"release_url": "https://github.com/sle118/squeezelite-esp32 | âota_prioâ: â6â,
"rotary_config": " A=32,B=19,SW=0,volume,longpress", | âota_stackâ: â10240â,
"set_GPIO": "", | ârel_apiâ:
"spdif_config": "", | âhttps://api.github.com/repos/sle118/squeezelite-esp32/releas
"spi_config": "", | ârelease_urlâ: âhttps://github.com/sle118/squeezelite-esp32/r
"stats": "n", | ârotary_configâ: âA=32,B=19,SW=0,volume,knobonlyâ,
"telnet_block": "500", | âset_GPIOâ: â12=irâ,
"telnet_buffer": "40000", | âspdif_configâ: âbck=5,ws=25,do=4â,
"telnet_enable": "", | âspi_configâ: ââ,
"wifi_smode": "f" | âstatsâ: ânâ,
} \ âtargetâ: ââ,
> âtelnet_blockâ: â500â,
> âtelnet_bufferâ: â40000â,
> âtelnet_enableâ: âDâ,
> âwifi_smodeâ: âfâ
> }Now my display is back on! Not sure what settings changed it but I added the spdif_config, set_GPIO, changed the equalizer I think. At least that lit the display back up 
Thanks!
Check this NVS backup
There are also backups of others players I own already. So choose the right one.
Itâs only the config of the hardware of the Mn Cast, noting else will changed.
@NVS Editor
- [ Load file ] (choose NVS json backup file)
- [ Commit ]
- [ Reboot ]
Then all the hardware should work again.
Additional enhancements I added to NVS Backup file:
- Volume Control +Long Press > Play/Pause Prev./Next | Long press again to get back to volume control
- Display is flipped so that the IR holes are at front and the display can still be read normally.
- Medieval IR enabled
@Raspiaudio
THX for those background info. Donât know which fabric your partner is, but it seems they have some quality issues. Maybe Makerfabs (Open Hardware OEM is there main business) could be an alternative, or to make more pressure to your current partner. 
Regarding the faulty display, I still have to think what could be the best solution,
so that the environment is not unnecessarily polluted because of such a small OLED display.
Maybe you can think of a solution on this for the environment as well.
But Iâll send you an email about that when I have more time and after the white one has arrived and been briefly tested.
Cheers
cOOLio
I think the missing setting was i2c_config. The i2c bus can use different ESP32 pins. This tells the ESP32 which pins are to be connected to device SDA & SCL. I think the DAC and display share the bus on Mn Cast.
The i2c config settings usually change with different boards depending on how the board has been designed.
@bpa this dac does not need i2c, it is only using I2s
@cOOLio do you refer as âquality issueâ the shorter than expected screen connector it is not, just a specification of a component that differs from what you receive, it happens. This is why Iâm doing pre-serie. Thanks for your help.
No No, thatâs fine for me. I mean the faulty screen itself only. All the rest is fine for me.
you are both right @pba @Raspiaudio but IMHO you are talking on different things.
Yes, the DAC does not need any additional settings to get activated, send via I2C (dac_controlset).
And Yes, the OLED Display needs also the right I2C settings (i2c_config) to work.
Regarding IR anyone have a Logitech remote to see if you have any logs when pressing a button?
Using an a simple Arduino sketch I can receive any code from any remote, so I think the hardware is fine. But in Squeezelite (quoting Philippe git) âonly a Logitech SB remote from Boom, Classic or Touch will work. I think the file Slim_Devices_Remote.ir in the âserverâ directoryâ
So on the server side maybe the key is to add new codes if you donât have a Logitech remote.
I need to try.
Iâve got an -quite- old squeezbox radio with its remote. Probably not the same sets of IR signal than Boom, Classic or Touch. Made some tests : no action on Mn Cast
Regarding IR, Iâve made some test it seems that by default the Squeezelite software is activating an internal pull down on the Gpio 12, so the IR signal coming to the ESP32 is attenuated. Compared to a test arduino sketch Iâm using for infra red that is at the right level and decodes it right.
tried in the editor to activate the intenal pull up but still no change on the gpio :
is it the correct syntax?