Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Lack of tamper / RF Jamming notifications or log messages #69

Open
simontrimmer opened this issue Aug 27, 2022 · 0 comments
Open

Lack of tamper / RF Jamming notifications or log messages #69

simontrimmer opened this issue Aug 27, 2022 · 0 comments
Assignees

Comments

@simontrimmer
Copy link

Not a bug report but I did get a series of notifications yesterday from the official texecom smartcom app about RF jamming, looking today there is nothing indicated in the container log that indicated anything occurred, just the regular power log lines at the same seconds offset in the minute. Looking at the alarm log via wintex I can see tamper event group messages around "Radio Jamming Alarm" and "Radio Jamming Restore", you'd expect tamper alarms to be reported? If classification of unusual events is an issue, perhaps enabling an unfiltered log from the com port is a possible debug feature?

In this case I suspect the RF jamming messages are indicative of a battery in a sensor running down, but I'd preferred to have gotten the telemetry from HA rather than the texecom app as there is the possibility of more metadata (e.g. the texecom app didn't indicate which device was lost from the mesh)

Premier Elite 48 with a ricochet expander

HA at 2022.8.6
texecom2mqtt container at v1.2.3
container log captured at debug level

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants