'Dromotica' app for controlling Domoticz from Android

[sebas]

Update coming up that should definitly fix the temperature crash. It was caused by device types I haven't added yet. Got something in place for that now.

Also I took a look at the dimmers not updating and that should now also be fixed. As I don't have a dimmer and Domoticz somehow doens't let me add a fake dimmer to test with I haven't been able to test the workings. So please let me know how it works

[Peter112]

if you create a lightwaveRF dimmer manually this is displayed in domoticz with a slider. This is what i used for testing my plc interface.

[Gizmo]

Dimmers still dont work correctly, here is the output for a dimmer from json.htm?type=devices&filter=light&used=true&order=Name
I hope that helps...

Code: Select all

{ "BatteryLevel" : 255, "CustomImage" : 0, "Data" : "Set Level: 53 %, Level: 53 %", "Favorite" : 1, "HardwareID" : 1, "HardwareName" : "RFX", "HaveDimmer" : true, "HaveGroupCmd" : true, "ID" : "0B4E6EE", "Image" : "Light", "IsSubDevice" : false, "LastUpdate" : "2014-01-05 08:01:35", "Level" : 53, "LevelInt" : 8, "MaxDimLevel" : 16, "Name" : "Hall", "Notifications" : "false", "SignalLevel" : 7, "Status" : "Set Level: 53 %", "SubType" : "AC", "SwitchType" : "Dimmer", "SwitchTypeVal" : 7, "Timers" : "false", "Type" : "Lighting 2", "TypeImg" : "dimmer", "Unit" : 11, "Used" : 1, "UsedByCamera" : false, "idx" : "1016" }

[Sappien]

Temperature tab is working fine now.

[supergroover]

The temperature meter in the living room and the raspberry is working now with the latest update.
Only the temperature outside from weather underground isn't yet working.


Unfortunately the dimmers aren't working correctly.
Both dimmers are on at the moment.

[sebas]

if you create a lightwaveRF dimmer manually this is displayed in domoticz with a slider. This is what i used for testing my plc interface.

Thanks. That one does work. I've tried several types and they all had the slider stuck at 0.

Dimmers still dont work correctly, here is the output for a dimmer from json.htm?type=devices&filter=light&used=true&order=Name
I hope that helps...

Code: Select all

{ "BatteryLevel" : 255, "CustomImage" : 0, "Data" : "Set Level: 53 %, Level: 53 %", "Favorite" : 1, "HardwareID" : 1, "HardwareName" : "RFX", "HaveDimmer" : true, "HaveGroupCmd" : true, "ID" : "0B4E6EE", "Image" : "Light", "IsSubDevice" : false, "LastUpdate" : "2014-01-05 08:01:35", "Level" : 53, "LevelInt" : 8, "MaxDimLevel" : 16, "Name" : "Hall", "Notifications" : "false", "SignalLevel" : 7, "Status" : "Set Level: 53 %", "SubType" : "AC", "SwitchType" : "Dimmer", "SwitchTypeVal" : 7, "Timers" : "false", "Type" : "Lighting 2", "TypeImg" : "dimmer", "Unit" : 11, "Used" : 1, "UsedByCamera" : false, "idx" : "1016" }

Thanks. Found out what was causing it and I have a fix ready for it for the next update.

The temperature meter in the living room and the raspberry is working now with the latest update.
Only the temperature outside from weather underground isn't yet working.

...

Unfortunately the dimmers aren't working correctly.
...
Both dimmers are on at the moment.

Found out what was wrong with the dimmers.
I've got several data submissions for devices. Those will be added soon. Thank you all for that. The Weather Underground temp. will be supported shortly.

[fifise]

[Quote=sebas]
I have planned to support the client certificate option to secure the access to Domoticz. That's more secure than the username & password option and should be doable based on the research I've done so far.[/quote]


Thanks a lot for implementing the client certificate it's as secure as a VPN and way more secure than a login/password on Internet ( login/password are very weak again brut force)

[hamba]

Hi,

I can't seem to get the app to connect when I'm away, it keeps saying "Could not connect to Domoticz server"
I'm using a cert from startssl, I can also get to it via the browser, its just the android app that doesn't want to connect.

Regards
Hamba

[sebas]

Hi,

I can't seem to get the app to connect when I'm away, it keeps saying "Could not connect to Domoticz server"
I'm using a cert from startssl, I can also get to it via the browser, its just the android app that doesn't want to connect.

Regards
Hamba

The app connects over HTTP and if necessary with basic-auth or the login screen. Https and certificates are not supported.
You'll have to enable communication over http to be able to connect.

[hamba]

Ah, thanks for the explanation, any idea when https will be supported?

[Gizmo]

I couple of suggestions..

Widget for Temp sensors - Have it auto refresh maybe once every 30-60 minutes and a refresh button to instantly refresh.
An option to only show favorites (items on dashboard)

The widget for switches is still broken, do you have a fix ready for it?

[sebas]

Update coming up. It's published to the store, will be available in the coming hours.

Update content:
Version 1.1
* Added support for HTTPS
* Added support for gzip encoding. This will save on data usage. Needs Domoticz version 1.1376+
* Added support for P1 Smart Meters for gas usage
* Added support for P1 Smart Meters for energy usage
* Added support for Thermostat temperature readings
* Added support for Lux sensor readings
* Added support for Humidity only sensor readings
* Added support for Weather Underground wind meter readings
* Added support for LaCrosse TX3 humidity sensor readings
* Dimmers work correctly.

A note on the GZIP compression.
This is added to Domoticz in version 1.1376. The app will still function with a lower version of Domoticz but will consume more data as the data is not compressed before it is send to the app.
If you have a nginx proxy setup you can add the gzip compression there as well so it will work with lower versions of Domoticz. To do this first follow the instructions on this wiki page. You can skip the parts about SSL certificates if you don't want to setup HTTPS access to Domoticz. Then configure it so that it will forward traffic to port 8080 or to whatever port you have Domoticz running.
Open your nginx.conf in /etc/nginx and make sure that gzip compression is turned on. This is how my nginx.conf looks like for the Gzip config:

Code: Select all

##
	# Gzip Settings
	##

	gzip on;
	gzip_disable "msie6";

	# gzip_vary on;
	# gzip_proxied any;
	# gzip_comp_level 6;
	# gzip_buffers 16 8k;
	# gzip_http_version 1.1;
	# gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;

This is how my domoticz configuration file in nginx looks like. It's under /etc/nginx/sites-available and I have setup access via HTTPS and HTTP. Hence the two server{} blocks.

Code: Select all

access_log off;
add_header Cache-Control public;
server_tokens off;
server  {
   include    /etc/nginx/proxy_params;
   listen 443 ssl;
   keepalive_timeout 70;
   server_name localhost;
   ssl on;
   ssl_certificate             /etc/ssl/ca/server.crt;
   ssl_certificate_key         /etc/ssl/ca/server.key;
   add_header X-Frame-Options SAMEORIGIN;
   location / {
     proxy_pass http://localhost:8080/;
     access_log /var/log/nginx/domoticz.access.log;
     error_log /var/log/nginx/domoticz.error.log;
   }
}

server  {
   include    /etc/nginx/proxy_params;
   listen 81;
   keepalive_timeout 70;
   server_name localhost;
   add_header X-Frame-Options SAMEORIGIN;
   location / {
     proxy_pass http://localhost:8080/;
     access_log /var/log/nginx/domoticz.access.log;
     error_log /var/log/nginx/domoticz.error.log;
   }
}

A note on the HTTPS connection.
Because I needed to allow for HTTPS access using user generated SSL certificates I needed to setup Dromotica so that it will accept any SSL certificate provided. Normally access is blocked when the certificate that is provided does not come from a trusted source. You'll need to pay a SSL certificate agency to get such a certificate. User generated certificates are not signed by a trusted CA. Modern browsers will warn you about untrusted certificates and will allow you to continue. I can't do that in Dromotica so I needed to accept any certificate that's returned by the server. This means that you are still vulnerable to man in the middle attacks when you are on a network you do not trust. The communication between Dromotica and Domoticz will still be encrypted.

I have some requests to add more devices still on the list of to-do's. They will follow shortly so if yours isn't on it yet, it will come . Thanks to all of you who submitted devices to be added. If devices are still missing please submit them using the button in the app.

[Gizmo]

I updated the Domotiz installation and the app but now i only get "The server did not return a valid response" using insecure and could not connect with secure, im using remote connection and have forwarded the ports 8080 and 443 to the nas im running domoticz on, i guess there is some more settings needed for using secure but why does not insecure work?

[sebas]

I updated the Domotiz installation and the app but now i only get "The server did not return a valid response" using insecure and could not connect with secure, im using remote connection and have forwarded the ports 8080 and 443 to the nas im running domoticz on, i guess there is some more settings needed for using secure but why does not insecure work?

A invalid response means that the server did not return the json as expected. So the app did connect to the server.
I've had that response sometimes and all of those times I entered the incorrect username or password.

For secure you don't need to set anything except the correct port (default 443) and forward that port to the correct port on your Pi in your router. It does need a SSL certificate that uses the correct domain that you're connecting to. It doesn't need to be signed by a trusted CA.

[wizzard72]

I updated the Domotiz installation and the app but now i only get "The server did not return a valid response" using insecure and could not connect with secure, im using remote connection and have forwarded the ports 8080 and 443 to the nas im running domoticz on, i guess there is some more settings needed for using secure but why does not insecure work?

I have the same. It happend after updating to Domoticz v1.1376 and v1.1380.

[sebas]

I updated the Domotiz installation and the app but now i only get "The server did not return a valid response" using insecure and could not connect with secure, im using remote connection and have forwarded the ports 8080 and 443 to the nas im running domoticz on, i guess there is some more settings needed for using secure but why does not insecure work?

I have the same. It happend after updating to Domoticz v1.1376 and v1.1380.

Let me check what happened.

[Gizmo]

I have checked the login details over and over and tested them in webpage with firefox and the loginb details is correct, i have no idea why i cant connect with insecure, with secure it just says "Could not connect to domoticz server" and as i said, i have forwarded the port 443 but i have no idea where or how i should add SSL certificate you mentioned..

Current version.
Domoticz V1.1381

[sebas]

I thought I had it untill I used the previous version of Dromotica that was working fine before. As it's the previous 1.05 version it should work but it doesn't. It seems that something might have changed in Domoticz. I'll need to figure out what first before I can fix this. It only happens when you need an username and password to login. Without authentication everything works fine.

For HTTPS access you'll need to setup a SSL certificate otherwise your server isn't secure. You can find instructions on how to do that on the Wiki.

[andriej]

I've just found thread about this program on forums - cool!
Anyway, since last update on my Nexus 5, I see "Error reading switches/scenes/whatever" with message "The server did not return a valid response."
I didn't do anything with the server, just updated Ddomoticz to latest beta and Dromotica.
Nexus 5 (Dalvik) with 4.4.2

[sebas]

It has to do with the gzip compression that was added to Domoticz.
The http header that indicates that gzip is enabled isn't received by Dromoticz or detected correctly so it handles it as plain text.
Somehow it only fails when authentication is enabled.