Currently I am using it as a slave under my other Domoticz.. but this is (obviously) not ideal.. and want to go back to my synology. Could this be a dependency error? If so.. any idea which dependency I might be missing? This is probably related to your network adapter not receiving multicast ...

Currently I am using it as a slave under my other Domoticz.. but this is (obviously) not ideal.. and want to go back to my synology. Could this be a dependency error? If so.. any idea which dependency I might be missing? This is probably related to your network adapter not receiving multicast ...

Hi Corbin, Running Domoticz beta 3.6944 from Jadahl on synology I am still unable to update devices with error Invalid Key. On raspberry pi running Domoticz it is working great! So great work :) Currently I am using it as a slave under my other Domoticz.. but this is (obviously) not ideal.. and want ...

You don't need to use the Xiaomi app to use these sensors by the way. My sensors are working fine, and I never even touched the app. The only reason to use the app would be to update the firmware. But you'll always run the risk of breaking things if you do. I know this is more a question about ...

@Kwintessens Can you post the exact key you have entered for the Gateway? (you can change it later if you are worried about security) Also If you want to troubleshoot, please setup a test vm running Windows or Linux, and compile my github repo at https://github.com/corbinmunce/domoticz I've tried ...

I am still getting these errors after adding the gateway and devices in Domoticz (running beta version: 3.6765 on synology):

XiaomiGateway: SendMessageToGateway failed on first attempt, will try again
2017-02-25 10:01:53.921 Error: XiaomiGateway: unable to write command - Invalid Key

Any help?

Hi, I am running into the same issue with invalid key. Hardware and devices are added fine and initial status seems to be set correctly. I do not get any updates or possibility to control the gateway from Domoticz. I am currently using Domoticz Beta version: 3.6708 (Synologogy Ds216j). Could it be ...

Please note that because you enabled below option the modus will be set to home automatically when you run gigasetelements-cli. Try to disable it by adding # in front of it and see if it works: # set modus {home,away,custom} (optional) modus=home Still not working, unfortunately.. for now I will ...

Still not working.. (So I am keeping the bash script outside of it to keep it working for me). My config file: [accounts] # username (email) in use with my.gigaset-elements.com username=xxxxxxxxxxxxxx # password in use with my.gigaset-elements.com password=xxxxxxxxxxxxxxxxxxxxx # access token to ...

For now it is not setting status automatically.. Everything else is (still) running fine after I modified the whole config. I'll look into the config a bit more careful tomorrow to see if I am missing some obvious things.

I understand what you're saying for that is a more elegant way.. From a Gigaset Elements point of view (as seen in the app) these are different.. The base state is more related to status of sensors and intrusion, whereas the other is simply the away state. If you're trying to combine the two I am ...

Now thinking how to best implement to update the current modus using the selector switch, the actual updating is not the problem but we have now 2 domoticz sensors for base (alert/selector) which I would like to merge into one if possible ... I understand what you're saying for that is a more ...

It works now, but with -ss I still get the following errors, indeed related to pushbullet. Doesn't matter to me since it works just fine.. I've tried to resolve the python-magic before but was unsuccessful (see below). Have yet to test the button in combination with the home/away modes.. What did ...

It works now, but with -ss I still get the following errors, indeed related to pushbullet. Doesn't matter to me since it works just fine.. I've tried to resolve the python-magic before but was unsuccessful (see below). Have yet to test the button in combination with the home/away modes.. What did ...

You can test the button selector switch by installing below branch and update the config file so button is linked to the newly created selector switch: git clone -b 14-button https://github.com/dynasticorpheus/gigasetelements-cli.git cd gigasetelements-cli pip install -r requirements.txt python ...

Is the bash/curl script I shared earlier working for you? (will be the next thing I am going to add to the cli so in the end we don't need it anymore) Yes, it's working fine.. I just edited the states to positions 10, 20 and 30 as 0 state is off to me. You can test the button selector switch by ...

Work in progress ... actually not to much code to change to make this work ... will test a bit more tonight http://i68.tinypic.com/2w4bi49.png Great!! I am running the script after button push (to avoid cronjob) as this is my single source of status change, but not ideal because it doesn't ...

Thanks for the feedback! As workaround I currently have a curl script running every minute which updates the base selector switch to the current state should however be implemented in the CLI itself of course :geek: Don't have too much time at the moment but I will put in on my to-do list. We ...

Nice work! Can you give some information about the ir hardware your using? I wanna try this on my ilife v7 robot. I want to build it also for my new vacuum cleaner (ilife a4) are you going to add more controls like: back to base, max cleaning etc? and are you going to migrate to mysensors 2.0 ...

Wherever I can help let me know. :) Care to share your script? I think firing it off from a button press instead of scheduled job would definitely work for me as a workaround. :D Sorry what script do you mean? The script I have running checks every minute the state of the system (Home/Away/Custom ...