Freebox Delta integration

[_Will_71]

Hi @gaelbillon, thanks for your feedback. You beat me to it—I wanted to ask you the question.

All the better if it’s working, we’ll see.
As for the sensors, having the door sensor report, for example, every 30s might not be fast enough.

Regarding the sensor I won’t be able to do anything more because it comes from the Free API.
You can control it in Node-Red.
You need to run the first flow I gave you where I showed you how to retrieve your shutters’ identifiers.
You’ll be able to read your sensors’ info as well.

For me the motion sensor is in the array at value 2. Then in the data array at value 2 you also find the battery value which returns an int — that is, an integer which here is between 0 and 100. Except I have the value null. I think you do too.

If I now look at the opening sensor I do have a value of 100 in value.

Otherwise I haven’t progressed much on writing the tests.
I’m redoing my kitchen entirely at the same time so not much time…

[gaelbillon]

Hi @_Will_71, so has the kitchen come along well?? Personally I was really tied up this week with tidying the basement!

Anyway, a few updates: since the restart on 27/10 everything was going well until yesterday evening when the shutters didn’t close, and they didn’t open this morning; after restarting the box this evening the shutters closed as expected.
FYI, before the restart, when testing on the FreeboxHome app, I noticed that the camera was indeed returning a stream!

We’ll have to put this box on a smart plug so we can restart it at regular intervals
Not very professional of Free, this API situation — even with their app it’s not working!!

Positive point: we can validate the shutters’ operation and I’ll run tests with the sensors as soon as possible.
Do you think it’s possible to command the alarm activation?

[_Will_71]

Hello @gaelbillon ,

@gaelbillon

so this kitchen has progressed well

I’ve already removed all the floor tiles and redone the electrical work. I’m currently skimming all the walls and ceiling.

However, when you don’t make calls to the API I never have any problems, I don’t know about your side. Is it intentional on Free’s part to limit the number of API calls???

@gaelbillon

We’re going to have to put this box on a smart plug to be able to restart it at regular intervals

On the box search page I added a button to restart the box. Otherwise you can do it with Node-RED as well. You just need to send a command. I can tell you how to do it if you want. After that, it remains to be seen whether the command is properly interpreted when the API has crashed.

@gaelbillon

Do you think it’s possible to command the activation of the alarm?

For this part, I’d rather for now really finish the unit test section that I haven’t had much time to advance. There’s a bit of work for this part and I’d prefer not to add too much before adding lots of features.
Also, there isn’t a suitable device to put on the dashboard. We’ll see if we can adapt the new alarm widget.

[gaelbillon]

Hi @_Will_71,

On the other hand, when you don’t make API calls I never had a problem, I don’t know about your side. Is it intentional on Free’s part to limit the number of API calls???’

The problem is that I don’t see what is making API calls, we don’t use the freeboxHome app every 5 minutes either??

On the box’s search page I put a button for restarting the box. Otherwise you can do it with Node-RED too. You just need to send a command. I could tell you how to do it if you want. Afterwards it’s a question of whether the command is correctly interpreted when the API has crashed.

I can confirm that the button works when the API is blocked, I just tested.
Could you foresee making this button usable in scenes to allow a scheduled restart? Not as a priority, and I’d like the Node-RED command for troubleshooting.

For this part I prefer for now to really finish the unit tests part which I haven’t had much time to progress. For this part there’s a bit of work and I’d rather not add too much before adding lots of features. Also there’s no device suitable for putting on the dashboard. We’ll see if we can adapt the new alarm widget.

I completely agree, it’s not a priority either, but indeed with alarm mode it would be wise to use this function to control the Freebox alarm in our scenes.

Thanks again.

[_Will_71]

@gaelbillon

The problem is that I only see what is making calls to the API

Actually I was talking about API calls with Node-RED or Gladys. If I remove those calls on my side I no longer have issues with their FreeboxHome.

@gaelbillon

Couldn’t you provide a button usable in scenes to allow a scheduled reboot?

Something to consider, yes. I put it like that quickly; I also need to improve the fact that nothing happens visually while the box is restarting. It bothers me to know that an action has taken place without any visual feedback.

Here is the Node-RED flow:

[
    {
        "id": "10629aa673184778",
        "type": "inject",
        "z": "d7c3929073ea7b03",
        "name": "Restart@4H",
        "props": [
            {
                "p": "payload"
            },
            {
                "p": "topic",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "00 04 * * *",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 160,
        "y": 1160,
        "wires": [
            [
                "98ed89926510ab68"
            ]
        ]
    },
    {
        "id": "98ed89926510ab68",
        "type": "function",
        "z": "d7c3929073ea7b03",
        "name": "REBOOT FREEBOX",
        "func": "msg.url = \"/system/reboot\"\nmsg.method = \"POST\"\nmsg.payload = {\n    \"value\": null\n}\nreturn msg;",
        "outputs": 1,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 380,
        "y": 1160,
        "wires": [
            [
                "2f6128ed385d5349"
            ]
        ]
    },
    {
        "id": "2f6128ed385d5349",
        "type": "api",
        "z": "d7c3929073ea7b03",
        "name": "",
        "url": "",
        "server": "35b9faf136b9302a",
        "x": 610,
        "y": 1160,
        "wires": [
            [
                "61e45827b9e0d9a5"
            ]
        ]
    },
    {
        "id": "61e45827b9e0d9a5",
        "type": "debug",
        "z": "d7c3929073ea7b03",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "",
        "statusType": "auto",
        "x": 770,
        "y": 1160,
        "wires": []
    },
    {
        "id": "35b9faf136b9302a",
        "type": "freebox-server",
        "host": "https://mafreebox.freebox.fr",
        "port": "443"
    }
]

The first Inject node here I configured to send the command every day at 4:00 AM. But you can trigger it manually or change the schedule. Adapt it as you like.

[gaelbillon]

Thanks for the flow, I’ll set it up if needed.
I restarted again a little while ago and 30 minutes later it was blocked again?? I just removed my motion sensor which is located in the main room, so I wonder if it’s the one making lots of calls?

[_Will_71]

I get the same thing with the integration and Node-RED.

Anyway, making a request to poll a sensor of this type bothers me. We should be able to read directly the request sent by the sensor when it changes state. Imagine you set a 1-minute polling interval on your contact sensor, for example. You have time to open and close the door before you’ve even made a request.

So if you’re lucky, when a thief enters your home, if you poll at that exact moment you’ll see the state change and detect an intrusion. Imagine the request was just made and a few seconds later a thief enters. He has slightly less than a minute to close the door. So no intrusion detection. Unless he leaves the door open!

In short, I don’t like this way of doing things and I wonder if it’s worth including these sensors.

For this integration, in my opinion it should include shutter control, camera stream reading, and alarm control. And besides, I wouldn’t use the alarm because it requires only Free sensors and I don’t want that.

[gaelbillon]

Once again, I agree with you, and like you the shutters are my priority.
As for

[Jluc]

Hi @_Will_71,
Can you control your SOMFY RTS shutters however you want?
Also, on the Delta, Alexa is available, but is it possible to use it in Gladys?

[_Will_71]

Hi @Jluc,

My shutters are on IO so I won’t be able to confirm whether that works on RTS.
Besides, in the Free Home app you can choose between RTS or IO so it should work.

However, you need to add the security pack to your box. It’s a paid module. What’s unfortunate is that the pack can no longer be used with later boxes.

As for Alexa, I don’t use it so I can’t tell you.

[Jluc]

Hi @_Will_71,

Thank you for your reply. I do have the security pack but since I recently changed the Delta’s server, I haven’t had the chance to get everything back up and running. Before I could control the Somfy shutters with the Free Home app. It seems I had no choice and had to set them to operate in RTS mode. I’ll look into the problem.

[Jluc]

Hello,
The number of votes hasn’t changed in a long time. A solution was proposed but I don’t use Node-RED.
I am receiving the images from the cameras in the security pack.
Would it be possible to manage SOMFY devices directly from Gladys?

[_Will_71]

You then need a Somfy TaHoma box and to use Matter.

[mutmut]

Small clarification for Somfy: you need a Tahoma switch or tahoma V2 or Connexoon (for cloud and local API) and Matterbridge for the Matter gateway with the matterbridge-somfy-tahoma plugin.

[pierre-gilles]

Hi everyone,

For those who are here to use their Somfy roller shutters in Gladys, it’s now quite easy thanks to the Matter integration — I’m putting the tutorial here:

Intégrer ses équipements Somfy à Gladys via Matterbridge | Gladys Assistant