Impossible Parameters update via REST console

[Radu Crisan 0]

Hello.

I made the mistake of buying a Qubino Smart Meter and struggled with it and it's impossible cohabitation with Fibaro HomeCenter2.

Of course, as an innocent newbie, I wrote many times to both Qubino and Fibaro Tech Support and got general-available responses as: "should work", "no need for templates", etc.

Well, the thing with Qubino Smart Meter is a tricky one. For some users (and I saw on this forum a user from Romania with the correct display of values) seems to be working fine. Not for me. It always displayed the wrong decimal places for Intensity and Total Power, hence the missing cos-phi power factor. I deleted, reincluded and reconfigured the device over and over again. I mean, having a 26,1 Amps from a single light-bulb would be an extreme realization, don't you think? (attached picture).

The device parameters were manually added but I couldn't intervene too much in the HomeCenter interface to modify the decimal as in the manual some parameters were 1,2 or 3-byte decimal and in the interface, I couldn't select anything but 2d or 4d .

I tried to learn a thing or two about api and commands via REST-console. I am not a programmer but I am eager to learn and make the stuff work.

For this particular device, I tried, after reconfiguration, to update the parameters via REST-console. Bu no matter how many times I am sending this:

Quote

{
"properties": {
"parameters": [{
            "id": 7,
            "size": 1,
            "value": 4
        }, {
            "id": 10,
            "size": 2,
            "value": 255
        }, {
            "id": 12,
            "value": 0
        }, {
            "id": 40,
            "size": 1,
            "value": 1
        }, {
            "id": 42,
            "size": 2,
            "value": 0
        }, {
            "id": 45,
            "size": 1,
            "value": 0
        }, {
            "id": 100,
            "size": 1,
            "value": 0
        }, {
            "id": 110,
            "size": 2,
            "value": 0
        }, {
            "id": 111,
            "size": 2,
            "value": 30
        }, {
            "id": 112,
            "lastReportedValue": 0,
            "lastSetValue": 0,
            "size": 1,
            "value": 0
        }, {
            "id": 130,
            "lastReportedValue": 16010452,
            "lastSetValue": 16010452,
            "size": 4,
            "value": 16010452
        }, {
            "id": 131,
            "size": 2,
            "value": 102
        }, {
            "id": 132,
            "size": 2,
            "value": 16640
        }, {
            "id": 11,
            "size": 2,
            "value": 0
        }, {
            "id": 13,
            "size": 2,
            "value": 0
        }, {
            "id": 14,
            "size": 2,
            "value": 0
        }, {
            "id": 145,
            "size": 1,
            "value": 18960
        }, {
            "id": 146,
            "size": 1,
            "value": 4395
        }, {
            "id": 147,
            "size": 1,
            "value": 19869
        }, {
            "id": 148,
            "size": 1,
            "value": 0
        }, {
            "id": 143,
            "size": 1,
            "value": 16776625
        }, {
            "id": 144,
            "size": 4,
            "value": 9863
        }, {
            "id": 142,
            "size": 1,
            "value": 3623
        }, {
            "id": 141,
            "size": 3,
            "value": 1897
        }, {
            "id": 140,
            "size":1,
            "value": 2181
}]
}

 

 the result is this:

 

Quote

1. {
2. "id": 101,
3. "name": "100.0",
4. "roomID": 18,
5. "type": "com.fibaro.energyMeter",
6. "baseType": "com.fibaro.meter",
7. "enabled": true,
8. "visible": true,
9. "isPlugin": false,
10. "parentId": 100,
11. "remoteGatewayId": 0,
12. "interfaces": ["energy", "power", "zwave", "zwaveMultiChannelAssociation", "zwaveSwitchAll"],
13. "properties": {
14. "parameters": [{
15. "id": 7,
16. "lastReportedValue": 4,
17. "lastSetValue": 4,
18. "size": 1,
19. "value": 4
20. }, {
21. "id": 10,
22. "lastReportedValue": 255,
23. "lastSetValue": 255,
24. "size": 2,
25. "value": 255
26. }, {
27. "id": 12,
28. "lastReportedValue": 0,
29. "lastSetValue": 0,
30. "size": 2,
31. "value": 0
32. }, {
33. "id": 40,
34. "lastReportedValue": 1,
35. "lastSetValue": 1,
36. "size": 1,
37. "value": 1
38. }, {
39. "id": 42,
40. "lastReportedValue": 0,
41. "lastSetValue": 0,
42. "size": 2,
43. "value": 0
44. }, {
45. "id": 45,
46. "lastReportedValue": 0,
47. "lastSetValue": 0,
48. "size": 1,
49. "value": 0
50. }, {
51. "id": 100,
52. "lastReportedValue": 0,
53. "lastSetValue": 0,
54. "size": 1,
55. "value": 0
56. }, {
57. "id": 110,
58. "lastReportedValue": 0,
59. "lastSetValue": 0,
60. "size": 2,
61. "value": 0
62. }, {
63. "id": 111,
64. "lastReportedValue": 30,
65. "lastSetValue": 30,
66. "size": 2,
67. "value": 30
68. }, {
69. "id": 112,
70. "lastReportedValue": 0,
71. "lastSetValue": 0,
72. "size": 1,
73. "value": 0
74. }, {
75. "id": 130,
76. "lastReportedValue": 16010452,
77. "lastSetValue": 16010452,
78. "size": 4,
79. "value": 16010452
80. }, {
81. "id": 131,
82. "lastReportedValue": 102,
83. "lastSetValue": 102,
84. "size": 2,
85. "value": 102
86. }, {
87. "id": 132,
88. "lastReportedValue": 16640,
89. "lastSetValue": 16640,
90. "size": 2,
91. "value": 16640
92. }, {
93. "id": 11,
94. "lastReportedValue": 0,
95. "lastSetValue": 0,
96. "size": 2,
97. "value": 0
98. }, {
99. "id": 13,
100. "lastReportedValue": 0,
101. "lastSetValue": 0,
102. "size": 2,
103. "value": 0
104. }, {
105. "id": 14,
106. "lastReportedValue": 0,
107. "lastSetValue": 0,
108. "size": 2,
109. "value": 0
110. }, {
111. "id": 145,
112. "lastReportedValue": 0,
113. "lastSetValue": 18960,
114. "size": 1,
115. "value": 0
116. }, {
117. "id": 146,
118. "lastReportedValue": 4450,
119. "lastSetValue": 4450,
120. "size": 4,
121. "value": 4450
122. }, {
123. "id": 147,
124. "lastReportedValue": 20063,
125. "lastSetValue": 20063,
126. "size": 4,
127. "value": 20063
128. }, {
129. "id": 148,
130. "lastReportedValue": 0,
131. "lastSetValue": 0,
132. "size": 4,
133. "value": 0
134. }, {
135. "id": 143,
136. "lastReportedValue": 16775909,
137. "lastSetValue": 16775909,
138. "size": 4,
139. "value": 16775909
140. }, {
141. "id": 144,
142. "lastReportedValue": 9972,
143. "lastSetValue": 9972,
144. "size": 4,
145. "value": 9972
146. }, {
147. "id": 142,
148. "lastReportedValue": 2606,
149. "lastSetValue": 2606,
150. "size": 4,
151. "value": 2606
152. }, {
153. "id": 141,
154. "lastReportedValue": 1626,
155. "lastSetValue": 1626,
156. "size": 4,
157. "value": 1626
158. }, {
159. "id": 140,
160. "lastReportedValue": 2252,
161. "lastSetValue": 2252,
162. "size": 4,
163. "value": 2252
164. }],
165. "pollingTimeSec": 0,
166. "zwaveCompany": "Goap",
167. "zwaveInfo": "3,4,5",
168. "zwaveVersion": "1.1",
169. "configured": true,
170. "dead": false,
171. "deviceControlType": 0,
172. "deviceIcon": 102,
173. "emailNotificationID": 0,
174. "emailNotificationType": 0,
175. "endPointId": 0,
176. "energy": 0.0,
177. "liliOffCommand": "",
178. "liliOnCommand": "",
179. "log": "",
180. "logTemp": "",
181. "manufacturer": "",
182. "markAsDead": true,
183. "model": "",
184. "nodeId": 17,
185. "parametersTemplate": "0",
186. "power": 292.6,
187. "productInfo": "1,89,0,7,0,82,1,1",
188. "pushNotificationID": 0,
189. "pushNotificationType": 0,
190. "remoteGatewayId": 0,
191. "saveLogs": true,
192. "serialNumber": "ZMNHTD1 H1S2P1",
193. "showEnergy": true,
194. "smsNotificationID": 0,
195. "smsNotificationType": 0,
196. "switchAllMode": "SWITCH_ALL_INCLUDED_IN_THE_ALL_ON_ALL_OFF_FUNCTIONALITY",
197. "unit": "kWh",
198. "useTemplate": true,
199. "userDescription": "",
200. "value": 0.0
201. },
202. "actions": {
203. "reconfigure": 0,
204. "reset": 0
205. },
206. "created": 1503954136,
207. "modified": 1503954136,
208. "sortOrder": 27
209. }

 

 

 

Sincerely, I am over my head. I believe that some will think about this as a newbie problem, maybe I am too into it to figure out the obvious, but I really really need help understanding and addressing this problem, as well as how to solve it, how to add correct parameters and to make a goddamn 150 EUR device (QubinoSmart Meter) display some values.

 

Thank you

Please login or register to see this attachment.

Please login or register to see this attachment.

[RH_Dreambox 189]

Parameters 140 - 148 does not exist.
Remove them and use the parameters in the link below.

Please login or register to see this link.

 

[Radu Crisan 0]

On 30/08/2017 at 10:33 AM, RH_Dreambox said:

Parameters 140 - 148 does not exist.
Remove them and use the parameters in the link below.

Please login or register to see this link.

 

Hello. Sorry, I've been away for a while.

Still the same damn thing about the Qubino ZMNHTD1 SmartMeter. I've cleared the 140-148 parameters and still the same bug. It won't display the correct amperage (is multiplied by fact 10 - foto attached) and no reactive power. The thing with reactive power is probably related to the fact that amperage is "too high". It is physically impossible to have 99 Amps on a home. 

Please login or register to see this attachment.

Please login or register to see this attachment.

[RH_Dreambox 189]

Parameters 130 and above (130 to 148) is read only parameters, so delete them.
Default parameters is
Par.    Byte    Value
7    1    4
10    2    255
11    2    0
12    2    0
13    2    0
14    2    0
40    1    10     (or 1)
42    2    0    (60, 300, 600 or 1800 if you prefere that)
45    1    0
100    1    0
110    2    0
111    2    30
112    1    0

[Radu Crisan 0]

Thanks. I’ll modify them now

Edited September 26, 2017 by Radu Crisan

[petergebruers 1,268]

This is a very long shot, but could this be a matter of firmware on the qubino? I have an old thermostat from them and it has a similar 10x issue for temperature.The newer model with different firmware should work. I wrote a workaround, I published it on this forum. I doubt this approach works for the energy meter.

 

So maybe you can publish your firmware versions here?

[Radu Crisan 0]

I attached the device's templates.

Please login or register to see this attachment.

Damn it ! Still the same *abuse* !

(attached)

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

[petergebruers 1,268]

I had a look at the file you attached and it says firmware "1.01".

Now we need info from other users, because I do not own this device...

[Radu Crisan 0]

Quick update: the problem is ... still on. Because as of yesterday, the piece of #### that is Qubino Smart meter, decided not to show amperage at all.

Please login or register to see this attachment.

[Radu Crisan 0]

On 26/09/2017 at 10:26 AM, petergebruers said:

This is a very long shot, but could this be a matter of firmware on the qubino? I have an old thermostat from them and it has a similar 10x issue for temperature.The newer model with different firmware should work. I wrote a workaround, I published it on this forum. I doubt this approach works for the energy meter.

 

So maybe you can publish your firmware versions here?

 

can you show me that post? Maybe I can make it work

[petergebruers 1,268]

I am not at home and the code is on my HC. Diffcult to do on my phone.

 

It won't make you happy: it is a fix, to set the correct temperature on a thermostat. It does not fix your issue. And it has nothing to do with parameters either. But for educational purposes, I will post the code later. You might not get an update in your mail because the forum software merges answers... so please check this post this evening.

 

Edit: here's the code:

Please login or register to see this code.

 

 

Edited September 28, 2017 by petergebruers

[Radu Crisan 0]

15 hours ago, petergebruers said:

I am not at home and the code is on my HC. Diffcult to do on my phone.

 

It won't make you happy: it is a fix, to set the correct temperature on a thermostat. It does not fix your issue. And it has nothing to do with parameters either. But for educational purposes, I will post the code later. You might not get an update in your mail because the forum software merges answers... so please check this post this evening.

 

Edit: here's the code:

Please login or register to see this code.

 

 

aa, so it's a scene. Thanks, man

[petergebruers 1,268]

It has to be a scene, because it needs to run each time someone or something sets the thermostat. For example, when you change the temp to 22 on your phone, the device goes to 2.2 and the scene runs. It multplies the set point by 100, so the controller sends "220" which the valve correctly sees as 22.