-
Notifications
You must be signed in to change notification settings - Fork 37
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
DECT Window sensors #81
Comments
Hi, I don't think this is currently implemented due to examples. Thanks for the output. I will try to add it asap. Inlet you know once it has been added. |
Hi, I had a quick look at it and it seems that this integration takes a little bit longer then I thought. <devicelist version="1" fwversion="7.29">
<device identifier="11324 0299919" id="413" functionbitmask="1" fwversion="30.17.02.02.011" manufacturer="0x2c3c" productname="HAN-FUN">
<present>1</present>
<txbusy>0</txbusy>
<name>Keller</name>
</device>
<device identifier="11324 0299919-1" id="2000" functionbitmask="8208" fwversion="0.0" manufacturer="0x2c3c" productname="HAN-FUN">
<present>1</present>
<txbusy>0</txbusy>
<name>Keller</name>
<etsiunitinfo>
<etsideviceid>413</etsideviceid>
<unittype>513</unittype>
<interfaces>256</interfaces>
</etsiunitinfo>
<alert>
<state>0</state>
<lastalertchgtimestamp>1665073872</lastalertchgtimestamp>
</alert>
</device>
</devicelist> for some reason the device shows up twice in the list. Then we need It appears that the second device is a "sub-device" of the first one. Like a chassi with additional modules. How does this look like in your FritzBox UI. Do you mind sharing? |
Well, reading the Documentation helps 😅
Then let's add these device types. |
I can run from source, if you want me to try something out. |
Started implementing this but won't be able to finish it today. The next few days I will definitely get back to your offer 😉 |
Hi, I added support for "HUN-FUN" devices. Can you please check out Thank you |
I can see that it does something:
I can also see new fields (
I'm not sure how useful that will be. However, what I don't see is some simple field for "door/window is open". Should there be one? |
Hi @pohly, it was late last night and added some bugs as well for good measure. I just pushed a change. Can you have a look if the data looks better now and all fields you are expecting are shown in DEBUG output? Thank you |
Looks good now, thanks!
|
It's interesting that the unit types of the magnetic and optic sensors are different. They perform exactly the same function. |
great to hear, now I need to somehow add these devices to the HA dashboard |
Hi @pohly, I added an updated version of the home automation dashboard. Can you try it out and see if this works for you? Thank you |
I tried uploading grafana/influx2_dashboards/fritzbox_home_automation_dashboard.json to Grafana v9.6.1. What confused me initially was that the the UI for the query doesn't show where the specified field gets selected. In the JSON, that is here: Are you writing that by hand or am I missing something in the Grafana UI? Then there's the problem that it doesn't find any data. I am pointing it at a "fritz-box" data source backed by influxdb with "InfluxQL" as query language. Is that perhaps the problem? |
Yes, it was. Reconfiguring the source to use Flux fixed it. I also found that I had to set a default bucket in the Grafana source, otherwise I got a "bucket not set" error in the dashboard. Should the dashboard have a way to select the bucket? |
Not really, all dashboards should use the same bucket. If more then one box is used then they can be separated by the box tag. It should be described here: https://github.com/bb-Ricardo/fritzinfluxdb/blob/main/README.md#grafana |
If this works for you I would close this issue. |
But not all of my dashboards are for data gathered by fritzinfluxdb. I have one bucket configured for it and another bucket where telegraf stores its data. Anyway, I guess I can work around this (if it's a workaround, not sure) by defining different sources for the same influxdb, each with a different default bucket. Feel free to close this issue, I think it all works as intended. Thanks for your support! |
Maybe I should add a variable to all Dashboards and set it to default bucket by default. What do you think? |
Such a solution sounds better to me, but I am not a Grafana/InfluxDB expert. |
Unfortunately, this is not so easy as I thought. Yes, the easiest would be a second data source with the correct bucket defined and to use this for the dashboards. |
Should https://github.com/bb-Ricardo/fritzinfluxdb/blob/main/fritzinfluxdb/classes/fritzbox/service_definitions/homeauto.py (from #44?) already work for window and door sensors (for example, https://www.smarthome.de/geraete/smarthome-tuer-fensterkontakt-optisch-weiss)?
I updated to 1.1.0 and I can see that something gets stored in influxdb:
But there's no field for "open/closed".
Here's the result of
http://fritz.box/webservices/homeautoswitch.lua?sid=[SesionID]&switchcmd=getdevicelistinfos
Note the difference between one sensor which is closed:
and one which is open:
<alert><state>
changes. I double-checked that it goes back to 0 when closing.The text was updated successfully, but these errors were encountered: