Issues

  • Parameter-Access through local F@H REST API

    Hi, as of now I can get all parameters for a device and/or a channel, when I read out the configuration. But nothing else. So I propose two additions to the local REST API: 1. Inform through the websocket if a parameter changes, so if a parameter is modified through the web or the app, that every program, which is listening to the websocket gets informed 2. Make the parameters changeable through the REST-API (same as the datapoints) Thansk a lot in advance

    Status: Proposed | Reported by Hidden Thu, 25 Jan 2024 10:57:23 GMT

  • How to "press" a trigger-device over the local REST-API

    I have a device with the following configuration: "ABB28EBC3651": { "interface": "TP", "displayName": "Sensor/switch actuator, 8/8gang, MDRC", "unresponsive": false, "unresponsiveCounter": 0, "defect": false, "channels": { ..., "ch0012": { "floor": "01", "room": "13", "displayName": "Garagentor", "functionID": "45", "inputs": { "idp0001": { "pairingID": 2, "value": "1" }, "idp0003": { "pairingID": 4, "value": "0" } }, "outputs": {}, "parameters": { "par0032": "10" } }, ... }, "parameters": { "par0026": "1" } How can I "fire" this trigger through the REST-API? The two input-datapoints don't help

    Status: Proposed | Reported by Hidden Thu, 16 Nov 2023 22:36:07 GMT

  • Data Solar Reactor is not being presented correct with SmartTouch 10 Panel

    SmartTouch 10 Panel is not showing the Solar Collector Information correct. PairingIDs 1214, 1216, 1217 and 1218 are not being shown. In the APP I can see the correct informations. Panel Version: 2.1.0 Build 1971

    Status: Proposed | Reported by Hidden Thu, 13 Jul 2023 20:47:01 GMT

  • CODetector and FIRE Detector as virtual devices are undocumented

    The above mentioned devices are havig undocumented pairing IDs. This shall be added to the documentation

    Status: Proposed | Reported by Hidden Tue, 31 Jan 2023 06:00:40 GMT

  • Virtual device type is needed for keep-alive signal of a virtual device

    The virtual device keep-alive signal is not working with a simplified json object e.g {"properties": {"ttl": "60"}} as seen in the example as well but the device type must be specified otherwise a negative response is received. In the case keep-alive signal it is unneccessary to send the device type and in many use cases maybe the device type is not known or not interessting for keeping the device alive The device type shall be optional as stated in the example.

    Status: Proposed | Reported by Hidden Tue, 31 Jan 2023 05:59:17 GMT

  • Websocket connection is cyclically closed with code 1006 with SysAP 3.x.x

    As developer of a Java plugin for free@home using the websocket connection to get immediate status updates. The websocket connection ws stable with the SysAP2.6.3. After the update websocket connetion is closed after 3-5 Minutes of opening of the connection with the error code 1006. Which cnfiguration shall be set that the connection is not closed with this error code.

    Status: Proposed | Reported by Hidden Mon, 23 Jan 2023 22:29:19 GMT

  • free@home flex devices FID list

    Hello, the new free@home flex components get new Function IDs thats not listed, so i need a Updated list to work with it Regards

    Status: Proposed | Reported by Hidden Mon, 25 Apr 2022 12:40:31 GMT

  • Scene trigger information missing for Virtual Device triggers

    Statement: When creating a virtual device using the local API, i'm unable to control the device trough scenes from the SYSAP. Situation: - The virtual device is created using the Local API (/fhapi/v1/api/rest/virtualdevice) with parameters: type=SwitchingActuator, TTL=180 - The device is able to recieve ON/OFF requests to ch0000/idp0000. Both using physical sensors as from the SYSAP webinterface. - The virtual device is coded to send replies by sending ch0000/odp0000 for ON/OFF actor status changes. - The device is working as expected in LightGroups. Problem: Scenes get triggered by a Scene request (AL_SCENE_CONTROL) to idp0003 on channel ch0000. However the content to the scene as documented in the API documentation, chapter ‘Scene support for virtual devices’ scenesTriggered is empty. Example recieved Json: 2021-11-25T15:35:10 {"00000000-0000-0000-0000-000000000000": {"datapoints": {"60005CD9523A/ch0000/idp0003": "9"},"devices": {},"devicesAdded": [],"devicesRemoved": [],"scenesTriggered": {}}} Attached is the transcript for tests. I can provide full implementation code (C#, works both in Windows/Visual Studio and Linux/Mono 6.12)

    Status: Proposed | Reported by Hidden Thu, 25 Nov 2021 14:52:40 GMT

  • Issue between virtual Actor and real Sensor / switch

    wie eben telefonisch besprochen hier der Fehlerbericht zur Weiterleitung an die Programmierer der API/Virtuellen Devices und dem potentiellen Bug in der Zusammenarbeit virtueller Aktor mit Wippen / Sensoren und der Free@Home UI. Zusammenfassung: Wippe und WebUI können anscheinend einen virtuellen Schaltaktor nicht auslösen - schreiben diese ggf auf das falsche Datenelement? Der virtuelle Aktor ist via API durch 1/0 -> ch0000/odp0000 korrekt bedienbar. Schreiben ggf UI und Wippe für virtuelle Aktoren nicht nach ch0000/odp0000, sodass sie diese nicht bedienen können? Ich bin per Email erreichbar . Danke. Die Details: Ausgangslage: Es wurde ein virtueller Schaltaktor via API erzeugt, im Raum platziert und mit einer rechten Wippe (Sensor) eines 2.1 wireless Jalousieaktors verbunden. Der virtuelle Aktor ist im Hintergrund mit OpenHAB3 verbunden, um dort ein Gerät anzuschalten. Dies tut aber nichts zur Sache des hier beschriebenen Problems. Was funktioniert: Der virtuelle Aktor ist problemlos via Swagger/API schaltbar (1 -> ch0000/odp0000) - dann zeigt die UI korrekt das "Licht an" am virtuellen Aktor, und die Wippe zeigt Statuslicht "An" (und OpenHAB schaltet die Lampe ein). Ebenso ist er ausschaltbar via API (0 -> ch0000/odp0000) - UI zeigt "Lampe Aus", Wippe Statuslicht "aus" (und OpenHAB schaltet die Lampe aus). So sieht das in API aus: "An" und so im Free@Home Monitor "An": API "Aus": Monitor Verlauf "Aus": Problem / was nicht geht: Der Benutzer soll den virtuellen Aktor natürlich nicht via API bedienen, sondern dies via WebUI und Wippe (siehe unten) machen, dies geht leider nicht. Drücken des Aktors in der WebUI "An": Monitor: Drücken Schalterwippe "An" (rechts): Monitor:

    Status: Proposed | Reported by Hidden Wed, 28 Apr 2021 15:32:05 GMT

  • LocalAPI results in "500 internal server error" after update of Sysap 2 to firmware 2.6.2

    LocalAPI results in "500 internal server error" after update of Sysap 2 from 2.6.1 to firmware 2.6.2 Tried disable / re-enable Local API. Tried different users. Tried /Swagger, curl and access through (previously on 2.6.1 working) NodeRed Flows, same error, all result in a 30sec - 60 sec delay then "500 Internal Server Error". Restarting Sysap , power off and on SysAp all did not help. Disabled nodeRed to ensure this is not a rate limiting / authentication issue same effect when trying just on /Swagger after a wait and/or a restart of the Sysap. Please advise as the Local API integration here is critical for the house.

    Status: Proposed | Reported by Hidden Wed, 28 Apr 2021 15:18:35 GMT

You're not signed in. Please sign-in to report an issue or post a comment.