Domoticz

Posted: **Monday 13 February 2017 22:57**

Hi ptitneo,

I'm using the public server and both MQTT and Domoticz are shows as Connected.
Not able to figure out how to start a logging on the messages yet. Found a tool called MQTTLens but not sure what topic to subscribe to.

Regards,
Rick

Posted: **Monday 13 February 2017 23:02**

Can you open the developer console on a desktop browser, and see if you get error messages?

Posted: **Monday 13 February 2017 23:12**

Just one warning:

Code: Select all

Use of the Application Cache is deprecated on insecure origins. Support will be removed in the future. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.

reacticz.t0m.fr/:1 Adding master entry to Application Cache with manifest http://reacticz.t0m.fr/ios.manifest
reacticz.t0m.fr/:1 Application Cache NoUpdate event
MqttClientSingleton.js:55 connected to mqtt broker

Posted: **Monday 13 February 2017 23:32**

Yeah that message is related to a hack for iOS. Not relevant here.

Can you confirm that the devices list shows up properly in the dedicated page ?
Can you share the result of http://<your domoticz ip>:8080/json.htm?type=devices&filter=all&used=true&order=Name ? (this is what this page calls to get the list).

Then when you are on the dashboard, open the developer tools and switch to the Network tab, then play with the buttons you have configured of the dashboard. You should see some json.htm request piling up. Are any of these showing up in red ?

Posted: **Monday 13 February 2017 23:57**

ptitneo wrote:Yeah that message is related to a hack for iOS. Not relevant here.

Can you confirm that the devices list shows up properly in the dedicated page ?
Can you share the result of http://<your domoticz ip>:8080/json.htm?type=devices&filter=all&used=true&order=Name ? (this is what this page calls to get the list).

Well, this is about 3000 lines of code, so I'm gonna skip that for now

But I get where you're going to. I believe you would like to match the IDX, right?

ptitneo wrote:Then when you are on the dashboard, open the developer tools and switch to the Network tab, then play with the buttons you have configured of the dashboard. You should see some json.htm request piling up. Are any of these showing up in red ?

Well, for the buttons that do work, I see new rows appearing in the network tab.
For the ones that don't seem to work, there's no feedback in the network list as well. But no reds included.

Posted: **Tuesday 14 February 2017 1:04**

Oh wow ok we'll pass on the 3 thousand lines then

Anyway the fact that some devices are working is interesting. So what type are those that do and those that don't exactly ? Would you be able to find their IDX and give me the device info (ie the result of /json.htm?type=devices&rid=IDX) for some that do not work ?

Posted: **Tuesday 14 February 2017 15:21**

Hi ptitneo,

Just created a quick video which demonstrates a list of issues:
https://www.screencast.com/t/DDnNblIuqDQ

Note that for the blinds (Rolluik rechts) the buttons Open and Close don't work, but Stop DOES work

#mindblown
The dimmer also does work, but the yellow indicator doesn't move as nice as in the GitHub animation.

Lichtintensiteit:

Code: Select all

{
   "ActTime" : 1487082039,
   "ServerTime" : "2017-02-14 15:20:39",
   "Sunrise" : "07:50",
   "Sunset" : "17:49",
   "result" : [
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "Set Level: 10 %",
         "Description" : "",
         "Favorite" : 1,
         "HardwareID" : 10,
         "HardwareName" : "Dummy",
         "HardwareType" : "Dummy (Does nothing, use for virtual switches only)",
         "HardwareTypeVal" : 15,
         "HaveDimmer" : true,
         "HaveGroupCmd" : true,
         "HaveTimeout" : false,
         "ID" : "00110000",
         "Image" : "Light",
         "IsSubDevice" : false,
         "LastUpdate" : "2017-02-06 21:35:46",
         "Level" : 10,
         "LevelActions" : "||||",
         "LevelInt" : 10,
         "LevelNames" : "Off|Low|Mid|High|Full",
         "LevelOffHidden" : false,
         "MaxDimLevel" : 100,
         "Name" : "Lichtintensiteit",
         "Notifications" : "false",
         "PlanID" : "9",
         "PlanIDs" : [ 9 ],
         "Protected" : false,
         "SelectorStyle" : 0,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "Status" : "Set Level: 10 %",
         "StrParam1" : "",
         "StrParam2" : "",
         "SubType" : "Selector Switch",
         "SwitchType" : "Selector",
         "SwitchTypeVal" : 18,
         "Timers" : "false",
         "Type" : "Light/Switch",
         "TypeImg" : "Light",
         "Unit" : 1,
         "Used" : 1,
         "UsedByCamera" : false,
         "XOffset" : "617",
         "YOffset" : "33",
         "idx" : "294"
      }
   ],
   "status" : "OK",
   "title" : "Devices"
}

Woonkamer (midden):

Code: Select all

{
   "ActTime" : 1487082067,
   "ServerTime" : "2017-02-14 15:21:07",
   "Sunrise" : "07:50",
   "Sunset" : "17:49",
   "result" : [
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "Set Level: 66 %",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 4,
         "HardwareName" : "RFXtrx433e",
         "HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
         "HardwareTypeVal" : 1,
         "HaveDimmer" : true,
         "HaveGroupCmd" : true,
         "HaveTimeout" : false,
         "ID" : "00D0000",
         "Image" : "Light",
         "IsSubDevice" : false,
         "LastUpdate" : "2017-02-14 15:13:04",
         "Level" : 66,
         "LevelInt" : 10,
         "MaxDimLevel" : 15,
         "Name" : "Woonkamer (midden)",
         "Notifications" : "false",
         "PlanID" : "4",
         "PlanIDs" : [ 4 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "Status" : "Set Level: 66 %",
         "StrParam1" : "",
         "StrParam2" : "",
         "SubType" : "AC",
         "SwitchType" : "Dimmer",
         "SwitchTypeVal" : 7,
         "Timers" : "false",
         "Type" : "Lighting 2",
         "TypeImg" : "dimmer",
         "Unit" : 1,
         "Used" : 1,
         "UsedByCamera" : false,
         "XOffset" : "397",
         "YOffset" : "316",
         "idx" : "284"
      }
   ],
   "status" : "OK",
   "title" : "Devices"
}

Kantoor:

Code: Select all

{
   "ActTime" : 1487082086,
   "ServerTime" : "2017-02-14 15:21:26",
   "Sunrise" : "07:50",
   "Sunset" : "17:49",
   "result" : [
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "Off",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 4,
         "HardwareName" : "RFXtrx433e",
         "HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
         "HardwareTypeVal" : 1,
         "HaveDimmer" : true,
         "HaveGroupCmd" : true,
         "HaveTimeout" : false,
         "ID" : "0A33716",
         "Image" : "Light",
         "IsSubDevice" : false,
         "LastUpdate" : "2017-02-13 20:08:10",
         "Level" : 0,
         "LevelInt" : 0,
         "MaxDimLevel" : 15,
         "Name" : "Kantoor",
         "Notifications" : "false",
         "PlanID" : "3",
         "PlanIDs" : [ 3 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "Status" : "Off",
         "StrParam1" : "",
         "StrParam2" : "",
         "SubType" : "AC",
         "SwitchType" : "On/Off",
         "SwitchTypeVal" : 0,
         "Timers" : "false",
         "Type" : "Lighting 2",
         "TypeImg" : "lightbulb",
         "Unit" : 10,
         "Used" : 1,
         "UsedByCamera" : false,
         "XOffset" : "668",
         "YOffset" : "449",
         "idx" : "92"
      }
   ],
   "status" : "OK",
   "title" : "Devices"
}

Rolluik links (Offline):

Code: Select all

{
   "ActTime" : 1487081867,
   "ServerTime" : "2017-02-14 15:17:47",
   "Sunrise" : "07:50",
   "Sunset" : "17:49",
   "result" : [
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "Stopped",
         "Description" : "",
         "Favorite" : 0,
         "HardwareID" : 4,
         "HardwareName" : "RFXtrx433e",
         "HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
         "HardwareTypeVal" : 1,
         "HaveDimmer" : false,
         "HaveGroupCmd" : false,
         "HaveTimeout" : false,
         "ID" : "050000",
         "Image" : "Light",
         "IsSubDevice" : false,
         "LastUpdate" : "2017-01-20 12:07:08",
         "Level" : 0,
         "LevelInt" : 0,
         "MaxDimLevel" : 0,
         "Name" : "Rolluik links",
         "Notifications" : "false",
         "PlanID" : "4",
         "PlanIDs" : [ 4 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "Status" : "Stopped",
         "StrParam1" : "",
         "StrParam2" : "",
         "SubType" : "RFY",
         "SwitchType" : "Blinds",
         "SwitchTypeVal" : 3,
         "Timers" : "false",
         "Type" : "RFY",
         "TypeImg" : "blinds",
         "Unit" : 1,
         "Used" : 1,
         "UsedByCamera" : false,
         "XOffset" : "377",
         "YOffset" : "473",
         "idx" : "456"
      }
   ],
   "status" : "OK",
   "title" : "Devices"
}

Rolluik rechts:

Code: Select all

{
   "ActTime" : 1487082019,
   "ServerTime" : "2017-02-14 15:20:19",
   "Sunrise" : "07:50",
   "Sunset" : "17:49",
   "result" : [
      {
         "AddjMulti" : 1.0,
         "AddjMulti2" : 1.0,
         "AddjValue" : 0.0,
         "AddjValue2" : 0.0,
         "BatteryLevel" : 255,
         "CustomImage" : 0,
         "Data" : "Stopped",
         "Description" : "",
         "Favorite" : 1,
         "HardwareID" : 4,
         "HardwareName" : "RFXtrx433e",
         "HardwareType" : "RFXCOM - RFXtrx433 USB 433.92MHz Transceiver",
         "HardwareTypeVal" : 1,
         "HaveDimmer" : false,
         "HaveGroupCmd" : false,
         "HaveTimeout" : false,
         "ID" : "010000",
         "Image" : "Light",
         "IsSubDevice" : false,
         "LastUpdate" : "2017-02-14 15:13:20",
         "Level" : 0,
         "LevelInt" : 0,
         "MaxDimLevel" : 0,
         "Name" : "Rolluik rechts",
         "Notifications" : "false",
         "PlanID" : "4",
         "PlanIDs" : [ 4 ],
         "Protected" : false,
         "ShowNotifications" : true,
         "SignalLevel" : "-",
         "Status" : "Stopped",
         "StrParam1" : "",
         "StrParam2" : "",
         "SubType" : "RFY",
         "SwitchType" : "Blinds",
         "SwitchTypeVal" : 3,
         "Timers" : "false",
         "Type" : "RFY",
         "TypeImg" : "blinds",
         "Unit" : 2,
         "Used" : 1,
         "UsedByCamera" : false,
         "XOffset" : "303",
         "YOffset" : "141",
         "idx" : "445"
      }
   ],
   "status" : "OK",
   "title" : "Devices"
}

Regards,
Rick

Posted: **Tuesday 14 February 2017 15:28**

Thanks Rick, this along with the screencast should help me figure out what the hell is going on here. It might take me a few days though

Posted: **Tuesday 14 February 2017 15:42**

Take your time ptitneo. I'm already very grateful you're taking the time to check this out

Do you already have any thoughts what might causing these anomalies?
The mosquito server is currently running on my Synology NAS where Domoticz is running on a RPi. Would it make any difference once I add a new mosquito setup on the same RPi as Domoticz?

Posted: **Tuesday 14 February 2017 16:00**

I have the same setup.

I'm really puzzled:
- For your RFY Blinds, the Stop command is sent over JSON whereas Open and Close are sent over MQTT. And only "Stop" works.
- Similarly, the thermostat widget emits commands in json but fetches the current setpoint with MQTT. The video shows that it does emit but either Domoticz doesn't obey and update with the value or it does and MQTT fails at communicating the new setpoint.
This seems to indicate an oddity with MQTT (client device not properly configured in Domoticz, messages going over the wrong (sub)channels, something like that). BUT

we also see in the video that selector switch works (both sending commands and receiving status update). And this one uses MQTT only! So it looks like it's only partly broken. Very strange.

One more thing, could you share the result of typing

Code: Select all

JSON.stringify(localStorage)

in your console?

Posted: **Tuesday 14 February 2017 16:17**

Well, the temperature does gets changed (takes a few seconds though)
And the selector switch only changes in the interface, not in real life.

So for me, this clearly indicates that there's a problem with MQTT.

In what console would you like me to enter the

Code: Select all

JSON.stringify(localStorage)

?
In the SSH console of my NAS?

Posted: **Tuesday 14 February 2017 16:21**

No, I meant the developer console, in your web browser.

If you're willing to try with a different Mosquitto broker, this would maybe help narrowing down the problem.

Posted: **Tuesday 14 February 2017 16:25**

Here you go:

Code: Select all

"{"layout2":"[{\"w\":4,\"h\":2,\"x\":0,\"y\":0,\"i\":\"d|51\",\"moved\":false,\"static\":false},{\"w\":4,\"h\":1,\"x\":0,\"y\":2,\"i\":\"d|99\",\"moved\":false,\"static\":false},{\"w\":2,\"h\":1,\"x\":4,\"y\":2,\"i\":\"d|100\",\"moved\":false,\"static\":false},{\"w\":2,\"h\":1,\"x\":4,\"y\":1,\"i\":\"d|169\",\"moved\":false,\"static\":false},{\"w\":2,\"h\":1,\"x\":4,\"y\":0,\"i\":\"d|168\",\"moved\":false,\"static\":false},{\"w\":6,\"h\":1,\"x\":0,\"y\":5,\"i\":\"d|92\",\"moved\":false,\"static\":false},{\"w\":3,\"h\":2,\"x\":0,\"y\":6,\"i\":\"d|456\",\"moved\":false,\"static\":false},{\"w\":3,\"h\":2,\"x\":3,\"y\":6,\"i\":\"d|445\",\"moved\":false,\"static\":false},{\"w\":6,\"h\":1,\"x\":0,\"y\":3,\"i\":\"d|294\",\"moved\":false,\"static\":false},{\"w\":6,\"h\":1,\"x\":0,\"y\":4,\"i\":\"d|284\",\"moved\":false,\"static\":false}]","serverConfig":"{\"domoticzAuthChecked\":false,\"domoticzLogin\":\"\",\"domoticzPassword\":\"\",\"domoticzUrl\":\"http://192.168.178.19:8080\",\"mqttAuthChecked\":false,\"mqttBrokerUrl\":\"ws://192.168.178.10:9001\",\"mqttLogin\":\"\",\"mqttPassword\":\"\"}","themeId":"\"Default\"","whitelist2":"[\"d|51\",\"d|99\",\"d|100\",\"d|169\",\"d|168\",\"d|92\",\"d|456\",\"d|445\",\"d|294\",\"d|284\"]"}"

Will try to create another Mosquitto broker on my Domoticz Pi tonight.

Posted: **Tuesday 14 February 2017 16:45**

Ah! Another oddity: you are on dashboard 2 (using '?2' in the url) but you don't have a dashboard 1. Probably not what's causing the trouble (but who knows).

Posted: **Tuesday 14 February 2017 17:07**

That can be right. Was experimenting with a few pages and exported the second to another computer.
But the 'normal' 1st page doesn't work as well

Posted: **Tuesday 14 February 2017 20:54**

Okay, I've figured out the issue.. (And I feel kinda stupid about it)
While installing Mosquitto on the RPi, I was checking my settings @ Domoticz. There I noticed it was previously configured with the RPi IP, not the Synology IP..

First tests indicate this solved my issue, but will try some more to make sure.

In order to prevent future issues because of an incorrect or missing Domoticz setting, I was thinking that an automated check on /json.htm?type=hardware might be a good improvement to the tool.

For now, I'm going to finish the local installation of Mosquitto on the RPi and will have a drink afterwards.

Thanks for helping me out ptitneo

Posted: **Wednesday 15 February 2017 0:58**

Ah interesting what this misconfiguration caused

Yeah maybe we could change the setting screen so that it uses the type=hardware API call to get the info on the MQTT device and warn if it isn't available. It could even retrieve the IP and login/password from there, so the only thing left to be manually configured in reacticz would be the websockets port number.

But... If that IP was misconfigured in the mqtt device like it was in your case, it still wouldn't work. But at least it would have been easier to find out.

Posted: **Wednesday 15 February 2017 11:35**

True.. or you keep the current fields try to match the config URL with the one configured in Domoticz

Anyway, just noticed there's a difference in design between my page and the GitHub screenshot.
Example:

: 2017-02-15_09-53-14.png (12.44 KiB) Viewed 5332 times

Is there any way to change to this new(?) design?

Posted: **Wednesday 15 February 2017 12:12**

Actually the screenshot is from the old design. I had to change for 2 reasons:
1) contrast levels were too low, causing poor readability. The update in the color scheme is an attempt to (loosely) stick to WCAG standard recommendations on that. Universal design matters a lot to me.
2) Title was above buttons in other switch types such as selector switches.

One thing we could consider is removing the margin between open/stop/close. But the selector switch has margins so it wouldn't be very consistent.
Other than that, unless you build from an old version of the code, I am afraid you won't get the old style.

PS feel free to update these misleading screenshots in GitHub

Posted: **Wednesday 15 February 2017 13:18**

Too bad. Actually liked the old design

Considering it's just another css file, any way of forcing the old design via url parameter or option?

Domoticz

Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle

Re: Reacticz dashboard: no install, no hassle