Skip to content
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

No handler for message 5 #126

Closed
Trefex opened this issue Jan 3, 2020 · 8 comments
Closed

No handler for message 5 #126

Trefex opened this issue Jan 3, 2020 · 8 comments
Labels
bug Something isn't working to be confirmed Reported but not yet confirmed
Milestone

Comments

@Trefex
Copy link
Contributor

Trefex commented Jan 3, 2020

2020-01-03 13:25:54,314 - ERROR    - PAI.paradox.lib.async_message_manager - No handler for message 5
Detail: Container: 
    fields = Container: 
        data = b'RG\x80\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 70)
        value = Container: 
            po = Container: 
                command = 5
                status = Container: 
                    reserved = False
                    alarm_reporting_pending = False
                    Winload_connected = True
                    NeWare_connected = False
            packet_length = 71
            control = Container: 
                ram_access = True
                eeprom_address_bits = 0
            bus_address = 0
            address = 2
            data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 64)
        offset1 = 0
        offset2 = 70
        length = 70
    checksum = b'\x1b' (total 1)

I receive this sometimes when doing some arming / disarming via Home Assistant.

I have not seen that many errors when running the docker on my Windows PC, but i see this now more frequent when running on the Docker NAS.

Is the async handler robust or is something wrong in my setup?

@Trefex Trefex added bug Something isn't working to be confirmed Reported but not yet confirmed labels Jan 3, 2020
@Trefex
Copy link
Contributor Author

Trefex commented Jan 3, 2020

Using tag latest from DockerHub.

@Trefex
Copy link
Contributor Author

Trefex commented Jan 3, 2020

Might be coincidence with arm/disarm as i receive also this message 4-5 mins after arm/disarm.

@yozik04
Copy link
Collaborator

yozik04 commented Jan 3, 2020

dupe #89
Happens sometimes and it is fine. Reason unknown.

@yozik04 yozik04 closed this as completed Jan 3, 2020
@yozik04 yozik04 added this to the 2.0.0 milestone Feb 3, 2020
@Trefex
Copy link
Contributor Author

Trefex commented Aug 20, 2020

Hi @yozik04 i still experience this with version 2.2.0

@drzoidberg33
Copy link

drzoidberg33 commented Feb 27, 2024

I've just set PAI using ESP32 Serial -> IP method, everything seems to work but I'm getting these error messages every few seconds.

Mine look pretty much the same as OPs:

2024-02-27 21:28:46,393 - ERROR    - PAI.paradox.lib.handlers - No handler for message 5
Detail: Container: 
    fields = Container: 
        data = b'R\x00\x80\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 36)
        value = Container: 
            po = Container: 
                command = 5
                status = Container: 
                    reserved = False
                    alarm_reporting_pending = False
                    Winload_connected = True
                    NeWare_connected = False
            validation = 128
            address = 2
            data = b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'... (truncated, total 32)
        offset1 = 0
        offset2 = 36
        length = 36
    checksum = b'\xdc' (total 1)

I have the ESP32 serial connection piggy-backing off the serial output on my Olarm Pro (https://olarm.com/products/olarm-pro-4g) and I wonder if that's causing this potentially.

I don't want to lose the Olarm as it is useful and I'm already paying for the subscription through my security company.

I'm currently using PAI through the HA Addon on version 3.4.0 with a MG5050 (only the one serial connection which is why I'm using the one on the Olarm).

@yozik04
Copy link
Collaborator

yozik04 commented Feb 27, 2024

@drzoidberg33 it is fine, relax 😎

@drzoidberg33
Copy link

@drzoidberg33 it is fine, relax 😎

Thanks, it's working great btw, but I've only had it up for 30 minutes so far 👍

@yozik04
Copy link
Collaborator

yozik04 commented Mar 30, 2024

I have added IO_TIMEOUT setting. Please try to play with it. Default is 0.5 seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working to be confirmed Reported but not yet confirmed
Projects
None yet
Development

No branches or pull requests

3 participants