-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Comments
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? |
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. |
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. |
I'm suspecting that command to enter elevated mode is somehow different with this cable. |
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. |
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 |
On can you confirm to enter this from keypad, on y or system is *0 follow by SC or MC? And that this works? |
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. |
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. |
Ok, here are the packets from Olink when I enter the master codde: |
Thanks, can I ask if you've successfully used this integration https://github.com/fwpt/HASS-Jablotron80-T? |
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? |
I actually entered the code through Olink's keypad. |
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? |
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. |
@phrachovina can I confirm that you've been changing your master code throughout these logs to be different codes? |
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. |
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. |
I used only 3 codes, master, service and my user code. |
Yes I see that now sorry. |
@phrachovina can you try testing with the latest release? |
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 |
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!) |
Same situation - Could not read settings! Is system disarmed? Log included |
Significantly improved in my testing with release 0.26 |
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 |
No errors or warnings, looks good to me |
Yes, great job, thanks very much. 👍 |
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
.
The text was updated successfully, but these errors were encountered: