-
Notifications
You must be signed in to change notification settings - Fork 17
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
can't get away from eavesdropping mode. #60
Comments
As per the warning message, your schema file or known_list appears to be missing. Have you defined these? |
I'm afraid I don't understand what I have to do for that. what I attached are the files as created after a normal run of evogateway.py. From what I see there is a known_list in ramses_rf_schema.json. It's not clear for me how I have to create a schema file and/or known_list. |
A default schema file is automatically generated by the script, once it has been running for a period of time and has managed to "snoop" the evohome devices in your system. This is then saved as You can now edit this schema file with e.g. a text editor or VSCode etc, and in the The format of the known_list section should be something like:
Unless you are experiencing spurious messages from unwanted neighbouring devices etc, it should be fine to continue using the system even with that known_list warning. Finally, you may find further information on the whole schema and known_list etc at the ramses_rf repo. |
I've tried a couple of things but still no luck. My ramses_rf_schama.json file, it contains a know list:
If I start the script it shows:
And if I stop the script a new ramses_rf_schema.json file is written without my changes. This fits with what's written in de readme.rm: "This file should not normally need to be manually edited (previous versions are overwritten with the current version)." |
As long as it is not defaulting to evesdrop mode, you can ignore the above message I think. |
I'm having the same issue. Each time I start the gateway eavesdropping starts and a new ramses file is generated when I stop the gateway. |
I've not yet a solution, it's for me indeed still the same. |
I will try put some time aside over the festive period to have a look at this properly. |
@PRoomberg - which versions of ramses_rf are you using? I have just tried out installing on a clean vm. Other than an error with the Are you both saying that your |
I'm running 0.22.4. And yes, each time the gateway starts it shows these lines:
|
The ramses_rf version is fine. I noticed that your schema missing warning is showing as line 1137. However, in the current code, that line is a blank, and that specific warning is on line 1135. Can you check that you are running the latest version of evoGateway, and if so, see if you can identify where the extra 2 lines are in your version? Also separately, I assume there are no file permission issues? Are you running on Windows by any chance? |
I was a bit lazy and copied those lines from a post above.
|
Can you post any output text prior to this line. I am specifically looking for a loading schema mesage or a schema not found message. |
This is my log of a short run:
|
There is no prior output. Only the command prompt with the start of the python script. The same as blb4github shows above. |
I don't think this is the problem, but for good order, can you try using the latest master, which is at version 3.14 (this has not been tagged, so just download the Are you confident that there are no file permissions issues? |
Also getting the same prob:
also ending up with mutiple saved shema and devices.json files |
Can you try adding the following into line 1137, and see what it shows:
|
Certainly, will. Should be able to get back to this over the weekend |
Guess you after this bit:
|
I'm getting the same results as above when I add that line. |
That's as expected, as the line was only to show us the value of those variables. Can you post your config file as well. |
|
Here's my config:
|
Thanks. Can you add the following to the bottom of your config file, and give it a try:
|
Added it and restarted. Now this messages is shown in the events.log
But no lines after that. Removed the parameter and restarted again.
Followed by real events. |
Firstly, I will say that despite this minor problem this is an extremely helpful module. Many thanks for the effort put into this, it has saved me a boat load of headaches, excellent work. I have added the requested and also get the same:
It goes no further than that. Changing the value to false and restarting resolves, but back to:
|
Thanks for trying. Very odd. It seems to be getting stuck on opening the schema file. Are you sure file permissions are ok etc? Are you running on linux or Windows? |
Linux, raspberry pi 5. Everything (incl the directory itself) has the same owner (current user) and group. I have tried this running standalone from the command line and as service run as either root or user - same result |
If you've tried with root, then it most likely is not a permissions issue then. If you are up for it, can you replace lines 1121 to 1132 in the main script with the following:
Please try this with the |
I'm running Ubuntu 20.04.6 LTS in a VMware virtual machine on a Mac. I've added the checkpoints to the code but didn't see any details in the events.log.
That gave a better result:
|
With the print statements, they would only show on the screen, and not go into the log file. But good job on logging all the checkpoints. These all look fine and can be removed. Can you try putting one in the remainder of that function, and particularly at the end, just before the If the checkpoints show that the end of function is reached correctly, then the next thing to check is your schema file itself and see if there is anything there that is making it hang. |
okay managed to get mine to work. All the checkpoints looked good on mine and the function was returning correctly. It was then failing at this point:
I put an exception handler round this
and it returned this
Not fully understanding your code I removed the double asterisk relating to the arguments for lib_kwargs.
To this:
This then allowed it to run, although not sure if right or not. Does this help? |
Great detective work! The problem appears to be in the schema file (the above double asterisk is so that we pass a pointer to the parameters collection, rather than a single individual parameter value - the reason it "works" without the asterisks is that your schema file parameters are no longer being sent to the underlying ramses gateway - i.e. your schema file contents are being completely ignored). The error says that there is a key in your schema file that is not being accepted. I recall that the underlying ramses library had a few changes in the schema file structure at about the time of the last update of evoGateway, and so it is possible that something has slipped through. Can you remove the |
Removed the |
It seems as if there may be one or more further issues with your schema. Can you try removing sections at a time from the schema and see if you can pin down which part is causing the issue? |
@dmsviento did you discover anything more? |
Apologies, been away with work. Plan on getting back to it this weekend |
I think this is the same issue I had, which is resolved here: |
I've tried all kind of things based on the readme and the issues reported earlier, but I can't get away from eavesdropping mode. I hope someone can help!
The log I receive whe starting up:
:~/scripts $ python evogateway.py
2023-08-29 12:36:26,710 [1137] Schema file missing or the 'known_list' section is missing. Defaulting to ramses_rf 'eavesdropping' mode
Best practice is exactly one gateway (HGI) in the known_list: []
It is strongly recommended to provide a known_list, and use it as a whitelist (device_id filter), configure: enforce_known_list = True
2023-08-29 12:36:26 |
2023-08-29 12:36:26 | ------------------------------------------------------------------------------------------
2023-08-29 12:36:26 | Devices loaded from 'devices.json' file:
2023-08-29 12:36:26 | CTL 01:187689 - Controller
2023-08-29 12:36:26 | TRV 04:032215 - TRV:032215
2023-08-29 12:36:26 | TRV 04:032217 - TRV:032217
2023-08-29 12:36:26 | TRV 04:095385 - TRV:095385
2023-08-29 12:36:26 | TRV 04:202711 - TRV:202711
2023-08-29 12:36:26 | TRV 04:202713 - TRV:202713
2023-08-29 12:36:26 | TRV 04:202715 - TRV:202715
2023-08-29 12:36:26 | TRV 04:202717 - TRV:202717
2023-08-29 12:36:26 | HGI 18:000730 - evoGateway
2023-08-29 12:36:26 | ------------------------------------------------------------------------------------------
2023-08-29 12:36:26 |
2023-08-29 12:36:26 | # evogateway 3.11-0.22.40 (using 'ramses_rf' library 0.22.40)
Not using any device filter: using a known_list (as a whitelist) is strongly recommended)
My devices.json and ramses_rf_schema.json files:
devices.json.txt
ramses_rf_schema.json.txt
The text was updated successfully, but these errors were encountered: