-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switches does randomly set on/off #6
Comments
Is it only in Domoticz, or also on the device itself? Which device is it? |
All on\off devices, it when i disable the local tuya it does not happen
anymore
Op di 24 sep 2024 om 14:47 schreef Xenomes ***@***.***>
… Is it only in Domoticz, or also on the device itself? Which device is it?
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7K66MG24W36E3TYD6ETXKDZYFNMPAVCNFSM6AAAAABOYEHUFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZRGE3TINZWHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Okay, i will setup a test to see what is going on. |
The bathroom heater did turn on in the middle of the night, i tought i was
hacked but further investigation i noticed the boiler, dishwasher etc turns
off. Not at the same time. But random. I turned off local tuya plugin and
everything seems ok now
Op di 24 sep 2024 om 15:26 schreef Xenomes ***@***.***>
… Okay, i will setup a test to see what is going on.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7K66MEXG5CH4WYODWFUCLTZYFSBXAVCNFSM6AAAAABOYEHUFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZRGI3TIMRVG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
That’s not good... I’ll keep you updated on the process. Did this happen with the previous version? |
Found the issue, in the new scaling, type detection was incorrect. A True or False was converted to 1 and 0. 😅 |
Ik probeer het morgen uit 😘
Op wo 25 sep 2024 om 19:56 schreef Xenomes ***@***.***>
… Found the issue, in the new scaling, type detection was incorrect. A True
or False was converted to 1 and 0. 😅
Fixed in the latest push.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7K66ME756L4SNKWTCRWGOLZYL2NHAVCNFSM6AAAAABOYEHUFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUG44TAMJWGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Af en toe gebeurt het nog
Op wo 25 sep 2024 om 21:44 schreef Marino Vande Walle <
***@***.***>:
… Ik probeer het morgen uit 😘
Op wo 25 sep 2024 om 19:56 schreef Xenomes ***@***.***>
> Found the issue, in the new scaling, type detection was incorrect. A True
> or False was converted to 1 and 0. 😅
> Fixed in the latest push.
>
> —
> Reply to this email directly, view it on GitHub
> <#6 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7K66ME756L4SNKWTCRWGOLZYL2NHAVCNFSM6AAAAABOYEHUFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZUG44TAMJWGY>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
Dat is vervelend, ik kan het probleem helaas niet nagebootst. Mijn testapparaat staat al twee dagen uit en is niet vanzelf aan gegaan. That's unfortunate, I can't replicate the issue. My test device has been off for two days and hasn't turned on by itself. |
Heb een nieuwe versie online gezet, kwam er achter dat de DSP some niet in een run gevonden werden, met een extra detectie in test script nog geen misser gehad. I uploaded a new version online, discovered that the DSPs were not found in a run, but with an additional detection in the test script, haven't had any misses so far. |
Ik krijg deze melding in de logs:
2024-10-04 16:28:53.541 Error: LocalTuya: handleThread: string indices must
be integers line 355
2024-10-04 16:28:53.541 Error: LocalTuya: handleThread: string indices must
be integers line 355
2024-10-04 16:28:53.541 Error: LocalTuya: handleThread: string indices must
be integers line 355
2024-10-04 16:28:53.542 Error: LocalTuya: handleThread: string indices must
be integers line 355
Op ma 30 sep 2024 om 21:26 schreef Xenomes ***@***.***>:
… Heb een nieuwe versie online gezet, kwam er achter dat de DSP some niet in
een run gevonden werden, met een extra detectie in test script nog geen
misser gehad.
I uploaded a new version online, discovered that the DSPs were not found
in a run, but with an additional detection in the test script, haven't had
any misses so far.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7K66MEGEKBSV3QAN43AP6DZZGJXDAVCNFSM6AAAAABOYEHUFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBTHA4DMOBQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Heb je een indicatie welk apparaat het is? Op regel 355 wordt de schaalfactor aangeroepen. Ik heb een detectie ingebouwd die ervoor zorgt dat alleen float, int en numerieke strings worden toegelaten in de berekening. Do you have any indication of which device it is? On line 355, the scaling function is called. I've implemented a check that only allows floats, integers, and numeric strings in the calculation. |
Gevonden! De JSON zonder schaal veroorzaakte een fout, opgelost in versie 0.5a. Found it! The JSON without scale caused an error, fixed in version 0.5a. |
Error is gone, but values are 10 times too high again and getting these
messages
2024-10-06 14:13:39.989 LocalTuya: Run Startup script
2024-10-06 14:13:39.989 LocalTuya: No mapping found for device: Droogkast
sub device: countdown_1
2024-10-06 14:13:39.989 LocalTuya: No mapping found for device: Droogkast
sub device: relay_status
2024-10-06 14:13:39.989 LocalTuya: No mapping found for device: Droogkast
sub device: overcharge_switch
2024-10-06 14:13:39.989 LocalTuya: No mapping found for device: Droogkast
sub device: light_mode
2024-10-06 14:13:39.989 LocalTuya: No mapping found for device: Droogkast
sub device: cycle_time
2024-10-06 14:13:39.990 LocalTuya: No mapping found for device: Droogkast
sub device: random_time
2024-10-06 14:13:39.990 LocalTuya: No mapping found for device: Droogkast
sub device: switch_inching
2024-10-06 14:13:39.991 LocalTuya: Run Startup script
2024-10-06 14:13:39.991 LocalTuya: No mapping found for device: Grote
vriezer sub device: countdown_1
2024-10-06 14:13:39.991 LocalTuya: No mapping found for device: Grote
vriezer sub device: relay_status
2024-10-06 14:13:39.991 LocalTuya: No mapping found for device: Grote
vriezer sub device: overcharge_switch
2024-10-06 14:13:39.992 LocalTuya: No mapping found for device: Grote
vriezer sub device: light_mode
2024-10-06 14:13:39.992 LocalTuya: No mapping found for device: Grote
vriezer sub device: cycle_time
2024-10-06 14:13:39.992 LocalTuya: No mapping found for device: Grote
vriezer sub device: random_time
2024-10-06 14:13:39.992 LocalTuya: No mapping found for device: Grote
vriezer sub device: switch_inching
2024-10-06 14:13:39.993 LocalTuya: Run Startup script
2024-10-06 14:13:39.993 LocalTuya: No mapping found for device: Boiler sub
device: countdown_1
2024-10-06 14:13:39.993 LocalTuya: No mapping found for device: Boiler sub
device: relay_status
2024-10-06 14:13:39.993 LocalTuya: No mapping found for device: Boiler sub
device: overcharge_switch
2024-10-06 14:13:39.993 LocalTuya: No mapping found for device: Boiler sub
device: light_mode
2024-10-06 14:13:39.993 LocalTuya: No mapping found for device: Boiler sub
device: cycle_time
2024-10-06 14:13:39.993 LocalTuya: No mapping found for device: Boiler sub
device: random_time
2024-10-06 14:13:39.993 LocalTuya: No mapping found for device: Boiler sub
device: switch_inching
2024-10-06 14:13:39.995 LocalTuya: Run Startup script
2024-10-06 14:13:39.995 LocalTuya: No mapping found for device: Koelkast
kelderverdieping sub device: countdown_1
2024-10-06 14:13:39.995 LocalTuya: No mapping found for device: Koelkast
kelderverdieping sub device: relay_status
2024-10-06 14:13:39.995 LocalTuya: No mapping found for device: Koelkast
kelderverdieping sub device: overcharge_switch
2024-10-06 14:13:39.995 LocalTuya: No mapping found for device: Koelkast
kelderverdieping sub device: light_mode
2024-10-06 14:13:39.995 LocalTuya: No mapping found for device: Koelkast
kelderverdieping sub device: cycle_time
2024-10-06 14:13:39.995 LocalTuya: No mapping found for device: Koelkast
kelderverdieping sub device: random_time
2024-10-06 14:13:39.995 LocalTuya: No mapping found for device: Koelkast
kelderverdieping sub device: switch_inching
2024-10-06 14:13:39.996 LocalTuya: Run Startup script
2024-10-06 14:13:39.996 LocalTuya: No mapping found for device: Vaatwasser
sub device: countdown_1
2024-10-06 14:13:39.997 LocalTuya: No mapping found for device: Vaatwasser
sub device: relay_status
2024-10-06 14:13:39.997 LocalTuya: No mapping found for device: Vaatwasser
sub device: overcharge_switch
2024-10-06 14:13:39.997 LocalTuya: No mapping found for device: Vaatwasser
sub device: light_mode
2024-10-06 14:13:39.997 LocalTuya: No mapping found for device: Vaatwasser
sub device: cycle_time
2024-10-06 14:13:39.997 LocalTuya: No mapping found for device: Vaatwasser
sub device: random_time
2024-10-06 14:13:39.997 LocalTuya: No mapping found for device: Vaatwasser
sub device: switch_inching
2024-10-06 14:13:39.998 LocalTuya: Run Startup script
2024-10-06 14:13:39.998 LocalTuya: No mapping found for device:
Batterijlader sub device: countdown_1
2024-10-06 14:13:39.998 LocalTuya: No mapping found for device:
Batterijlader sub device: relay_status
2024-10-06 14:13:39.998 LocalTuya: No mapping found for device:
Batterijlader sub device: overcharge_switch
2024-10-06 14:13:39.998 LocalTuya: No mapping found for device:
Batterijlader sub device: light_mode
2024-10-06 14:13:39.998 LocalTuya: No mapping found for device:
Batterijlader sub device: cycle_time
2024-10-06 14:13:39.999 LocalTuya: No mapping found for device:
Batterijlader sub device: random_time
2024-10-06 14:13:39.999 LocalTuya: No mapping found for device:
Batterijlader sub device: switch_inching
2024-10-06 14:13:40.000 LocalTuya: Run Startup script
2024-10-06 14:13:40.000 LocalTuya: No mapping found for device: Wasmachine
sub device: countdown_1
2024-10-06 14:13:40.000 LocalTuya: No mapping found for device: Wasmachine
sub device: relay_status
2024-10-06 14:13:40.000 LocalTuya: No mapping found for device: Wasmachine
sub device: overcharge_switch
2024-10-06 14:13:40.000 LocalTuya: No mapping found for device: Wasmachine
sub device: light_mode
2024-10-06 14:13:40.000 LocalTuya: No mapping found for device: Wasmachine
sub device: cycle_time
2024-10-06 14:13:40.000 LocalTuya: No mapping found for device: Wasmachine
sub device: random_time
2024-10-06 14:13:40.000 LocalTuya: No mapping found for device: Wasmachine
sub device: switch_inching
2024-10-06 14:13:40.002 LocalTuya: Run Startup script
Op vr 4 okt 2024 om 23:01 schreef Xenomes ***@***.***>:
… Gevonden! De JSON zonder schaal veroorzaakte een fout, opgelost in versie
0.5a.
Found it! The JSON without scale caused an error, fixed in version 0.5a.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7K66MCSAY6ZKZ7PBCMF2QLZZ3X2TAVCNFSM6AAAAABOYEHUFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJUGQ4DKMBXGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Dat is goed, dit zijn debugmeldingen voor mappings die geen apparaat krijgen in Domoticz. Als je de debugmodus uitschakelt bij de plugin, verdwijnen ze. That's fine, these are debug messages for mappings that don't receive a device in Domoticz. If you turn off debug mode in the plugin, they will disappear. |
Switches seems to randomly get on/off
Can not reproduce it exactly
The text was updated successfully, but these errors were encountered: