Domoticz

they remain afaik

All Remain indeed. It only does ask for the login and password to Amazon again.. No other config required.
It even stay on the same Skill page

All working again after enable / disable, thanks

Had an initial fright as when I first went into Groups everything had gone pulled down though to refresh and everything came back

Keep up all the hard work

phew!

I'm unable to find my devices.

I am able to connect remotely via https. Checking my domiticz log, I don't see any incoming connections when I do a device discovery.

Any ideas?

can you give me a few characters of your email, and i'll see what's happening on the Controlicz side (e.g [email protected])

Thanks

[email protected]

RedRaven wrote: Sunday 03 December 2017 19:13 I have a question or perhaps a feature request.

My ISP does not provide me with a publicly reachable IP so I use my.domoticz.com for managing my Domoticz. Though currently I am using HA Bridge, I would definitely want to switch to Controlicz but since my Domoticz instance is not directly reachable how do I do it?

Is there a way you guys can recommend or something that can be done?

Bumping this @MadGeni

Hi - this has come up a couple of times. The short answer is not much can be done.

The Hue/Smartthings models is typical of how to implement this, where there is a cloud based service which handles the security model, and the client (Hue bridge/ smartthings hub) are the security client - but they are exposed to the internet, all the time, the same as the Controlicz model.
I've no idea how my.domoticz.com 'works' - but interactions are increasingly programmatic (via the API) - so Google Home/Alexa provide their API, which then in turn needs to be mapped to the Domoticz API (this is all after authenticating the user via Oauth2). This doesn't feel how my.domoticz.com works.
Controlicz also follows a standard model for integration, but i'm fully aware it provides another attack vector for devices (you give me your credentials, and you expose your domoticz host) - but I do all i can to ensure it's as secure as it can be. I regularly run OWASP tests/penetration tests etc.

Is it your ISP doesn't give you an external IP of any kind? or a static one? not heard of an ISP not telling you your dynamic IP address before.
I don't have a static IP, so i use noip.com to give me an external DNS name.

Phew - long post, sorry

NemesisXB wrote: Tuesday 05 December 2017 6:53 I'm unable to find my devices.

I am able to connect remotely via https. Checking my domiticz log, I don't see any incoming connections when I do a device discovery.

Any ideas?

Hi - are you still having this issue? I can't see any errors

sach wrote: Thursday 30 November 2017 21:23 It's almost working perfectly for me now. Can see both temps and setpoint of my sensor and thermostat via the app. Can query the current temp and setpoint perfectly via voice. Only small thing is when I ask to change setpoint or change via the app it comes up with an error but it works regardless....so not a major.

finally got round to fixing this

Cool! I will give it a go.
I just noticed something else and thought I would check if it's just for me. When checking lights via the app, there is a message saying device is unresponsive. I'm guessing it's trying to get the status of the device as I'm still able to switch on/off/dim but the status in the first instance is always off.

Hi Madgeni

I can confirm that every thermostats and temperature sensors work great now. I can set the thermostat and she responsed with correct setpoint. The temperature sensors also work great. The problem still occurs for the temperature sensor with the Type: Temp+ Humidity + Bar ; Sub type: Weather Station. When asking for the temperature. She will response with the temperature of the last requested temperature sensor. But I can live with that.

The other issue is the Scene with lots of lights/swithces. When ask to perform such scene, Alexa wil trigger the scene (all lights will start turning off/on one by one) but then Alexa will reponse with "The scene is not responding". I guess Alexa is waiting for the scene to complete before comfirming (by Saying Ok) but the scene action takes too long and Alexa thought the device (scene) is not responding.

Madgeni wrote: Tuesday 05 December 2017 20:03 The Hue/Smartthings models is typical of how to implement this, where there is a cloud based service which handles the security model, and the client (Hue bridge/ smartthings hub) are the security client - but they are exposed to the internet, all the time, the same as the Controlicz model.
I've no idea how my.domoticz.com 'works' - but interactions are increasingly programmatic (via the API) - so Google Home/Alexa provide their API, which then in turn needs to be mapped to the Domoticz API (this is all after authenticating the user via Oauth2). This doesn't feel how my.domoticz.com works.

My.Domoticz.Com does have an option/ability to connect to third party services as well; however there doesn't seem to any services enabled for it yet. Having said that, my.domoticz.com is increasingly getting unreliable as well

Madgeni wrote: Tuesday 05 December 2017 20:03 Is it your ISP doesn't give you an external IP of any kind? or a static one? not heard of an ISP not telling you your dynamic IP address before.
I don't have a static IP, so i use noip.com to give me an external DNS name.
Phew - long post, sorry

Actually, I loved reading your thoughts!

My ISP actually puts me on a internal IP (weird, but that's what they are doing; so I get a NAT'ed connection); so I have no way of exposing my services to the outside world. I am exploring a Reverse SSH model to expose services through another server; perhaps that works for Alexa services as well. Will let you know if I pull it off

Madgeni wrote: Tuesday 05 December 2017 21:03

NemesisXB wrote: Tuesday 05 December 2017 6:53 I'm unable to find my devices.

I am able to connect remotely via https. Checking my domiticz log, I don't see any incoming connections when I do a device discovery.

Any ideas?

Hi - are you still having this issue? I can't see any errors

Yes, still having the issue. I'm in an Amazon echo unsupported zone. Maybe something wrong with my setup (app version or something). Will play around and see if I can get something sorted out.

Thanks for having a look at it.

Chakkie wrote: Tuesday 05 December 2017 23:55 Hi Madgeni

I can confirm that every thermostats and temperature sensors work great now. I can set the thermostat and she responsed with correct setpoint. The temperature sensors also work great. The problem still occurs for the temperature sensor with the Type: Temp+ Humidity + Bar ; Sub type: Weather Station. When asking for the temperature. She will response with the temperature of the last requested temperature sensor. But I can live with that.

The other issue is the Scene with lots of lights/swithces. When ask to perform such scene, Alexa wil trigger the scene (all lights will start turning off/on one by one) but then Alexa will reponse with "The scene is not responding". I guess Alexa is waiting for the scene to complete before comfirming (by Saying Ok) but the scene action takes too long and Alexa thought the device (scene) is not responding.

Hi - will look at the Scene issue - it shouldn't be waiting for the state of each light/switch in the scene, i'm only waiting on a response from the scene API call - but that in turn might be waiting for lights/switch state etc. I can Promise it out.

NemesisXB wrote: Wednesday 06 December 2017 7:34

Madgeni wrote: Tuesday 05 December 2017 21:03

NemesisXB wrote: Tuesday 05 December 2017 6:53 I'm unable to find my devices.

I am able to connect remotely via https. Checking my domiticz log, I don't see any incoming connections when I do a device discovery.

Any ideas?

Hi - are you still having this issue? I can't see any errors

Yes, still having the issue. I'm in an Amazon echo unsupported zone. Maybe something wrong with my setup (app version or something). Will play around and see if I can get something sorted out.

Thanks for having a look at it.

This is odd, I can see http 200 responses, so Alexa is definitely asking for, and receiving the data

RedRaven wrote: Wednesday 06 December 2017 4:22 My ISP actually puts me on a internal IP (weird, but that's what they are doing; so I get a NAT'ed connection); so I have no way of exposing my services to the outside world. I am exploring a Reverse SSH model to expose services through another server; perhaps that works for Alexa services as well. Will let you know if I pull it off

that hop would probably work - as long as that call between the external facing server and your internal network was able to route traffic. Latency might be a bit of a problem

Hey - do a lot of you use Kodi?

Yep