Domoticz

Madgeni wrote: ↑Wednesday 13 February 2019 16:33 Hi all, Controlicz is undergoing maintenance - apologies for the outage, should be back in an hour

*Edit* - maintenance complete

Next time send out a e-mail to all active users as BCC ?

Hi guys,
I've managed to spend some time to get a ngrok alternative based on running ngrok as a service and then running a python script via cron for updates.
I couldn't get the great solution from mraichura working reliably for some reason.

Have a look at my github the readme should cover most bases.

all the best

Kevin

Well done Kevin

l0gic wrote: ↑Thursday 14 February 2019 16:17 Hi guys,
I've managed to spend some time to get a ngrok alternative based on running ngrok as a service and then running a python script via cron for updates.
I couldn't get the great solution from mraichura working reliably for some reason.

Have a look at my github the readme should cover most bases.

all the best

Kevin

That's really great Kevin. I'm unsure why the script didn't work for you. It's been a month that I've my script running on a measly RPi B(512mb RAM/ single core 700MHz) along with Domoticz, Node-Red & Mosquitto. As suggested by you, I've moved to systemd for startup and it's been working flawlessly.

Also, not to undermine your script or anything, this nodejs script listens for the events from ngrok and will instantly update Controlicz avoiding the few minutes blind-spot (due to 5 min cron interval), if an when the URL changes.

However, I'm glad to see people coming up with innovative ideas and sharing their codes.

For those who do not like all this setup issued, there is this free service called LocalTunne(https://localtunnel.github.io/www/) that provides free static URLs that do not change over time (unless someone else uses it before you do).

Hi mraichura,

thanks dude!
yeah, I never got to the bottom of why your code was not stable in my environment. I wrapped notifications around it including a heartbeat report but nothing worked.
I installed ngrok both independently as a service and also via the nodejs environment in case it made a difference.
Whenever the script failed it also took out ngrok even if it was a service - bizarre.
I'm running the latest Debian on a qotom intel box.

Fully on board with your comment about a 5 minute window with the cron process, have been mentally debating about mitigating/reducing that risk but as ngrok has been solid with no change for over a week and counting I'm placing that as a small inconvenience. I think I can plug into the ngrok system using python to catch changes as they happen but that is for another day.

First code I've ever put onto github, took me longer to write the readme.md properly than it took for the script (exaggeration but...)

All inspired by you mraichura - thanks.

Kevin

Separate thoughts with the ngrok set up...

since ngrok has been running I'm starting to consider the security / privacy side of this set up.
Previously I locked port 443 down to the two (probably only one needed - Nick?) controlicz IPs on my firewall.

With the free ngrok this is not possible (whitelist IP is available as a pay service) so anyone guessing the ngrok url can hit the domoticz front end.
Domoticz will prompt for user/password but on failing it will expose the fact that it is a Domoticz instance.
I've looked but I'm unable to see if ngrok is mitigating brute force scans.

I'm monitoring this at the moment and may consider switching back to DDNS/Open port with a lockdown to the Controlicz IPs.

Another thing to consider, "if it's free, you are the service" what is happening with the connections passing through the ngrok services?
If your data is being monitored, are you worried?

Views?

Kevin

what is this nonsense, i bought a subscription for a year around november and since january it says i do not have any subscription, i should have at least till november i would think...

Hi - i'm guessing you're the person who emailed me just now?
I have responded to your mail, take a look - thanks

For clarity - snellejellep didn't have an annual subscription, but a monthly one, which had lapsed.

Indeed, bought a new one now

hi ,
i have no action started from alexa via controlicz to my domoticz (no actions in the log of domoticz)
- i have a controlicz available , connected , tested with my domoticz and all the devices are displayed when i hit devices (inside controlicz)
- i have an alexa available, connected to controlicz' skills, all the device in a plan are discovered and reported inside alexa devices lists.
- i have created a routine using the device and when i hit on that routine alexa display : execution
- under domoticz all the devices are in a plan, with contrloicz:name of the device in description part, tested as working when i press the button

but : no action is reported under domoticz log and the devices in alexa is not responding

my device is a virtual device (Fibaro FSG 212) make just on / off and are shown on controlicz as a light/switch

any help of what is wrong is welcome
thanks

jluc2808 wrote: ↑Sunday 24 February 2019 12:31 hi ,
i have no action started from alexa via controlicz to my domoticz (no actions in the log of domoticz)
- i have a controlicz available , connected , tested with my domoticz and all the devices are displayed when i hit devices (inside controlicz)
- i have an alexa available, connected to controlicz' skills, all the device in a plan are discovered and reported inside alexa devices lists.
- i have created a routine using the device and when i hit on that routine alexa display : execution
- under domoticz all the devices are in a plan, with contrloicz:name of the device in description part, tested as working when i press the button

but : no action is reported under domoticz log and the devices in alexa is not responding

my device is a virtual device (Fibaro FSG 212) make just on / off and are shown on controlicz as a light/switch

any help of what is wrong is welcome
thanks

Hi there - if you mail me from your Controlicz profile, i'll take a look for you

General Controlicz Alexa update:
Sensor driven routines are now available to US customers - see the Controlicz FAQs for specific details, but the short version is you can now perform a large range of actions when a sensor trips.
As soon as the Motion/Contact sensor API is released to the EU, it will become instantly available to all users. Will update when that happens.

This is great !

Just a couple of questions. In the FAQ is states:
Then in your sensor – under notifications put: A|idx|$value|Sensor – eg. A|123|$value|Sensor , and enable the http toggle (disable the rest)

Does this string go in the "Custom Message" field of the sensors notification?
Is the idx value the one listed on the devices page on Controlicz (I guess the idx in domoticz and controlicz are the same)?
Is $value a variable?
Is Sensor the name of the sensor in Controlicz or just a placeholder

Thanks!

So I gave the new feature a try and when going into Alexa routines and select "when this happens"-> devices it comes back with the "We were unable to find any supported Devices"

In the sensor Notification, I put A|181|$value|Sensor, where 181 is the idx of the sensor.
Disabled and re-enabled the Controlicz skill in Alexa. (Alexa see's all of the sensors I added. i.e. they are all in a room plan)

Do I have to wait for some kind of provisioning to happen?

Thanks

Are you an amazon.com user? If so, I had to drag down on that devices page for my sensors to show up.

Not sure I understand your comments.
What do you mean by "an Amazon.com user" and "drag down on that devices page" ?

I have an Amazon.com account. I login to Alexa using that account (Alexa.amazon.com) on both windows and android devices.

Ok great - in the routines, and "When this happens", press Device, then in there, I had to swipe down to get my list of devices

Ok, so essentially a refresh? (when in the Device area I pull down from the top of the screen/tablet and get the circle arrow (i.e. refresh) but nothing changes.)

Still get "We were unable to find any supported Devices"

Ok, will take a look today