This project has been archived by its maintainers, and is no longer receiving any updates.
python_freeathome_local
The datamodel of the Free@Home Rest-API is setup the following way:
- The root-node is a SysAp
- The SysAp contains devices and a floorplan
- Each device has 1 to many channels (the behaviour of a channel is defined by the FunctionID)
- A channel has 0 to many Input- and Output-Datapoints (the behaviour of a datapoint is defined by the PairingID)
- An Input-Datapoint is used to set a value (e.g. turn on a switch) -- To change the value of an such a datapoint a PUT-call is needed
- An Output-Datapoint shows the current state (e.g. switch is on) -- All modifications are reported through a websocket-connection
- A device and a channel can have 0 to many parameters (the function of a parameter is defined by the ParameterID)
Drawback
The major drawback I see so far regarding the Rest-API is that the parameters can't be controlled. E.g. the WeatherStation has a parameter called 'par0039' (TRANSMISSION_INTERVAL), which defines how often updated values are send. This interval can be changed in the mobile app, but not through the Rest-API, additionally (what is even more worse) any modifications are not reported through the websocket. This means that after the initial load of the configuration any modifications to the parameters through the mobile app are not recognized by this library :(
Implemented channels
| Name | Inputs | Outputs |
|---|---|---|
| BrightnessSensor | - | brightness_level (float) - state brightness_alarm (bool) |
| RainSensor | - | rain_alarm (bool) - state rain_sensor_activation_percentage (float) rain_sensor_frequency (float) |
| TemperatureSensor | - | outdoor_temperature (float) - state frost_alarm (bool) |
| WindSensor | - | wind_speed (float) - state wind_alarm (bool) wind_force (float) |
| Trigger | timed_start_stop - press | - |
| SwitchActuator | switch_on_off (bool) - turn_on/turn_off forced (bool) timed_start_stop (bool) timed_movement (bool) |
info_on_off (bool) - state info_force (bool) info_error (bool) |
| WindowDoorSensor | - | window_door (bool) - state |
| MovementDetector | info_on_off | info_on_off (bool) - state brightness_level (float) timed_movement (bool) timed_presence (bool) |
| SwitchSensor | - | switch_on_off (bool) - state |
| ForceOnOffSensor | - | forced (bool) - state |
| BlindSensor | - | stop_step_up_down (bool) - state |
| DesDoorRingingSensor | - | timed_start_stop (bool) - state |
Metadata
Release files for python-freeathome-local 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| python_freeathome_local-0.0.6.tar.gz | 45.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_freeathome_local-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 107.6 kB
Release files / python_freeathome_local-0.0.6.tar.gz
| Download URL | python_freeathome_local-0.0.6.tar.gz |
|---|---|
| Size | 45.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53015e2f361255dfcebd1311984dc10685db4a9e9b3d1455eb932f12dde045c6
|
|
BLAKE2b-256 checksum How to use checksums |
0f4c28f1429a07e07c449b7c8c5535c304c3e53ca5c4d80affba9125b68a1ab8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Release files / python_freeathome_local-0.0.6-py3-none-any.whl
| Download URL | python_freeathome_local-0.0.6-py3-none-any.whl |
|---|---|
| Size | 62.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1220aac5aed5834d73fdff0b2251f8d14592462c89cc6697afdbcba6ac73053e
|
|
BLAKE2b-256 checksum How to use checksums |
818135e9fe3d2a5d54ffa7bf875b7fcd9cd387c638ce6e2f5d09f9def242ed94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for python-freeathome-local 0.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.