nalkinburgh

I am running into the same issue. The error is slightly different `User input malformed: persistent_notification is not a valid option for dictionary value @ data['include_domains']` I don't even see...

I also found a work around by editing the `.storage/core.config_entities` file as referenced in the comment below. It looks like this has been issue for awhile. https://github.com/custom-components/remote_homeassistant/issues/140#issuecomment-962630699

They were all working last night on 2.2.9 and they all have different names. Regarding the sensor version, I was referring to 2.2.9 because I can downgrade and get it...

Here is more log. Telemetry is not turned off. These worked fine on 2.2.9 and they updated automatically. This one does not have any additional sensors attached. Connected 115200 8N1......

I updated the device to 3.0.2 and continue to have the same problem. rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:1044 load:0x40078000,len:8896 load:0x40080400,len:5828 entry 0x400806ac Setup...

Interestingly I did update one node to 3.0.2 Verbose to see if I got any more information from the logs, and that one has stayed connected. My DHT11 gives no...

I did do that. I serial flashed 3.0.2 on the Kitchen device. That is the last logs I posted. I also did a serial flash with 3.0.2-verbose and oddly that...

I have one, that was not serial flashed just updated, that is status flashing. It will not stay connected. It just keeps trying then connects for less than a minute,...

You can pretty much see all of the bluetooth activity in the logs. I am not sure what you would consider high density. 4 phones, two watches, some bluetooth speakers...

I can check if that is happening on mine, but mine are currently using channel 7 as indicated in the logs.