Generate Panels does not work

[souvilleParticipant]

Hello

I’m a new user of Pulse Station.
I’m trying to connect SRT322 (wireless thermostat SRT321 + receiver) with a z-stick 2.

I managed to associate the receiver with z-stick
(It shows in Services > Zwave of PulseStation :
zwave-1 | Static PC Controller
zwave-2 | Thermostat)

I also managed to associate the wireless thermostat SRT321 with z-stick (It shows in Services > Zwave :
zwave-3 | Thermostat
zwave-4 | Thermostat).

I was surprise to see 2 “zwave devices” for each device ?

The pb is when I go to the admin Dashboard, if i click on Generate Panels, nothing happens.
Do I need to add panels with an other method ? (like this tuto https://www.pulse-station.com/fr/define-panel/ -> Ajouter un panneau manuellement)

What can I do ?
MariaDB and Pulse Station are installed, and the versions are the last one.

Thanks for your help

[woodronnieParticipant]

Hi,

I have the same issue.

Thanks for tips.

[coldbringerParticipant]

Hey, I encounter the same problems here. Any suggestions? Thank you!

[MikaKeymaster]

Can you consult the console of your browser to see if there is an error ?

[coldbringerParticipant]

Deprecated call to Blockly.updateToolbox, use workspace.updateToolbox instead. blockly_compressed.js:1297:103
Error: Blockly.getMainWorkspace(…) is null
Blockly.updateToolbox@http://192.168.0.101/PulseStation/blockly_src/static/blockly_compressed.js:1297:198
d.removeToolbox@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:13824
@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:52938
lf/this.$get</n.prototype.$broadcast@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:136:43
m/<@http://192.168.0.101/PulseStation/lib/angular/angular-route.min.js:11:408
f/<@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:119:113
lf/this.$get</n.prototype.$eval@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:217
lf/this.$get</n.prototype.$digest@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:130:225
lf/this.$get</n.prototype.$apply@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:510
h@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:87:374
K@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:91:1
Sf/</z.onload@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:93:37
angular.min.js:107:207

“pascalprecht.translate.$translateSanitization: No sanitization strategy has been configured. This can have serious security implications. See http://angular-translate.github.io/docs/#/guide/19_security for details.” angular.min.js:107:207
Deprecated call to Blockly.updateToolbox, use workspace.updateToolbox instead. blockly_compressed.js:1297:103
Error: Blockly.getMainWorkspace(…) is null
Blockly.updateToolbox@http://192.168.0.101/PulseStation/blockly_src/static/blockly_compressed.js:1297:198
d.removeToolbox@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:13824
@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:52938
lf/this.$get</n.prototype.$broadcast@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:136:43
m/<@http://192.168.0.101/PulseStation/lib/angular/angular-route.min.js:11:408
f/<@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:119:113
lf/this.$get</n.prototype.$eval@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:217
lf/this.$get</n.prototype.$digest@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:130:225
lf/this.$get</n.prototype.$apply@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:510
h@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:87:374
K@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:91:1
Sf/</z.onload@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:93:37
angular.min.js:107:207

Deprecated call to Blockly.updateToolbox, use workspace.updateToolbox instead. blockly_compressed.js:1297:103
Error: Blockly.getMainWorkspace(…) is null
Blockly.updateToolbox@http://192.168.0.101/PulseStation/blockly_src/static/blockly_compressed.js:1297:198
d.removeToolbox@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:13824
@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:52938
lf/this.$get</n.prototype.$broadcast@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:136:43
m/<@http://192.168.0.101/PulseStation/lib/angular/angular-route.min.js:11:408
f/<@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:119:113
lf/this.$get</n.prototype.$eval@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:217
lf/this.$get</n.prototype.$digest@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:130:225
lf/this.$get</n.prototype.$apply@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:510
h@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:87:374
K@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:91:1
Sf/</z.onload@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:93:37
angular.min.js:107:207

Error: m is null
c.addIdentification/</<@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:1
m@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:7:320
c.addIdentification/<@http://192.168.0.101/PulseStation/lib/PulseStation/PulseStation-admin.min.js:1:16366
n/h.success/<@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:87:26
f/<@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:119:113
lf/this.$get</n.prototype.$eval@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:217
lf/this.$get</n.prototype.$digest@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:130:225
lf/this.$get</n.prototype.$apply@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:133:510
h@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:87:374
K@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:91:1
Sf/</z.onload@http://192.168.0.101/PulseStation/lib/angular/angular.min.js:93:37
angular.min.js:107:207

[leroymthParticipant]

Hi Mika,

Same issue followed here : https://www.pulse-station.com/fr/forums/topic/objet-du-dashboard-non-visible/#post-2491

I think you can merge topics :).

Regards.

[souvilleParticipant]

Hello and thank you for helping

In the admin dashboard page, firebug console is ok. The four last lines are
“POST http://192.168.0.1/PulseStation/utils/php/isServiceRunning.php 200 OK”

And when I go to the zwave service page, firebug console get the same error than coldbringer, starting with
“Deprecated call to Blockly.updateToolbox, use workspace.updateToolbox instead.”

I don’t understand what could be the problem.
What can I test ?

Thanks

[K.RensKeymaster]

I haven’t seen before that one physical device is listed as 2 zwave devices, will check with Mika.
Generate panels usually works, if it does not, maybe you have a specific device that we did not add yet.

Can you control the device?
If Yes: you can create a scene that does the desired actions.
Then just use generate panels for adding the panels for running the scenes.
If then generate panels does not work, reply and I will give you how my scene panels look like.

Kind regards,
K.Rens

[MikaKeymaster]

If possible can you remove some devices (except if you have only zwave devices) ?

Otherwise I need access to your PulseStation, it will be easier to debug it…

[souvilleParticipant]

It works !!!!
Thanks a lot

My mistake was to think that I had to generate panels… But I don’t need to.
K.Rens you have certainly right, my specific device is not add to the system, so automatic panels doesnt work.

I can control things in Blockly, now I only have to understand what I can do.
I can control zwave-3 and zwave-4, which are the devices added whan I did associate the wireless thermostat.
I need to understand what are Switch (True or False) or Mode (Off or Heat)
I’m running tests, I think it will be ok.

Thanks again, the problem is solved

[K.RensKeymaster]

Glad to hear that 🙂

Kind regards,
K.Rens

[coldbringerParticipant]

In my case it seems that a bug in the sonos config file was responsible for the dahboards not working. Mika told me to remove “null,null” in the beginning of the sonos.json file. Afterwards, Sonos Service, Dashboards and Graphics worked again.

[Author]

Posts