Parkside lawn mower PMRDA 20-Li A1

[tkrynicki]

Hi,
any ideas for Parkside lawn mower PMRDA 20-Li A1 support ?
https://www.lidl.de/p/parkside-20-v-smart-maehroboter-pmrda-20-li-a1/p100325200
I found isssue added but already deleted:

[make-all]

The was deleted at the request of the submitter. I assume they would submit a new request without whatever information they were concerned about, but it seems they didn't.

[tkrynicki]

How can I support you to make this device integrated? If it's possible?

[make-all]

Based on the previous information given, it is very similar to the Moebot S that is already supported, and a minor tweak to that config should make it compatible.
Commit bf67175 should be enough to get it working.

[make-all]

Please include the log message from when you attempt to add the device if you still cannot add it using the "main" development version (which you can install through HACS using the Redownload option)

[TadFocus]

Hello, here is it.
"6" is battery sensor in %
"101" is state (STANDBY, MOWING, PARK, ERROR, etc.)
"106" is PIN code
another I don´t know.

`{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2023.5.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.10.11",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/Prague",
"os_name": "Linux",
"os_version": "6.1.29",
"supervisor": "2023.04.1",
"host_os": "Home Assistant OS 10.2",
"docker_version": "23.0.6",
"chassis": "embedded",
"run_as_root": true
},

"localtuya": {
  "version": "5.2.0",
  "requirements": []
},

"integration_manifest": {
"domain": "localtuya",
"name": "LocalTuya integration",
"codeowners": [
"@rospogrigio",
"@postlund"
],
"config_flow": true,
"dependencies": [],
"documentation": "https://github.com/rospogrigio/localtuya/",
"iot_class": "local_push",
"issue_tracker": "https://github.com/rospogrigio/localtuya/issues",
"requirements": [],
"version": "5.2.0",
"is_built_in": false
},
"data": {
"device_config": {
"friendly_name": "Robotick\u00e1 seka\u010dka na tr\u00e1vu PMRDA 20-Li A1",
"host": "192.168.1.197",
"device_id": "bf7adXXXXXXXXXXXXX5j6pd",
"local_key": ")z7b]-;oUXXXXXXXXX",
"protocol_version": "3.3",
"enable_debug": false,
"model": "Robot lawn mower PMRDA 20-Li A1",
"dps_strings": [
"6 (value: 100)",
"101 (value: STANDBY)",
"102 (value: 0)",
"103 (value: MOWER_LEAN)",
"104 (value: True)",
"105 (value: 3)",
"106 (value: 4444)",
"116 (value: False)"
],
"entities": [
{
"id": 101,
"friendly_name": "PMRDA stav",
"platform": "sensor"
},
{
"id": 6,
"friendly_name": "PMRDA stav baterie",
"device_class": "battery",
"platform": "sensor"
}
],
"product_key": "XXXXXXXXXXXXXXXX"
},
"device_cloud_info": {
"active_time": 1684157417,
"biz_type": 0,
"category": "gcj",
"create_time": 1684156377,
"icon": "smart/icon/ay1559701439060fw6BY/cd5d1eb275462c33b3ea5f52672fe535.png",
"id": "XXXXXXXXXXXXXXXXXXXXXX",
"ip": "XX.XX.XX.XX",
"lat": "57.0300",
"local_key": "XXXXXXXXXXXXXXXX",
"lon": "19.2600",
"model": "",
"name": "Robotick\u00e1 seka\u010dka na tr\u00e1vu PMRDA 20-Li A1",
"online": true,
"owner_id": "XXXXXXXX",
"product_id": "icw5XXXXfcevsve",
"product_name": "Robot lawn mower PMRDA 20-Li A1",
"status": [
{
"code": "battery_percentage",
"value": 100
}
],
"sub": false,
"time_zone": "+02:00",
"uid": "euXXXXXXXXXXXXXrrAwA",
"update_time": 1685876820,
"uuid": "7724dfba1f012984"
}
}
}`

[tkrynicki]

Is possible to decode ex. "112" - Work log: ZH7jNAAABEkBZH4zQwAACHIBZH4KWwAAGEcBZHtxhgAAAJ4BZHs2GQAAKSYBZHsyZAAAADwBZHdxUwAAB0oBZHYggAAAGSEBZHTOyQAALSsBZHS+DgAAB7gB ?
"111" Error log:
ZH7rFxZkfju1FmR+I/kUZH4jzhZke3IkFGR7MpEVZHsyiBhkd3imFWR3eKMCZHd4nhQ=

I see also not supported option: "116" i have value: false

And in smart app Error log can have states ex. Tapperd, lifted, upside down

[tkrynicki]

I'm wonder if error log: ZH7rFxZkfju1FmR+I/kUZH4jzhZke3IkFGR7MpEVZHsyiBhkd3imFWR3eKMCZHd4nhQ=
Is hashed time stamp with error text messages.
It should be 2023/06/05 19:47:01 trapped
If I correctly investigated.

[make-all]

It looks base64 encoded. There are online base64 decoders to test this theory.
But in general, base64 encoded fields can be binary data, so are only decoded when there is a specific use case where they are handled. Using them to encode text is a bit strange, because it just makes the text hard to read and increases the size overhead.

[make-all]

It appears to be valid base64, but decodes to binary, so I think it is not a text log but some sort of binary log (perhaps compressed)

[Peck07]

I know it's an old thread, but maybe helps:
error log
ZH7rFxZkfju1FmR+I/kUZH4jzhZke3IkFGR7MpEVZHsyiBhkd3imFWR3eKMCZHd4nhQ= decodes to:
64 7e eb 17 16
64 7e 3b b5 16
64 7e 23 f9 14
64 7e 23 ce 16
64 7b 72 24 14
64 7b 32 91 15
64 7b 32 88 18
64 77 78 a6 15
64 77 78 a3 02
64 77 78 9e 14
divided to 10 segments, because mower stores apparently the last 10 errors.
647EEB17 in decimal is 1,686,039,319 epoch, which is GMT: 2023. June 6., Tuesday 8:15:19,
16, 14, 18, 02 are probably the error codes.

Similarly, if you base64 decode ZH7jNAAABEkBZH4zQwAACHIBZH4KWwAAGEcBZHtxhgAAAJ4BZHs2GQAAKSYBZHsyZAAAADwBZHdxUwAAB0oBZHYggAAAGSEBZHTOyQAALSsBZHS+DgAAB7gB worklog, you get 10 records, the first:
64 7e e3 34 00 00 04 49 01 - first 4 bytes are again the epoch, 00 00 is probably a filler (or used for longer mow times, didn't do the math), 0449 in decimal is 1097, that's how many seconds it mowed, 01 is probably an indicator for automatic mowing.

[stefangries]

I just tried the main-branch of this integration with my Parkside Mower. Seems to be working quite well, only the status seems wrong:

The correct status is charging, but the main status of the mower is "Fehler" which translates to "Error":

By the way: To let the robot return to the dock, you first have to pause, then stop and then press return to dock. Otherwise it won't work.

[stefangries]

Seems like the current changes break something. The vacuum.* entity is now missing. Readding the device does not help.

This is the error on the console:

[make-all]

Sorry, I did not remove the mapping completely, I left an invalid empty mapping statement in there.

[stefangries]

Seems to be working now, thanks a lot!

[stefangries]

I found another small error. The integration seems not to be able to handle the "RAIN_PARK" state:

To make sure there are no other states the integration cannot handle, here are the states I have experiened so far.
Fot the device state: CHARGING/CHARGING_WITH_TASK_SUSPEND/MOWING/PAUSED/STANDBY/PARK/EMERGENCY/LOCKED/ERROR
For the problem state: MOWER_LEAN/RAIN_PARK/MOWER_UI_LOCKED/MOWER_EMERGENCY

[stefangries]

@make-all Thanks for fixing this 👍

[TadFocus]

You can use mower commands (mowing, pause, park etc?)

[TadFocus]

Note that the support for this device is not yet released, as it required a tweak to the Moebot config. If installing from HACS, you need to select Redownload, select "main" as the version, and wait for that version field to reactivate before pressing the Download button.

This was a problem, thank you

[Biegnik]

Hi, I used this tweak for a month and I was satisfied with results, but after last HS core update (2024.05.3) all mower entities became unavailable. Is there a chance for support?

[make-all]

Did you also update tuya-local?

[Biegnik]

No, I didn't. I followed your instructions from the post above.

[Biegnik]

I downgrade to HS 2024.4.4. and mower entities are available again... What can cause the problem with this update?

[adriaanos]

Does this work in the Smart Life/Tuya app for you? I get an error when I try to add it to the app and the mower factory resets

[stefangries]

For me the Tuya Smart App ist working.

[adriaanos]

I can connect with Bluetooth but cannot activate with WiFi

[cociweb]

Can anybody be so kind to share a snapshot of the config flow, please? I do not have sensors (on the latest version). The same behavior on 3.3 and 3.4 protocol versions.
I have these attributes, but I don't really know what are these and which one goes to which on the config flow.

[make-all]

The config flow for this integration does not look like that, most likely you are using localtuya, which is a different integration.

[cociweb]

The config flow for this integration does not look like that, most likely you are using localtuya, which is a different integration.

Yes, You are right! Thanks for the hints! With your custom component it is perfectly working!

[cociweb]

The config flow for this integration does not look like that, most likely you are using localtuya, which is a different integration.

Yes, You are right! Thanks for the hints! With your custom component it is perfectly working!

um there are some mismatch with the state reporting, and error reposrting, but for control puproses with some hack it can work. - maybe we can open a separate issue thread where we can work it out. Problem Riport is opened:
#1983

[rucanunes]

Could someone please tell me if you are using LocalTuya or the Tuya integration?
How do you add the Lawn Robot? I don't know how to do it because it asks for a blinking light...

Thank you.

[cociweb]

https://github.com/make-all/tuya-local?tab=readme-ov-file#installation

[rucanunes]

Thank you. Didn't know about this one. I was using Local Tuya.
What are the advantages of this integration compared to Local Tuya?

[make-all]

They have a different history, localtuya started with support for simple devices like switches and lights first, and adopted a DIY approach where the end user had to set up their device at dps level themselves. tuya-local forked from a goldair-climate integration, expanding to support other brands of climate devices at first, and keeping the approach that user should not need to know details at the protocol level, so all devices are supported by pre-defined config files. This distinction has become less important, as I think localtuya supports auto-generating all that user config based on the cloud data for the device. Both now support most kinds of entity available in Home Assistant.

Originally both were based on the pytuya library, which has been unmaintained now for years. localtuya chose to fork the library themselves, and maintain a copy inside their source tree. tuya-local chose to switch to tinytuya, which is maintained by a separate team. Because of the workload of maintaining both the HA side and the tuya side of the interface, localtuya can be a bit behind tinytuya when it comes to supporting new Tuya protocol versions, but I think the developers are co-operating so this may be less of a factor now. localtuya's fork of pytuya has been made fully async to fit in with Home Assistant, while tinytuya has remained synchronous, so tuya-local has to use worker threads to fit in with the async expectations of HA, which may make it a little less responsive and heavier.

[rucanunes]

Thank you very much for your detailed reply!! 👍

[cociweb]

I was asking how to add the Parkside Lawn Robot to Tuya so I can add it to HA. But I figured out.

Do you know if we can use both HA and the Parkside app?

you can use HA either with Tuya app or Parkside (lidl home) app too - but not with both. Tuya or lidl are exclusive.

[rucanunes]

If someone finds this post and doesn't know how to to add the Lawn Robot to the Tuya app, just go to "Config -> Activate wifi" on your Parkside Lawn Robot and use the Tuya app to add it.

[rucanunes]

Portugal?

This one's not so bad.

[jonferreira]

Yeah :) I was using Lidl Home. Anyway uninstalled that, paired it with the "Smart Live" app I was already using, installed and configured tuya-local and setup it on HA. 15min job and it's done!

Deffo easier than to layout all the perimeter wire and make it so that it find it's dock lol

[Fmoedas91]

hi anyone can help me? i'm stuck in here.

i don't know what is the values that i need to configure to have all control in vacumm mode (play, pause, dock etc). anyone can share this configuration? thanks

[make-all]

This is not the config dialog of this integration.

Please see this discussion instead: https://community.home-assistant.io/t/local-tuya-setup-for-mower/533487

[Footz355]

Yeah :) I was using Lidl Home. Anyway uninstalled that, paired it with the "Smart Live" app I was already using, installed and configured tuya-local and setup it on HA. 15min job and it's done!

Deffo easier than to layout all the perimeter wire and make it so that it find it's dock lol

And was it ease to obtain Tuya key for the mower?? It was a bit of a nightmare for me

[chepurka]

Maybe someone can help how to retrieve PIN code on PMRA 20-Li land mover?

[cociweb]

pull out the battery for a certain time. (maybe few minutes/hours are enough. but not more than 2 days....) it will restore to the default.

[rucanunes]

Go to grizzlytools.de and send a receipt of the product. They will send you the PIN.

[cociweb]

Hello,
Is there anybody who can get error cause different than MOWING_LEAN (Tilted) for 103? Mine always riports this cause (even if no problem is detected).
Latest version of integration and fw is used by me.
@stefangries @tkrynicki How is it working for you now?

[stefangries]

Yes, you are right, I observed the same. If you want to react on an actual error, I would recommend to watch your lawn_mower.* entity, which switches to the "error"-state, if there is an error.

[Vicente-Ch]

Hola. Para mi fue mucho mas funcional y sencillo integrarlo directamente como si fuese un dispositivo Moebot.
Dejo los pasos aqui:
1.Añadir en HACS como repositorio personalizado: https://github.com/Whytey/pymoebot
2.Descargarlo
3.reiniciar Home Assistant
4.Ajustes>Integraciones>Añadir nueva integracion y buscar Moebot.

5.fin

[make-all]

Your "emergency state" with that integration is still "MOWER_LEAN", so it doesn't seem to address the issue others are facing. I suspect that dp just does not provide useful information, and should be ignored.

[Vicente-Ch]

Pense que todo estaba bien. Pero despues de ponerlo en marcha ya no responde a los controles. Pause, stop... que puede ocurrir.
Error : No pudo llamar al servicio vacuum/pause. unknow error.
Tampoco actualiza el estado. Es como si perdiese la conexión.
Este error se originó a partir de una integración personalizada.

Tambien experimento multiples errores en el registro:

Registrador: pymoebot
Fuente: custom_components/moebot/vacuum.py:100
integración: MoeBot (documentación, problemas)
Ocurrió por primera vez: 14:56:39 (11 ocurrencias)
Último inicio de sesión: 15:13:50

Unable to pause due to current state: 'CHARGING'
Unable to pause due to current state: 'PAUSED'
Error from device: None

---------------------------------------------------o---------------------------------
Registrador: homeassistant.helpers.script.websocket_api_script
Fuente: helpers/script.py:526
Ocurrió por primera vez: 15:14:22 (1 ocurrencias)
Último inicio de sesión: 15:14:22

websocket_api script: Error executing script. Unexpected error for call_service at pos 1:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 526, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 763, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 726, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 296, in async_stop
await self.hass.async_add_executor_job(partial(self.stop, **kwargs))
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 103, in stop
self._moebot.cancel()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 205, in cancel
raise MoeBotStateException()
pymoebot.MoeBotStateException

Este error se originó a partir de una integración personalizada.
---------------------------------------------------------o--------------------------------------
Registrador: pymoebot
Fuente: custom_components/moebot/switch.py:40
integración: MoeBot (documentación, problemas)
Ocurrió por primera vez: 13:47:10 (1 ocurrencias)
Último inicio de sesión: 13:47:10

Error from device: {'Error': 'Unexpected Payload from Device', 'Err': '904', 'Payload': None}

[Vicente-Ch]

Aqui el registro de depuracion de la integracion, por si aporta algun dato, yo no entiendo nada:

2024-06-29 13:44:49.845 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration balance_neto 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
2024-06-29 13:44:49.846 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration octopus_spain 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
2024-06-29 13:44:49.847 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration moebot 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
2024-06-29 13:44:49.847 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meteogalicia_tides 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
2024-06-29 13:44:49.848 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered 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
2024-06-29 13:44:49.848 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration browser_mod 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
2024-06-29 13:44:49.849 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration edata 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
2024-06-29 13:44:49.849 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya 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
2024-06-29 13:44:49.850 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration huawei_solar 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
2024-06-29 13:44:49.850 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs 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
2024-06-29 13:44:52.058 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] CURRENT_HVAC_HEAT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.HEATING instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.060 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] CURRENT_HVAC_IDLE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.IDLE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.062 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] HVAC_MODE_AUTO was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.AUTO instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.066 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.069 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] HVAC_MODE_OFF was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.072 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] SUPPORT_PRESET_MODE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.075 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.078 WARNING (ImportExecutor_0) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE_RANGE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE_RANGE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.081 WARNING (ImportExecutor_0) [homeassistant.const] TEMP_CELSIUS was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.083 WARNING (ImportExecutor_0) [homeassistant.const] TEMP_FAHRENHEIT was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.FAHRENHEIT instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.089 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_CLOSE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.CLOSE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.092 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_OPEN was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.OPEN instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.094 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_SET_POSITION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.SET_POSITION instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.097 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_STOP was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.STOP instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.100 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_CLOSE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.CLOSE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.103 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_OPEN was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.OPEN instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.105 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_SET_POSITION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.SET_POSITION instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.108 WARNING (ImportExecutor_0) [homeassistant.components.cover] SUPPORT_STOP was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use CoverEntityFeature.STOP instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.113 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_DIRECTION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.115 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.118 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.120 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_DIRECTION was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.DIRECTION instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.123 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_OSCILLATE was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.OSCILLATE instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.127 WARNING (ImportExecutor_0) [homeassistant.components.fan] SUPPORT_SET_SPEED was used from localtuya, this is a deprecated constant which will be removed in HA Core 2025.1. Use FanEntityFeature.SET_SPEED instead, please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:52.144 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'localtuya' accesses hass.helpers.service. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from service directly at custom_components/localtuya/init.py, line 164: hass.helpers.service.async_register_admin_service(, please create a bug report at https://github.com/rospogrigio/localtuya/issues
2024-06-29 13:44:53.865 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({% if (states('sensor.temperatura_acs') | float > 50) %}
red
{% elif (states('sensor.temperatura_acs') | float > 40) %}
orange
{% elif (states('sensor.temperatura_acs') | float > 35) %}
green
{% else %}
cyan
{% endif %}) renders=2>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2239, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unknown'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 603, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2616, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2242, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1853, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unknown' when rendering template '{% if (states('sensor.temperatura_acs') | float > 50) %}
red
{% elif (states('sensor.temperatura_acs') | float > 40) %}
orange
{% elif (states('sensor.temperatura_acs') | float > 35) %}
green
{% else %}
cyan
{% endif %}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 715, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 605, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unknown' when rendering template '{% if (states('sensor.temperatura_acs') | float > 50) %}
red
{% elif (states('sensor.temperatura_acs') | float > 40) %}
orange
{% elif (states('sensor.temperatura_acs') | float > 35) %}
green
{% else %}
cyan
{% endif %}' but no default was specified
2024-06-29 13:44:53.992 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({% if (states('sensor.pv_consumed_power') | int > 2000) %}
red
{% elif (states('sensor.pv_consumed_power') | int > 1000) %}
orange
{% elif (states('sensor.pv_consumed_power') | int > 0) %}
yellow
{% else %}
green
{% endif %}) renders=2>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 603, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2616, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2258, in forgiving_int_filter
raise_no_default("int", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1853, in raise_no_default
raise ValueError(
ValueError: Template error: int got invalid input 'unknown' when rendering template '{% if (states('sensor.pv_consumed_power') | int > 2000) %}
red
{% elif (states('sensor.pv_consumed_power') | int > 1000) %}
orange
{% elif (states('sensor.pv_consumed_power') | int > 0) %}
yellow
{% else %}
green
{% endif %}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 715, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 605, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: int got invalid input 'unknown' when rendering template '{% if (states('sensor.pv_consumed_power') | int > 2000) %}
red
{% elif (states('sensor.pv_consumed_power') | int > 1000) %}
orange
{% elif (states('sensor.pv_consumed_power') | int > 0) %}
yellow
{% else %}
green
{% endif %}' but no default was specified
2024-06-29 13:44:53.995 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states("sensor.pv_consumed_power") |float }}W) renders=2>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2239, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unknown'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 603, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2616, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2242, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1853, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ states("sensor.pv_consumed_power") |float }}W' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 715, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 605, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ states("sensor.pv_consumed_power") |float }}W' but no default was specified
2024-06-29 13:44:55.420 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({% if (states('sensor.temperatura_acs') | float > 50) %}
red
{% elif (states('sensor.temperatura_acs') | float > 40) %}
orange
{% elif (states('sensor.temperatura_acs') | float > 35) %}
green
{% else %}
cyan
{% endif %}) renders=6>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2239, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unknown'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 603, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2616, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2242, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1853, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unknown' when rendering template '{% if (states('sensor.temperatura_acs') | float > 50) %}
red
{% elif (states('sensor.temperatura_acs') | float > 40) %}
orange
{% elif (states('sensor.temperatura_acs') | float > 35) %}
green
{% else %}
cyan
{% endif %}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 715, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 605, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unknown' when rendering template '{% if (states('sensor.temperatura_acs') | float > 50) %}
red
{% elif (states('sensor.temperatura_acs') | float > 40) %}
orange
{% elif (states('sensor.temperatura_acs') | float > 35) %}
green
{% else %}
cyan
{% endif %}' but no default was specified
2024-06-29 13:44:55.424 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({% if (states('sensor.pv_consumed_power') | int > 2000) %}
red
{% elif (states('sensor.pv_consumed_power') | int > 1000) %}
orange
{% elif (states('sensor.pv_consumed_power') | int > 0) %}
yellow
{% else %}
green
{% endif %}) renders=6>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 603, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2616, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2258, in forgiving_int_filter
raise_no_default("int", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1853, in raise_no_default
raise ValueError(
ValueError: Template error: int got invalid input 'unknown' when rendering template '{% if (states('sensor.pv_consumed_power') | int > 2000) %}
red
{% elif (states('sensor.pv_consumed_power') | int > 1000) %}
orange
{% elif (states('sensor.pv_consumed_power') | int > 0) %}
yellow
{% else %}
green
{% endif %}' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 715, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 605, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: int got invalid input 'unknown' when rendering template '{% if (states('sensor.pv_consumed_power') | int > 2000) %}
red
{% elif (states('sensor.pv_consumed_power') | int > 1000) %}
orange
{% elif (states('sensor.pv_consumed_power') | int > 0) %}
yellow
{% else %}
green
{% endif %}' but no default was specified
2024-06-29 13:44:55.425 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ states("sensor.pv_consumed_power") |float }}W) renders=6>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2239, in forgiving_float_filter
return float(value)
^^^^^^^^^^^^
ValueError: could not convert string to float: 'unknown'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 603, in async_render
render_result = _render_with_context(self.template, compiled, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2616, in _render_with_context
return template.render(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 1304, in render
self.environment.handle_exception()
File "/usr/local/lib/python3.12/site-packages/jinja2/environment.py", line 939, in handle_exception
raise rewrite_traceback_stack(source=source)
File "", line 1, in top-level template code
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2242, in forgiving_float_filter
raise_no_default("float", value)
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1853, in raise_no_default
raise ValueError(
ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ states("sensor.pv_consumed_power") |float }}W' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 715, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 605, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unknown' when rendering template '{{ states("sensor.pv_consumed_power") |float }}W' but no default was specified
2024-06-29 13:44:56.672 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-06-29 13:44:56.872 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'browser_mod' accesses hass.helpers.storage. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from storage directly at custom_components/browser_mod/store.py, line 94: self.store = hass.helpers.storage.Store(STORAGE_VERSION, STORAGE_KEY), please report it to the author of the 'browser_mod' custom integration
2024-06-29 13:44:57.251 ERROR (SyncWorker_2) [pymoebot] Error from device: {'Error': 'Check device key or version', 'Err': '914', 'Payload': None}
2024-06-29 13:44:57.421 WARNING (SyncWorker_4) [homeassistant.helpers.frame] Detected that custom integration 'localtuya' calls async_dispatcher_send from a thread other than the event loop, which may cause Home Assistant to crash or data to corrupt. For more information, see https://developers.home-assistant.io/docs/asyncio_thread_safety/#async_dispatcher_send at custom_components/localtuya/common.py, line 349: async_dispatcher_send(self._hass, signal, self._status), please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:57.423 WARNING (SyncWorker_5) [homeassistant.helpers.frame] Detected that custom integration 'localtuya' calls async_dispatcher_send from a thread other than the event loop, which may cause Home Assistant to crash or data to corrupt. For more information, see https://developers.home-assistant.io/docs/asyncio_thread_safety/#async_dispatcher_send at custom_components/localtuya/common.py, line 349: async_dispatcher_send(self._hass, signal, self._status), please report it to the author of the 'localtuya' custom integration
2024-06-29 13:44:57.767 WARNING (MainThread) [custom_components.localtuya.switch] [bf8...zv0] Entity switch.lavadora_lt is requesting unknown DPS index 18
2024-06-29 13:44:57.768 WARNING (MainThread) [custom_components.localtuya.switch] [bf8...zv0] Entity switch.lavadora_lt is requesting unknown DPS index 19
2024-06-29 13:44:57.768 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback Entity._async_write_ha_state_from_call_soon_threadsafe() (None)
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in _async_write_ha_state_from_call_soon_threadsafe
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1065, in __async_calculate_state
if extra_state_attributes := self.extra_state_attributes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/localtuya/switch.py", line 65, in extra_state_attributes
self.dps(self._config[CONF_CURRENT_CONSUMPTION]) / 10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'
2024-06-29 13:44:59.128 WARNING (ImportExecutor_0) [homeassistant.components.sensor] STATE_CLASS_MEASUREMENT was used from octopus_spain, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.MEASUREMENT instead, please report it to the author of the 'octopus_spain' custom integration
2024-06-29 13:44:59.143 WARNING (ImportExecutor_0) [homeassistant.components.sensor] STATE_CLASS_MEASUREMENT was used from octopus_spain, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.MEASUREMENT instead, please report it to the author of the 'octopus_spain' custom integration
2024-06-29 13:44:59.998 ERROR (SyncWorker_5) [homeassistant.util.logging] Exception in _new_entity_handler when dispatching 'localtuya_entity_bf982222d8c3513acb0mk6': ('switch.luz_pasillo_2',)
Traceback (most recent call last):
File "/config/custom_components/localtuya/common.py", line 261, in _new_entity_handler
self._dispatch_status()
File "/config/custom_components/localtuya/common.py", line 349, in _dispatch_status
async_dispatcher_send(self._hass, signal, self._status)
File "/usr/src/homeassistant/homeassistant/helpers/dispatcher.py", line 214, in async_dispatcher_send
hass.verify_event_loop_thread("async_dispatcher_send")
File "/usr/src/homeassistant/homeassistant/core.py", line 447, in verify_event_loop_thread
frame.report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 159, in report
_report_integration(what, integration_frame, level, error_if_integration)
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 197, in _report_integration
raise RuntimeError(
RuntimeError: Detected that custom integration 'localtuya' calls async_dispatcher_send from a thread other than the event loop, which may cause Home Assistant to crash or data to corrupt. For more information, see https://developers.home-assistant.io/docs/asyncio_thread_safety/#async_dispatcher_send at custom_components/localtuya/common.py, line 349: async_dispatcher_send(self._hass, signal, self._status). Please report it to the author of the 'localtuya' custom integration.

2024-06-29 13:45:00.006 ERROR (SyncWorker_4) [homeassistant.util.logging] Exception in _new_entity_handler when dispatching 'localtuya_entity_bf0bb05206be9140093baz': ('switch.depuradora_lt',)
Traceback (most recent call last):
File "/config/custom_components/localtuya/common.py", line 261, in _new_entity_handler
self._dispatch_status()
File "/config/custom_components/localtuya/common.py", line 349, in _dispatch_status
async_dispatcher_send(self._hass, signal, self._status)
File "/usr/src/homeassistant/homeassistant/helpers/dispatcher.py", line 214, in async_dispatcher_send
hass.verify_event_loop_thread("async_dispatcher_send")
File "/usr/src/homeassistant/homeassistant/core.py", line 447, in verify_event_loop_thread
frame.report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 159, in report
_report_integration(what, integration_frame, level, error_if_integration)
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 197, in _report_integration
raise RuntimeError(
RuntimeError: Detected that custom integration 'localtuya' calls async_dispatcher_send from a thread other than the event loop, which may cause Home Assistant to crash or data to corrupt. For more information, see https://developers.home-assistant.io/docs/asyncio_thread_safety/#async_dispatcher_send at custom_components/localtuya/common.py, line 349: async_dispatcher_send(self._hass, signal, self._status). Please report it to the author of the 'localtuya' custom integration.

2024-06-29 13:45:00.177 WARNING (ImportExecutor_0) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from edata, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please report it to the author of the 'edata' custom integration
2024-06-29 13:45:00.184 WARNING (ImportExecutor_0) [homeassistant.const] POWER_KILO_WATT was used from edata, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.KILO_WATT instead, please report it to the author of the 'edata' custom integration
2024-06-29 13:45:00.325 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'edata' at custom_components/edata/sensor.py, line 155: with open(RECENT_QUERIES_FILE, "w", encoding="utf8") as queries_file: (offender: /config/custom_components/edata/sensor.py, line 155: with open(RECENT_QUERIES_FILE, "w", encoding="utf8") as queries_file:), please create a bug report at https://github.com/uvejota/homeassistant-edata/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/edata/sensor.py", line 155, in async_setup_entry
with open(RECENT_QUERIES_FILE, "w", encoding="utf8") as queries_file:

2024-06-29 13:45:00.517 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'edata' at custom_components/edata/coordinator.py, line 78: self._datadis = EdataHelper( (offender: /usr/local/lib/python3.12/site-packages/edata/connectors/datadis.py, line 73: with open(RECENT_QUERIES_FILE, "r", encoding="utf8") as dst_file:), please create a bug report at https://github.com/uvejota/homeassistant-edata/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/edata/sensor.py", line 166, in async_setup_entry
coordinator = EdataCoordinator(
File "/config/custom_components/edata/coordinator.py", line 78, in init
self._datadis = EdataHelper(

2024-06-29 13:45:00.700 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module inside the event loop by custom integration 'edata' at custom_components/edata/coordinator.py, line 170: self._datadis.process_data() (offender: /usr/local/lib/python3.12/site-packages/holidays/registry.py, line 236: self.entity = getattr(importlib.import_module(self.module_name), self.entity_name)), please create a bug report at https://github.com/uvejota/homeassistant-edata/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/edata/sensor.py", line 166, in async_setup_entry
coordinator = EdataCoordinator(
File "/config/custom_components/edata/coordinator.py", line 98, in init
self._load_data(preprocess=True)
File "/config/custom_components/edata/coordinator.py", line 170, in _load_data
self._datadis.process_data()

2024-06-29 13:45:00.854 WARNING (ImportExecutor_0) [homeassistant.const] DEVICE_CLASS_BATTERY was used from moebot, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.BATTERY instead, please report it to the author of the 'moebot' custom integration
2024-06-29 13:45:06.394 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to import_module inside the event loop by custom integration 'edata' at custom_components/edata/coordinator.py, line 170: self._datadis.process_data() (offender: /usr/local/lib/python3.12/site-packages/dateparser/languages/loader.py, line 215: import_module("dateparser.data.date_translation_data." + lang),), please create a bug report at https://github.com/uvejota/homeassistant-edata/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/edata/sensor.py", line 166, in async_setup_entry
coordinator = EdataCoordinator(
File "/config/custom_components/edata/coordinator.py", line 98, in init
self._load_data(preprocess=True)
File "/config/custom_components/edata/coordinator.py", line 170, in _load_data
self._datadis.process_data()

2024-06-29 13:45:06.446 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'edata' accesses hass.components.websocket_api. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from websocket_api directly at custom_components/edata/websockets.py, line 68: hass.components.websocket_api.async_register_command(, please create a bug report at https://github.com/uvejota/homeassistant-edata/issues
2024-06-29 13:45:06.619 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.freeds_pwm_aut_man are missing or not currently available
2024-06-29 13:45:06.619 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities switch.freeds_pwm_aut_man are missing or not currently available
2024-06-29 13:45:07.907 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 630: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
2024-06-29 13:45:19.976 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'edata' at custom_components/edata/coordinator.py, line 149: with open( (offender: /config/custom_components/edata/coordinator.py, line 149: with open(), please create a bug report at https://github.com/uvejota/homeassistant-edata/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/config/custom_components/edata/sensor.py", line 181, in async_first_refresh
await coordinator.async_refresh()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 288, in async_refresh
await self._async_refresh(log_failures=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/edata/coordinator.py", line 149, in _async_update_data
with open(

2024-06-29 13:46:39.245 ERROR (SyncWorker_13) [pymoebot] Error from device: None
2024-06-29 13:47:10.054 ERROR (SyncWorker_11) [pymoebot] Error from device: {'Error': 'Unexpected Payload from Device', 'Err': '904', 'Payload': None}
2024-06-29 13:47:14.989 ERROR (SyncWorker_22) [pymoebot] Error from device: None
2024-06-29 13:49:44.890 ERROR (SyncWorker_23) [pymoebot] Error from device: None
2024-06-29 14:00:01.257 WARNING (MainThread) [custom_components.localtuya.switch] [bf0...baz] Entity switch.depuradora_lt is requesting unknown DPS index 18
2024-06-29 14:00:01.257 WARNING (MainThread) [custom_components.localtuya.switch] [bf0...baz] Entity switch.depuradora_lt is requesting unknown DPS index 19
2024-06-29 14:00:01.258 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback Entity._async_write_ha_state_from_call_soon_threadsafe() (None)
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in _async_write_ha_state_from_call_soon_threadsafe
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1065, in __async_calculate_state
if extra_state_attributes := self.extra_state_attributes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/localtuya/switch.py", line 65, in extra_state_attributes
self.dps(self._config[CONF_CURRENT_CONSUMPTION]) / 10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'
2024-06-29 14:06:19.415 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:08:49.387 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:10:01.646 WARNING (MainThread) [custom_components.localtuya.switch] [bf0...baz] Entity switch.depuradora_lt is requesting unknown DPS index 18
2024-06-29 14:10:01.647 WARNING (MainThread) [custom_components.localtuya.switch] [bf0...baz] Entity switch.depuradora_lt is requesting unknown DPS index 19
2024-06-29 14:10:01.647 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback Entity._async_write_ha_state_from_call_soon_threadsafe() (None)
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in _async_write_ha_state_from_call_soon_threadsafe
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1065, in __async_calculate_state
if extra_state_attributes := self.extra_state_attributes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/localtuya/switch.py", line 65, in extra_state_attributes
self.dps(self._config[CONF_CURRENT_CONSUMPTION]) / 10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'
2024-06-29 14:11:20.478 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:13:20.556 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:18:21.503 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:22:52.561 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:23:52.416 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:25:52.379 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:27:52.598 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:28:52.360 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:29:52.358 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:30:17.592 WARNING (MainThread) [custom_components.localtuya.switch] [bf8...zv0] Entity switch.lavadora_lt is requesting unknown DPS index 18
2024-06-29 14:30:17.592 WARNING (MainThread) [custom_components.localtuya.switch] [bf8...zv0] Entity switch.lavadora_lt is requesting unknown DPS index 19
2024-06-29 14:30:17.593 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback Entity._async_write_ha_state_from_call_soon_threadsafe() (None)
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in _async_write_ha_state_from_call_soon_threadsafe
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1065, in __async_calculate_state
if extra_state_attributes := self.extra_state_attributes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/localtuya/switch.py", line 65, in extra_state_attributes
self.dps(self._config[CONF_CURRENT_CONSUMPTION]) / 10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'
2024-06-29 14:33:22.344 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:33:52.341 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:36:22.405 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:38:22.575 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:41:54.598 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:45:29.759 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'edata' at custom_components/edata/coordinator.py, line 149: with open( (offender: /config/custom_components/edata/coordinator.py, line 149: with open(), please create a bug report at https://github.com/uvejota/homeassistant-edata/issues
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 255, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/edata/coordinator.py", line 149, in _async_update_data
with open(

2024-06-29 14:46:56.376 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:47:56.436 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:49:26.345 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 14:53:19.972 ERROR (SyncWorker_29) [pymoebot] Error from device: {'Error': 'Unexpected Payload from Device', 'Err': '904', 'Payload': None}
2024-06-29 14:56:39.553 ERROR (SyncWorker_35) [pymoebot] Unable to pause due to current state: 'CHARGING'
2024-06-29 14:56:39.557 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 14:56:49.536 ERROR (SyncWorker_28) [pymoebot] Unable to pause due to current state: 'CHARGING'
2024-06-29 14:56:49.538 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 14:56:52.970 ERROR (SyncWorker_49) [pymoebot] Unable to cancel due to current state: 'CHARGING'
2024-06-29 14:56:52.972 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 296, in async_stop
await self.hass.async_add_executor_job(partial(self.stop, **kwargs))
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 103, in stop
self._moebot.cancel()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 205, in cancel
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 14:57:17.578 ERROR (SyncWorker_54) [pymoebot] Error from device: None
2024-06-29 14:57:19.078 ERROR (SyncWorker_9) [pymoebot] Unable to pause due to current state: 'PAUSED'
2024-06-29 14:57:19.079 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 14:57:22.610 ERROR (SyncWorker_12) [pymoebot] Unable to pause due to current state: 'PAUSED'
2024-06-29 14:57:22.611 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 14:57:36.328 ERROR (SyncWorker_58) [pymoebot] Error from device: None
2024-06-29 14:57:38.034 ERROR (SyncWorker_5) [pymoebot] Error from device: None
2024-06-29 14:59:23.352 ERROR (SyncWorker_38) [pymoebot] Unable to pause due to current state: 'PAUSED'
2024-06-29 14:59:23.353 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 14:59:38.303 ERROR (SyncWorker_33) [pymoebot] Error from device: None
2024-06-29 14:59:41.227 ERROR (SyncWorker_1) [pymoebot] Error from device: None
2024-06-29 15:00:56.651 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 15:03:30.010 ERROR (SyncWorker_35) [pymoebot] Error from device: None
2024-06-29 15:03:33.256 ERROR (SyncWorker_45) [pymoebot] Unable to pause due to current state: 'PAUSED'
2024-06-29 15:03:33.257 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 15:04:23.460 ERROR (SyncWorker_39) [pymoebot] Error from device: {'Error': 'Check device key or version', 'Err': '914', 'Payload': None}
2024-06-29 15:04:36.692 ERROR (SyncWorker_27) [pymoebot] Unable to pause due to current state: 'PAUSED'
2024-06-29 15:04:36.695 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 15:04:44.356 ERROR (SyncWorker_61) [pymoebot] Error from device: None
2024-06-29 15:04:58.913 ERROR (SyncWorker_15) [pymoebot] Unable to pause due to current state: 'PAUSED'
2024-06-29 15:04:58.914 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 15:09:13.895 ERROR (SyncWorker_38) [pymoebot] Unable to pause due to current state: 'PAUSED'
2024-06-29 15:09:13.896 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 387, in async_pause
await self.hass.async_add_executor_job(self.pause)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 100, in pause
self._moebot.pause()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 195, in pause
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 15:09:17.870 ERROR (SyncWorker_61) [pymoebot] Error from device: None
2024-06-29 15:09:20.713 ERROR (SyncWorker_28) [pymoebot] Error from device: None
2024-06-29 15:09:25.430 ERROR (SyncWorker_46) [pymoebot] Error from device: None
2024-06-29 15:10:27.424 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 15:12:04.808 ERROR (SyncWorker_43) [pymoebot] Error from device: {'Error': 'Check device key or version', 'Err': '914', 'Payload': None}
2024-06-29 15:12:05.247 INFO (MainThread) [custom_components.moebot] Created a moebot: [MoeBot - {id: bf136b42997205f22fdvcr, state: None, battery: None}]
2024-06-29 15:12:05.479 DEBUG (pymoebot) [custom_components.moebot] 'MoeBotVacuumEntity' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.480 DEBUG (pymoebot) [custom_components.moebot] 'MowingStateSensor' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.482 DEBUG (pymoebot) [custom_components.moebot] 'BatterySensor' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.482 DEBUG (pymoebot) [custom_components.moebot] 'EmergencyStateSensor' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.482 DEBUG (pymoebot) [custom_components.moebot] 'WorkModeSensor' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.483 DEBUG (pymoebot) [custom_components.moebot] 'PyMoebotVersionSensor' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.483 DEBUG (pymoebot) [custom_components.moebot] 'TuyaVersionSensor' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.483 DEBUG (pymoebot) [custom_components.moebot] 'WorkingTimeNumber' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.483 DEBUG (pymoebot) [custom_components.moebot] 'ParkWhenRainingSwitch' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:05.484 DEBUG (pymoebot) [custom_components.moebot] 'PollDeviceButton' got an update: {'dps': {'6': 100, '101': 'MOWING', '102': 0, '103': 'MOWER_LEAN', '104': True, '105': 3, '106': 2323, '116': False}}
2024-06-29 15:12:36.535 ERROR (SyncWorker_35) [pymoebot] Error from device: None
2024-06-29 15:12:45.742 ERROR (SyncWorker_26) [pymoebot] Unable to cancel due to current state: 'MOWING'
2024-06-29 15:12:45.745 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 241, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 296, in async_stop
await self.hass.async_add_executor_job(partial(self.stop, **kwargs))
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 103, in stop
self._moebot.cancel()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 205, in cancel
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 15:13:50.336 ERROR (SyncWorker_9) [pymoebot] Error from device: None
2024-06-29 15:14:22.746 ERROR (SyncWorker_21) [pymoebot] Unable to cancel due to current state: 'MOWING'
2024-06-29 15:14:22.750 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Unexpected error for call_service at pos 1:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 526, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 763, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 726, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 296, in async_stop
await self.hass.async_add_executor_job(partial(self.stop, **kwargs))
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 103, in stop
self._moebot.cancel()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 205, in cancel
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 15:14:22.757 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140178578954784] Error handling message: Unknown error (unknown_error) Tito from 192.168.10.20 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 793, in handle_execute_script
script_result = await script_obj.async_run(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1769, in async_run
return await asyncio.shield(create_eager_task(run.async_run()))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 464, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 528, in _async_step
self._handle_exception(
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 558, in _handle_exception
raise exception
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 526, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 763, in _async_call_service_step
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 726, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2741, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2784, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 977, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1049, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vacuum/init.py", line 296, in async_stop
await self.hass.async_add_executor_job(partial(self.stop, **kwargs))
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/moebot/vacuum.py", line 103, in stop
self._moebot.cancel()
File "/usr/local/lib/python3.12/site-packages/pymoebot/init.py", line 205, in cancel
raise MoeBotStateException()
pymoebot.MoeBotStateException
2024-06-29 15:28:57.567 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 15:29:27.469 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 15:30:17.641 WARNING (MainThread) [custom_components.localtuya.switch] [bf8...zv0] Entity switch.lavadora_lt is requesting unknown DPS index 18
2024-06-29 15:30:17.641 WARNING (MainThread) [custom_components.localtuya.switch] [bf8...zv0] Entity switch.lavadora_lt is requesting unknown DPS index 19
2024-06-29 15:30:17.642 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback Entity._async_write_ha_state_from_call_soon_threadsafe() (None)
Traceback (most recent call last):
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 992, in _async_write_ha_state_from_call_soon_threadsafe
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1126, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1065, in __async_calculate_state
if extra_state_attributes := self.extra_state_attributes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/localtuya/switch.py", line 65, in extra_state_attributes
self.dps(self._config[CONF_CURRENT_CONSUMPTION]) / 10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
TypeError: unsupported operand type(s) for /: 'NoneType' and 'int'
2024-06-29 15:38:54.195 ERROR (pymoebot) [pymoebot] Error from device: {'Error': 'Network Error: Unable to Connect', 'Err': '901', 'Payload': None}
2024-06-29 15:40:04.852 ERROR (pymoebot) [pymoebot] Error from device: {'Error': 'Network Error: Unable to Connect', 'Err': '901', 'Payload': None}
2024-06-29 15:41:15.507 ERROR (pymoebot) [pymoebot] Error from device: {'Error': 'Network Error: Unable to Connect', 'Err': '901', 'Payload': None}
2024-06-29 15:41:27.555 WARNING (MainThread) [homeassistant.components.automation.10_inversor_activar_cargas_por_alto_voltaje] 10/inversor activar cargas por alto voltaje : Already running
2024-06-29 15:42:26.163 ERROR (pymoebot) [pymoebot] Error from device: {'Error': 'Network Error: Unable to Connect', 'Err': '901', 'Payload': None}

[Ludo-V]

Hello,
Since the last update, 2024.7.1, I can no longer control the lawn mower from Alexa.
The previous entity was VACCUM. Now it's LAWN_MOWER.
And apparently LAWN_MOWER is not managed by Alexa!
Do you have a solution?
Thanks for your help and especially for your work.

[cociweb]

I'm not fully aware of alexa, but what about exposing HA scripts? Since the integration is not fully fits the device, you need to pause the lawnmower, then "press" the cancel button and than you can instruct the lawnmower.

You can create separate scripts to the movements as docking, spot mode, or start mowing. these scripts can be used in automations as well.

[make-all]

Your issue seems to be with the Alexa integration in HA, or Alexa itself.

[Ludo-V]

Thanks, but before the update everything worked perfectly...
now when I try to reinstall the old version, it keeps the same LAWN_MOWER entity!
I can't get back to VACUUM!
Can anyone tell me how to remove all traces of LAWN_MOWER in home assistant, please ?

[cociweb]

Actually, there was no difference between lawn_mower and vacuum entities; they were aliases. They functioned in the same manner, meaning both had the same issues. I believe your problem stems from the upstream issues of Home Assistant (HA). Since the lawnmower is a relatively new (approximately 6 months old) native entity type, it's advisable to transition from vacuum to lawn_mowers. You won't be able to revert to vacuum. In my experience, migrating to lawn_mower works fine only some minor value mappings are not ok. - The glitches are remained the same...

[Ludo-V]

Lawn_mower is not recognized by Alexa...
Vacuum is a recognized entity.

In the link below you have the list of entities managed by Alexa

[Ludo-V]

list of entities managed by Alexa :

https://www.home-assistant.io/integrations/alexa.smart_home/#vacuum