xZetsubou
commented
3 weeks ago Post the entry diagnostics
Closed Magalopole closed 1 day ago
xZetsubou
commented
3 weeks ago Post the entry diagnostics
Megalopole
commented
3 weeks ago xZetsubou
commented
3 weeks ago Re-configure the device named Porta Quarto Gael and change the protocol version to 3.4 because auto shouldn't be a valid value...
Megalopole
commented
3 weeks ago config_entry-localtuya-a3b485d0a7119bc40cea29b7e95e0b0e-1.json
It's the same way, I've tried all kinds of protocols.
xZetsubou
commented
3 weeks ago Have you tried to fully turn off / on the gateway power?
Megalopole
commented
3 weeks ago Sim, até mudei de local para melhorar o sinal de wifi.
xZetsubou
commented
3 weeks ago Not sure what exactly said but did you fix the issue?
Megalopole
commented
3 weeks ago The problem continues, I said I had turned it off and on and I also moved the hub to improve the wifi signal.
hayvan96
commented
3 weeks ago I have the same behaviour on a already existing and configured device, which worked for months without any issue.
xZetsubou
commented
3 weeks ago Try with update 2024.6.0 and if it's not working post the logs with 2024.6.0 changes.
hayvan96
commented
3 weeks ago 2024-06-08 09:56:10.809 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-08 09:56:13.175 DEBUG (MainThread) [custom_components.localtuya.discovery] Listening to broadcasts on UDP port 6666, 6667 2024-06-08 09:56:13.176 INFO (MainThread) [custom_components.localtuya] Cloud API account not configured. 2024-06-08 09:56:13.644 DEBUG (MainThread) [custom_components.localtuya.switch] [bfa...1fs - Kirjasto] Initialized switch [Kirjasto] 2024-06-08 09:56:13.645 DEBUG (MainThread) [custom_components.localtuya.switch] [bfa...1fs - Kirjasto] Adding switch.kirjasto with configuration: {'friendly_name': 'Kirjasto', 'entity_category': 'None', 'current': '18', 'current_consumption': '19', 'voltage': '20', 'restore_on_reconnect': False, 'is_passive_entity': False, 'id': '1', 'platform': 'switch', 'icon': ''} 2024-06-08 09:56:13.645 DEBUG (MainThread) [custom_components.localtuya.coordinator] [bff...6z9 - TV] Trying to connect to: 192.168.1.14... 2024-06-08 09:56:13.734 DEBUG (MainThread) [custom_components.localtuya.core.pytuya] [bff...6z9 - TV] Dispatching message CMD 10 TuyaMessage(seqno=1, cmd=10, retcode=1, payload=b"\x98*\xfc#\xa6Idw\xc6h1\xefI,\x8d\n\xaa!\xb5'I\xb4lz@\xa9\xe9g\\\xde\xa0\xf6", crc=410952128, crc_good=True, prefix=21930, iv=None) 2024-06-08 09:56:13.735 DEBUG (MainThread) [custom_components.localtuya.switch] [bfa...1fs - Kirjasto] Entity Kirjasto (DP 1) - Not restoring as restore on reconnect is disabled for this entity and the entity has an initial status or it is not a passive entity 2024-06-08 09:56:13.735 DEBUG (MainThread) [custom_components.localtuya.coordinator] [bff...6z9 - TV] Success: connected to: 192.168.1.14 2024-06-08 09:56:14.936 DEBUG (MainThread) [custom_components.localtuya.discovery] Discovered device: {'ip': '192.168.1.14', 'gwId': 'bfaab1be2e5b211f4ex1fs', 'active': 2, 'ablilty': 0, 'encrypt': True, 'productKey': 'keyqwtgrcsf3hxng', 'version': '3.3'} 2024-06-08 09:56:23.851 DEBUG (MainThread) [custom_components.localtuya.core.pytuya] [bff...6z9 - TV] Dispatching message CMD 9 TuyaMessage(seqno=0, cmd=9, retcode=0, payload=b'', crc=2958142211, crc_good=True, prefix=21930, iv=None) 2024-06-08 09:56:33.878 DEBUG (MainThread) [custom_components.localtuya.core.pytuya] [bff...6z9 - TV] Dispatching message CMD 9 TuyaMessage(seqno=0, cmd=9, retcode=0, payload=b'', crc=2958142211, crc_good=True, prefix=21930, iv=None) 2024-06-08 09:56:43.922 DEBUG (MainThread) [custom_components.localtuya.core.pytuya] [bff...6z9 - TV] Dispatching message CMD 9 TuyaMessage(seqno=0, cmd=9, retcode=0, payload=b'', crc=2958142211, crc_good=True, prefix=21930, iv=None) 2024-06-08 09:56:53.948 DEBUG (MainThread) [custom_components.localtuya.core.pytuya] [bff...6z9 - TV] Dispatching message CMD 9 TuyaMessage(seqno=0, cmd=9, retcode=0, payload=b'', crc=2958142211, crc_good=True, prefix=21930, iv=None) 2024-06-08 09:57:03.983 DEBUG (MainThread) [custom_components.localtuya.core.pytuya] [bff...6z9 - TV] Dispatching message CMD 9 TuyaMessage(seqno=0, cmd=9, retcode=0, payload=b'', crc=2958142211, crc_good=True, prefix=21930, iv=None)
hayvan96
commented
3 weeks ago xZetsubou
commented
3 weeks ago @hayvan96 From the logs there is no issues at all it's better if you copy the fully logs instead of a few because the logs you posted shows not showing much...
You may also try to change the protocol of the device to 3.2 just for testing as well.
hayvan96
commented
3 weeks ago @hayvan96 From the logs there is no issues at all it's better if you copy the fully logs instead of a few because the logs you posted shows not showing much...
You may also try to change the protocol of the device to
3.2just for testing as well.
I've posted all logs filtered on "tuya". Let me check if changing protocol changes anything.
hayvan96
commented
3 weeks ago No change. I've tried :
Megalopole
commented
3 weeks ago Debug file follows. the device diagnosis is not being generated, I have already reinstalled the integration and restarted the HA, for some reason after the update it is not creating the record. error_log-18.txt error_log-12.txt
Megalopole
commented
3 weeks ago 
github-actions[bot]
commented
1 week ago This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.
LocalTuya Version
2024.5.0
Home Assistant Version
2024.5.5
Environment
What happened?
After adding the devices, they become unavailable, or changing their state, but without being able to use them, especially ZigBee devices.
Steps to reproduce.
Relevant log output
Diagnostics information.
error_log-7.txt error_log-5.txt
