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

Missing status field on Objects for Netatmo Door and Windows Tags #199

Open
henesseye opened this issue Sep 6, 2024 · 5 comments
Open

Comments

@henesseye
Copy link

Describe the bug
With the adapter 3.1.0 i don't get the status field in the objects of my door and window tags. in the previous version there was a status field (Monitoring on/off which represented the actual status of the tag. open / closed.

Bildschirmfoto 2024-09-06 um 11 45 43

if I do a request on the API directly from netatmo dev section i get the following information for the tag

Bildschirmfoto 2024-09-06 um 11 48 38

Versions:

  • Adapter version: 3.1.0
  • JS-Controller version: 6.0.11
  • Node version: v20.17.0
  • Operating system: linux docker (official image - v10.0.0)
@henesseye
Copy link
Author

henesseye commented Sep 6, 2024

Extract from the log. as you can see, there is the status in the response, but the state is not listed/updated in objects in iobroker:
{"id":"70:ee:XX.XX:8a:08","type":"NACamDoorTag","battery_state":"low","battery_level":4520,"firmware_revision":58,"rf_state":"medium","rf_strength":66,"last_seen":1725620543,"last_activity":1725427324,"reachable":true,"bridge":"70:ee:50:XX:XX:3e","status":"closed"}

@henesseye
Copy link
Author

henesseye commented Sep 6, 2024

another hint.
there are differences between V 2.0.5 on the left side (correct status) and V 3.1.0 on the right side (no status)

image

@henesseye
Copy link
Author

i manually changed the code from monitoring to status and now i see the correct status in the objects. please check and deploy this as an update

@ThomasSteudner
Copy link

Hi there,
That fixes my issue.
thanks.

@Apollon77
Copy link
Collaborator

Hm ... are you sure that not other devices report "monitoring"? because the change likely was done with a reason ..... maybe simply have both ... need to think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants