Xenomes / Domoticz-TinyTUYA-Local-Plugin

MIT License
2 stars 2 forks source link

Devices seem off-line to plugin #4

Closed wvries closed 1 week ago

wvries commented 4 months ago

Hi,

One more to debug :-)

I get the following errors in the logfile:

2024-05-16 14:21:07.327 Error: TinyTuya(local): Device :bf9250a724f45d4672bdag is Offline! 2024-05-16 14:22:48.322 Error: TinyTuya(local): Device :bfca7b0908fc2e217eztow is Offline! 2024-05-16 14:25:00.008 Error: TinyTuya(local): Device :bf2e30944c01138d44lndd is Offline! 2024-05-16 14:26:32.421 Error: TinyTuya(local): Device :bf9250a724f45d4672bdag is Offline!

switching does not work when I get this error.

When restarting the plugin, all starts to work again (for some time, then again stops)

TinyTUYA Plugin Local Controlversion Alpha 0.3

Xenomes commented 4 months ago

When Plugin sees 'Device Unreachable' as status from Timytuya then this message is shown. Are these devices on the same network as Domoticz. no VLAN or other location?

wvries commented 4 months ago

Hi,No vlans or nothing. My dev Domoticz is running in a docker container though.But all other containers have no network issues at all.Tomorrow I will move the container networking to host, see if that makes a difference.Met vriendelijke groet,saludos cordiales,With kind regards,Wilbert de VriesFrom: Xenomes @.>Sent: Thursday, May 16, 2024 7:47:33 PMTo: Xenomes/Domoticz-TinyTUYA-Local-Plugin @.>Cc: Wilbert de Vries @.>; Author @.>Subject: Re: [Xenomes/Domoticz-TinyTUYA-Local-Plugin] Devices seem off-line to plugin (Issue #4) When Plugin sees 'Device Unreachable' as status from Timytuya then this message is shown. Are these devices on the same network as Domoticz. no VLAN or other location?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

wvries commented 4 months ago

Moved container to Host and still have sometimes this issue.

2024-05-18 14:18:54.840 Error: TinyTuya(local): Device :bf9250a724f45d4672bdag is Offline! 2024-05-18 14:22:05.395 Error: TinyTuya(local): Device :32124004ecfabc205204 is Offline! 2024-05-18 14:22:05.407 Error: TinyTuya(local): handleThread: '32124004ecfabc205204' line 336 2024-05-18 14:24:10.003 Error: TinyTuya(local): Device :bfca7b0908fc2e217eztow is Offline! 2024-05-18 14:24:23.210 Error: TinyTuya(local): Device :bf9250a724f45d4672bdag is Offline! 2024-05-18 14:28:49.154 Error: TinyTuya(local): Device :32124004ecfabc205204 is Offline! 2024-05-18 14:28:49.158 Error: TinyTuya(local): handleThread: '32124004ecfabc205204' line 336 2024-05-18 14:32:15.905 Error: TinyTuya(local): Device :bf9250a724f45d4672bdag is Offline!

I do now also see one device that is reported Offline also having a handleThread line 336 report in the error log.

Also, in the normal debug log, I see many entries of "no mapping for..." for almost all devices. 2024-05-18 14:50:49.156 TinyTuya(local): Device name=Siren id=32124004ecfabc205204 ip=192.168.1.144 version=3.1 2024-05-18 14:50:49.156 TinyTuya(local): Update devices in Domoticz 2024-05-18 14:50:49.243 TinyTuya(local): No mapping for BatteryStatus skipped 2024-05-18 14:50:49.260 TinyTuya(local): No mapping for Alarmtype skipped 2024-05-18 14:50:49.289 TinyTuya(local): No mapping for AlarmPeriod skipped 2024-05-18 14:50:49.312 TinyTuya(local): No mapping for AlarmSwitch skipped Is that due to the fact that not all states are implemented for all the devices ?

Xenomes commented 4 months ago

I do now also see one device that is reported Offline also having a handleThread line 336 report in the error log.

Yes, 336 is a bug in the script, here the plugin is put in offilne.

Also, in the normal debug log, I see many entries of "no mapping for..." for almost all devices. 2024-05-18 14:50:49.156 TinyTuya(local): Device name=Siren id=32124004ecfabc205204 ip=192.168.1.144 version=3.1 2024-05-18 14:50:49.156 TinyTuya(local): Update devices in Domoticz 2024-05-18 14:50:49.243 TinyTuya(local): No mapping for BatteryStatus skipped 2024-05-18 14:50:49.260 TinyTuya(local): No mapping for Alarmtype skipped 2024-05-18 14:50:49.289 TinyTuya(local): No mapping for AlarmPeriod skipped 2024-05-18 14:50:49.312 TinyTuya(local): No mapping for AlarmSwitch skipped Is that due to the fact that not all states are implemented for all the devices ?

No mapping is a debug line, Tuya is using a lot of names so i can see what is needed to be added.

Xenomes commented 1 week ago

In the new push it look this is fixed!