-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Sabotage #79
Comments
I’m sorry I don’t understand |
When i connect rpi via USB to Jablotron, cant control any PGs. After few minutes Jablotron triggers a sabotage alarm code entry attempts exceeded Using code for admin with all permissions |
are you CZE ? |
Do you have service code? Can you check your Jablotron settings if there’s a option to disable the behaviour that triggers the sabotage alarm? The integration mimics F-link behaviour so it has to send code every minute. |
Yes im using service code. |
I don’t think using service code for the integration is good idea. |
today I will try to reinstall the integration and set it up again |
You don’t have to reinstall integration - just change the code in options. |
added a new user with new code and rights to control pg same problem...... code entry exceeded Have JA-107K |
I have JA-118M to control the lights. What kind of device should i set ? |
|
its some issue with devices ..... JA-118M module maybe. if I turn off the device the sabotage alarm will not start |
@schift85 is it possible to manage the module/lights via F-link? |
yes, it is posible |
If you can debug the connection via Wireshark, we can be able to add support for the lights. |
Tato chyba pochází z vlastní integrace. Logger: homeassistant.config_entries Error setting up entry Jablotron for jablotron100 During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Tato chyba pochází z vlastní integrace. Logger: custom_components.jablotron100 Service unavailable: |
The main reason for this error is that that user with given code does not access to devices. |
I log in to f-link with the same code. |
I also tried the initial settings without the device, the integration works, but the PG cannot be controlled. When I turn on the PG via F-link, I see a status change in the integration |
|
jakmile v nastavení zapnu zařízení, integrace koncí chybou |
There was one user that reported similar problem - he has asterisk in the pin code. However I'm not sure if pin code without asterisk will help. |
PIN without * not work :-( |
i tried jablotron cloud with the same user (PIN) and everything works. Unfortunately I can only use PG |
You can try to enable debug (see README) and send the startup logs. |
if I tick only pg and leave the device unchecked, the integration comes without error. the problem is that pg cannot be controlled. it turns off by itself after a few seconds and returns to the off state |
Please try to solve one problem at once. I don't know currently if we try to solve devices or PG outputs... |
im not sure where is startup log |
Tato chyba pochází z vlastní integrace. Logger: custom_components.jablotron100 Service unavailable: |
One idea - the problem may be with just one device. You can try to enable one device, check if integration works. Then enable second device etc |
if I set only the first device (keyboard) the integration is loaded in the queue. when I add another device (radio module) the integration ends with an error |
if I switch the radio module to empty and try another device (motion detector) the integration ends with an error |
Please try to enable DEBUG (see README) and send the full log |
DEBUG enabled but i dont know what kind of log you want |
Please enable logging of all incoming and outcoming packets. Then try to enable the motion detector (device 3) and send all integration logs when the error occurs. |
2023-08-11 22:13:30.441 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs 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
|
Why are in the logs devices 1 and 8? Where are numbers 2-7? |
1-keyboard |
if i set only one device, integration work great..... tested on PIR |
So devices 8 and 9 don't work together? |
no, single device work, it doesn't matter what device it is if i set up any two devices together = error |
This is "invalid login" packet. So there's something wrong with the user/code. There's bug in the integration and the error is not reported when device is just one - however there's the same problem with one device (I see it in the logs). Are you able to install integration directly from GitHub (not from HACS) when I prepare specific testing version for you? |
I can definitely install primo integration from github. Would it be possible to communicate via email in the Czech language? Thanks |
@schift85 you can use Discord |
Version to test: https://github.com/kukulich/home-assistant-jablotron100/tree/test |
I installed the test version and added all the devices and the integration of the writing setup failed |
2023-08-12 08:41:10.755 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs 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
|
There’s stil the same login error - it looks there’s a problem with the user. I don’t have 107 so I don’t know what to do. You can use Discord chat - somebody may help you. |
the unit announces an alarm due to frequent entry of the security code
The text was updated successfully, but these errors were encountered: