Support for FTW04 #49
Comments
|
This looks good ! here is the result Edited by @gaetancollaud to keep only the revelant part and keep this thread short. {
"data": {
"type": "apartmentStatus",
"included": {
"dsDevices": [
{
"id": "302ed89f43f0000000002d000004345d00",
"type": "dsDeviceStatus",
"attributes": {
"functionBlocks": [
{
"id": "302ed89f43f0000000002d000004345d00"
}
],
"submodules": [
{
"id": "302ed89f43f0000000002d000004345d00",
"operationsLocked": false
}
]
}
}
],
"zones": [],
"userDefinedStates": []
}
}
} |
|
Thanks @jtognazzi but I don't see the values of the sensors, could you try this one please: curl -k -X GET --location "https://HOSTNAME:8080/api/v1/apartment/dsDevices/status" -H "Authorization: Bearer API_KEY"Il will edit your previous answer to keep only the important part |
|
Actually, the temperature and humidity values appears under the zones list as type zoneStatus. and following your request pattern, I tried this request also I hope it helps. |
|
Sorry for truncating your first message a bit too quickly. I didn't checked the zones. It's interesting, this means instead of focusing on the devices sensors I could concentrate on the zones. And I see that the application temperature has a Thanks for your help |
|
Actually my dss server doesn't expose the temperature application, so it wil be really tricky for me to test. Could you try this and tell me if it has any effect on our system ? The response will be empty but maybe you can see in digitalStrom web UI that something changed. BE AWARE, this will modify the set point of your zone number 6: curl -X PATCH --location "https://HOSTNAME:8080/api/v1/apartment/zones/6/status" \
-H "Authorization: Bearer API_KEY" \
-H "Content-Type: application/json" \
-d '[
{
"op": "replace",
"path": "/applications/temperature/setpoint",
"value": 20
}
]'I'v see that you also have a different set point for different mode like night etc. so i've no idea what the behavior will be regarding this application (again I don't have it I cannot test it myself). Those settings cannot be set through the API, so maybe it's a dead end anyway. |
|
Yes, it worked !
|
|
Cool, thanks for the confirmation. I have this app, but no devices so it's in "off" mode all the time. I could try to start implementing, but it would be a lot of back and forth with you and would be realy tidious. I've reached to digitalStrom AG to see if they can lend me a device to test. I don't need them and I personnaly don't want to invest 200chf (FTW04) + 100chf (BL) for an opensource app that I already develop on my free time. Let's hope they accept. |
|
Sure, I fully understand. Thanks anyway |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should easily be able to support sensors like the FTW04.
The implementation should be similar to metterings, we could do a pooling every now and then for the sensors and report the value to MQTT.
Since I personally don't own such devices it will be difficult for me to implement but I can try to mock the response. If someone would be kind enough to run this command and give me the result, I would appreciate it (don't hesitate to remove personal information I just need an example) ? This command will get the current status of the appartment (including the sensors value).
Structure example:
{ "data": { "included": { "dsDevices": [ { "id": "302ed89f43f0000000002d000004345d00", "type": "dsDevice", "attributes": { "name": "Room 2", "gtin": "4251161900036", "dsid": "302ed89f43f02d000004345d", "displayId": "0004345d", "present": true, "submodules": [ "302ed89f43f0000000002d000004345d00" ], "zone": "1", "controller": "302ed89f43f0000000000e400000c9bb00" } } ], "submodules": [ { "id": "302ed89f43f0000000002d000004345d00", "type": "submodule", "attributes": { "name": "Room 2", "technicalName": "FTW04 dS", "dsDevice": "302ed89f43f0000000002d000004345d00", "functionBlocks": [ "302ed89f43f0000000002d000004345d00" ], "zone": "1", "application": "joker" } } ], "functionBlocks": [ { "id": "302ed89f43f0000000002d000004345d00", "type": "functionBlock", "attributes": { "name": "Room 2", "technicalName": "FTW04 dS", "active": true, "sensorInputs": [ { "id": "0", "attributes": { "technicalName": "Sensor#0" } }, { "id": "1", "attributes": { "technicalName": "Sensor#1" } }, { "id": "2", "attributes": { "technicalName": "Sensor#2", "type": "temperature" } }, { "id": "3", "attributes": { "technicalName": "Sensor#3", "type": "humidity" } } ], "submodule": "302ed89f43f0000000002d000004345d00", "deviceAdapter": "302ed89f43f0000000002d000004345d00" } } ] } } }The text was updated successfully, but these errors were encountered: