Linkplay-based speakers and devices unvailable about home-assistant-custom-components-linkplay

[nagyrobi]

What do you see in your logs? Do you use DHCP IP address reservation for your devices? They must be on the same address always.

I also run Home Assistant 2021.9.7, they are perfect.

[lajehome]

Hi, I don't see anything in my logs. Just see this warning but have seen it since first installation: WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration linkplay which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant Yes, They have up reservation and they are in the same network segment. Can I activate some logs to see what's happening? Regards, A terça, 21/09/2021, 17:17, H. Árkosi Róbert ***@***.***> escreveu:

…

What do you see in your logs? Do you use DHCP IP address reservation for your devices? They must be on the same address always. I also run Home Assistant 2021.9.7, they are perfect. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#51 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTUILCB7MKSI6C2YZC47OLUDCV2JANCNFSM5EOP67YA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[nagyrobi]

Go to your entities list, see aren't tghey there under a different entity id?

Perhaps add to your config:

logger:
  logs:
    custom_components.linkplay: debug

[lajehome]

Hi, Yes, I already put that configuration and nothing. I think it's the speakers. I have three speakers and only two are not working. Can't see why. I will remove everything and reconfigure again to see if it works. But definitely it's not the integration. Thanks for your help. If you have any ideas please let me know :). I'm completely in the dark right now. Regards,

…

On Tue, Sep 21, 2021 at 6:30 PM H. Árkosi Róbert ***@***.***> wrote: Add to your config: logger: logs: custom_components.linkplay: debug — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#51 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTUILHT54AWWE7TJBFUBMTUDC6LTANCNFSM5EOP67YA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Cumpimentos, João Alves

[lajehome]

Hi, I think the problem it's the firmware from the speakers. Is the only difference I see. On the two speakers I have (KS Kitsound) the firmware is 4.2.327555.37 and the build date is 20210827. The speaker it's working on (GGMM-E5) has the firmware 4.2.8506.1 and the build date is 20200706. I don't know how to solve this :/. Regards, João Alves

…

On Tue, Sep 21, 2021 at 6:55 PM João Alves ***@***.***> wrote: Hi, Yes, I already put that configuration and nothing. I think it's the speakers. I have three speakers and only two are not working. Can't see why. I will remove everything and reconfigure again to see if it works. But definitely it's not the integration. Thanks for your help. If you have any ideas please let me know :). I'm completely in the dark right now. Regards, On Tue, Sep 21, 2021 at 6:30 PM H. Árkosi Róbert ***@***.***> wrote: > Add to your config: > > logger: > logs: > custom_components.linkplay: debug > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#51 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AQTUILHT54AWWE7TJBFUBMTUDC6LTANCNFSM5EOP67YA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > -- Cumpimentos, João Alves

-- Cumpimentos, João Alves

[nagyrobi]

Where do you see the firmware version?

Check http://DEVICE_IP/httpapi.asp?command=getStatusEx what's the result?

[lajehome]

Hi, I see it in the app from the speaker's. I sent you in attach a print screen. Regards, João Alves A terça, 21/09/2021, 20:54, H. Árkosi Róbert ***@***.***> escreveu:

…

Where do you see the firmware version? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#51 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTUILHKKNPK5JNVSFVAI7LUDDPGVANCNFSM5EOP67YA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[nagyrobi]

Post it here, as text. Replace sensitive data with XXXX...

[lajehome]

Hi, In the speaker ((GGMM-E5)) that is working I have data retrieve from the device. The two speakers ( KS Kitsound) that aren't working I can't get the data because it gives me "ERR_CONNECTION_REFUSED". Regards, João Alves A terça, 21/09/2021, 21:29, H. Árkosi Róbert ***@***.***> escreveu:

…

Post it here — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#51 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTUILHX7QQIKAZFUVJOFUTUDDTJVANCNFSM5EOP67YA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[lajehome]

Hi, Do you think it could be because of this that the device doesn't respond to the http query? https://labs.f-secure.com/advisories/linkplay-firmware-wanlan-remote-code-execution/ Regards, João Alves

…

On Wed, Sep 22, 2021 at 11:19 AM João Alves ***@***.***> wrote: Hi, In the speaker ((GGMM-E5)) that is working I have the data below. { "language": "en_us", "ssid": "GGMM_E5_xxxx", "hideSSID": "0", "SSIDStrategy": "0", "firmware": "4.2.8506", "build": "release", "project": "GGMMA31_E5A", "priv_prj": "GGMMA31_E5A", "project_build_name": "a31ggmmalexa", "Release": "20200706", "branch": "stable\/wiimu-4.2", "group": "0", "expired": "0", "internet": "1", "uuid": "FF310080D51204815513xxxx", "MAC": "00:22:6C:F2:xx:xx", "STA_MAC": "00:22:6C:F2:xx:xx", "CountryCode": "CN", "CountryRegion": "1", "date": "2021:09:22", "time": "10:07:50", "tz": "0.000000", "dst_enable": "1", "netstat": "2", "essid": "4C414A45486F6xxx", "apcli0": "192.168.xxx.xxx", "eth2": "0.0.0.0", "hardware": "A31", "VersionUpdate": "0", "NewVer": "0", "mcu_ver": "1", "mcu_ver_new": "0", "dsp_ver_new": "0", "ra0": "10.10.10.254", "temp_uuid": "89503FE6A06E3xxx", "cap1": "0x1000", "capability": "0x28c84000", "languages": "0x4", "alexa_ver": "20180xxx", "dsp_ver": "0", "streams_all": "0x7ffffffe", "streams": "0x7ffffffe", "region": "unknown", "external": "0x0", "preset_key": "6", "plm_support": "0x0", "spotify_active": "0", "lbc_support": "0", "WifiChannel": "6", "RSSI": "-65", "battery": "0", "battery_percent": "0", "securemode": "1", "auth": "WPAPSKWPA2PSK", "encry": "AES", "psk": "70714D464C3179345474797979584A566A4D496E39684536494372505752553150662B655A70782F624Bxxxx", "ali_pid": "EDIFIER_ENTERTAINMENT_ATALK_MA1", "ali_uuid": "", "iot_ver": "1.0.0", "upnp_version": "1005", "upnp_uuid": "uuid:FF310080-D512-0481-5513-C442FF31xxxx", "uart_pass_port": "8xxx", "communication_port": "8xxx", "web_firmware_update_hide": "0", "web_login_result": "-1", "ignore_talkstart": "0", "silenceOTATime": "", "ignore_silenceOTATime": "1", "new_tunein_preset_and_alarm": "1", "iheartradio_new": "1", "new_iheart_podcast": "1", "security": "https\/2.0", "security_version": "2.0", "privacy_mode": "0", "user1": "315:xxx", "user2": "1896:xxxx", "DeviceName": "ColunaMovel", "GroupName": "ColunaMovel" } The two speakers ( KS Kitsound) that aren't working I can't get the data because it gives me "ERR_CONNECTION_REFUSED". Regards, João Alves A terça, 21/09/2021, 21:29, H. Árkosi Róbert ***@***.***> escreveu: > Post it here > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#51 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AQTUILHX7QQIKAZFUVJOFUTUDDTJVANCNFSM5EOP67YA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > >

-- Cumpimentos, João Alves

[nagyrobi]

Hi, In the speaker ((GGMM-E5)) that is working I have data retrieve from the device. The two speakers ( KS Kitsound) that aren't working I can't get the data because it gives me "ERR_CONNECTION_REFUSED".

Yes that's the reason. Http api protocol is broken on those speakers. Unplug from power, replug doesn't fix it?

[lajehome]

Hi, No. And I have reset it and dind't fix it. There is another way to retrieve the data from the speakers (another API form)? I think that if all the speakers upgrade ther firmware the API will not work. Regards, João Alves

…

On Wed, Sep 22, 2021 at 1:20 PM H. Árkosi Róbert ***@***.***> wrote: Hi, In the speaker ((GGMM-E5)) that is working I have data retrieve from the device. The two speakers ( KS Kitsound) that aren't working I can't get the data because it gives me "ERR_CONNECTION_REFUSED". Yes that's the reason. Http api protocol is broken on those speakers. Unplug from power, replug doesn't fix it? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#51 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQTUILCBTY7KHVGYQ7ME2LTUDHCXPANCNFSM5EOP67YA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Cumpimentos, João Alves

[nagyrobi]

Our Arylic players have firmware v4.6.328252.24 dated 20210903 and they work just fine with the supported http api.

You should contact the speaker manufacturer to provide you with a fixed firmware.