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

JA-80T functionality #17

Closed
phrachovina opened this issue Jan 18, 2022 · 29 comments
Closed

JA-80T functionality #17

phrachovina opened this issue Jan 18, 2022 · 29 comments
Assignees
Labels
awaiting test bug Something isn't working

Comments

@phrachovina
Copy link

I have a JA-80T cable that doesn't work with this. However, I am able to perform beta testing and provide the necessary logs for debugging
jablotron.log
.

@mattsaxon
Copy link
Collaborator

Thanks, so looking at the logs, it looks like it is reading correctly, but not sending messages, is that correct?

So can you see the entities in HA and they are correctly updated? But you can set the system with HA?

@phrachovina
Copy link
Author

No, I click the Add integration of Jablotron80, choose JA-80T cable in the port /dev/ttyUSB0 and the master code, and th process wil end with an error "Could not read settings! Is system disarmed?". No entities was added. I enclose the current logs.
jablotron2.log

@mattsaxon
Copy link
Collaborator

Thanks, ok there a set of unknown messages types in there; 0, 1, 24, 64, 255

I suspect that is the issue and we have the information for now to progress. Appreciated.

@mattsaxon mattsaxon added the bug Something isn't working label Feb 2, 2022
@tahvane1
Copy link
Owner

tahvane1 commented Feb 2, 2022

I'm suspecting that command to enter elevated mode is somehow different with this cable.

@mattsaxon mattsaxon added question Further information is requested and removed bug Something isn't working labels Feb 10, 2022
@mattsaxon
Copy link
Collaborator

Yes, I see what you mean from the logs.

@phrachovina can you confirm that by entering *0 and your master code on the keypad you are able to enter "Service Mode".

Note that this code is the code you should be entering into HA during setup on the integration. If you are not entering that code, then the integration will not install and you get the above error.

@phrachovina
Copy link
Author

In JA-80 system are 3 types of codes: common, master and service. Maste code enter maintenance mode and service code enter service mode. I tried master and service codes, but neither worked. I am adding new logs
jablotron3.log
.

@mattsaxon
Copy link
Collaborator

On can you confirm to enter this from keypad, on y or system is *0 follow by SC or MC? And that this works?

@phrachovina
Copy link
Author

Yes, of course, it works. Master code enter maitenance mode and service code service mode, but service code should not be used. By default, the service code is known only to the installer, not to the user.

@mattsaxon
Copy link
Collaborator

Understood.

The only way I can think to proceed is that we will need a serial trace from you entering the master code in OLink. I'm very surprised that there is an issue as I can't see why the cable would impact this and the logs clearly show data coming back in the opposite direction fine.

@phrachovina
Copy link
Author

Ok, here are the packets from Olink when I enter the master codde:
packets.txt

@mattsaxon
Copy link
Collaborator

Thanks, can I ask if you've successfully used this integration https://github.com/fwpt/HASS-Jablotron80-T?

@mattsaxon
Copy link
Collaborator

With regard to the trace, I think this may be the received data on serial. Can you do a similar trace, but with the sent data when entering the code from the keypad in OLink, rather than at the physical keypad?

@phrachovina
Copy link
Author

I actually entered the code through Olink's keypad.
I also tried the integration Jabkitron80-T, but unfortunately it doesn't work.

@mattsaxon
Copy link
Collaborator

So for that trace, is it the data received or sent, it looks like it is data received at least. Can you create one for data sent only.

On the topic of it not working with the integration, https://github.com/fwpt/HASS-Jablotron80-T, since I don't have a cable, its going to be tough for me to get this working. Have you raised with the author, @fwpt?

@phrachovina
Copy link
Author

I don't know, how to catch packets from each side. In the Olilnk SW there are colors, so I upload picture of this while I'm sending the master code
packets

@mattsaxon
Copy link
Collaborator

Thanks, I wasn't aware of that tool, but comparing it to my output, it looks compatible. I'll take a closer look later too.

I've contacted fwpt on the home assistant forum and they have the cable working perhaps you should make contact and see if you can work out what is wrong between you given you have same hardware.

@mattsaxon
Copy link
Collaborator

@phrachovina can I confirm that you've been changing your master code throughout these logs to be different codes?

@phrachovina
Copy link
Author

I used 3 types of codes - user, master and service code. The service code cannot be used for normal use. As well as the master code, It can be used for initial configuration loading, but for normal use, only the user code is used, which is different for all members of the household.

@mattsaxon
Copy link
Collaborator

I'm referring to the logs that are shown in this thread. I see 4 different codes being used, is that because you've changed you ur code? Since only master and service can be used for initial setup, I'd expect to see 2 maximum in the logs, but I see 4.

@phrachovina
Copy link
Author

I used only 3 codes, master, service and my user code.

@mattsaxon
Copy link
Collaborator

Yes I see that now sorry.

mattsaxon added a commit to mattsaxon/jablotron80 that referenced this issue Mar 18, 2022
@mattsaxon mattsaxon added bug Something isn't working awaiting merge and removed question Further information is requested labels Mar 18, 2022
@mattsaxon mattsaxon self-assigned this Mar 18, 2022
@mattsaxon
Copy link
Collaborator

@phrachovina can you try testing with the latest release?

@phrachovina
Copy link
Author

phrachovina commented Mar 19, 2022

I tried it twice, it ran out for the first time, the devices appeared, but after sending it ended in an error "interrupted". The second attempt to add integration ended with the same error as before. I enclose logs
jablotron4.log
.

@mattsaxon
Copy link
Collaborator

Can you try the latest release please (0.25), I've resolved one of the issues you are getting, the first one.

I'm not sure on the second yet, but i've managed to get mine setup, its definitely unreliable at the moment, but I can usually get mine setup with 3 attempts with the latest code. If you get it setup its a bit more reliable, but certainly not perfect. I want to see if you are having same situation as me, I suspect you are.

(Note I haven't got a JA-80T cable, I've lashed up something similar by hand!)

@phrachovina
Copy link
Author

Same situation - Could not read settings! Is system disarmed? Log included
jablotron5.log
.

@mattsaxon
Copy link
Collaborator

Significantly improved in my testing with release 0.26

@phrachovina
Copy link
Author

Great, it looks like it works. My devices have been loaded, I haven't named them yet, I hope it will change later. I'm not home now, so I won't fully try it until this afternoon. Sending current logs for review
jablotron6.log
.

@mattsaxon
Copy link
Collaborator

No errors or warnings, looks good to me

@phrachovina
Copy link
Author

Yes, great job, thanks very much. 👍

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

No branches or pull requests

3 participants