Frontend issues with v0.9 and Hue Binding issues (may be related)

---

Hi,
yesterday I installed the latest version of pimatic. It all looks really sleek and I’m excited to use it!

Unfortunately there are a few issues I’m hitting. My setup currently is quite simple: I have the main application and the hue-zll binding installed.
The auto discovery works quite well (one of the reasons I choose pimatic, thanks for that!)

First: THe UI hangs a lot because of ui errors e.g.: Those appear after I added devices (via auto discovery) and then wanted to add them to pages.

error [pimatic-mobile-frontend]: Client error: Uncaught TypeError: Unable to process binding "if: function (){return !$root.isGroupCollapsed($data,{id:’$ungrouped’}) }"
Message: Unable to process binding "template: function (){return { name:$root.getItemTemplate,foreach:$data.getUngroupedDevices(),afterRender:$data.afterRenderDevice} }"
Message: ref.spectrum is not a function

error [pimatic-mobile-frontend]: Client error: Uncaught TypeError: Unable to process binding "if: function (){return !$root.isGroupCollapsed($data,{id:’$ungrouped’}) }"
Message: Unable to process binding "template: function (){return { name:$root.getItemTemplate,foreach:$data.getUngroupedDevices(),afterRender:$data.afterRenderDevice} }"
Message: ref.spectrum is not a function

error [pimatic-mobile-frontend]: Client error: You cannot apply bindings multiple times to the same element.

error [pimatic-mobile-frontend]: Client error: ref.spectrum is not a function

error [pimatic-mobile-frontend]: Client error: Cannot read property ‘length’ of undefined

Another problem is with the hue biding were commands simply don’t activate any functions. But this could be related to the errors above…

@tlindener: Strange, but it seems similar to this issue that was reported some months ago:

https://forum.pimatic.org/topic/1461/new-pimatic-plugin-for-integration-with-philips-hue/86

It seems to be related to the “Spectrum” JS color picker that’s used for selecting colors for color lights.

Could you please test whether you have issues when you configure all your lights as non-color lights? (Just override the class that is suggested during auto-discovery to any that isn’t HueZLLColorLight or HueZLLExtendedColorLight). Then the color picker is not used.

So this is a plain pimatic 0.9 install without any other plugins besides mobile-frontend and pimatic-hue-zll? What browser are you using?

Hi,

thanks for the quick reply!

I modified the device class as requested and it now works. (also controlling the light works now!)

I still get errors like these:
error [pimatic-mobile-frontend]: Client error: Cannot read property ‘top’ of undefined
error [pimatic-mobile-frontend]: Client error: Cannot read property ‘length’ of undefined
When moving items in the ui (just the one device actually)

It’s a plain pimatic 0.9 installation with mobile-frontend and pimatic-hue-zll. It’s a fresh installation from yesterday. I’m working with chromium on Ubuntu 16.04. To be honest I haven’t followed the installation procedere exactly and used NodeJs 6.3 since I’m developing my own software on this device too and therefor prefer to use the latest version.

I hope that’s not interfering with pimatic since these issues are all ui related.

@tlindener said in Frontend issues with v0.9 and Hue Binding issues (may be related):

It’s a plain pimatic 0.9 installation with mobile-frontend and pimatic-hue-zll. It’s a fresh installation from yesterday. I’m working with chromium on Ubuntu 16.04. To be honest I haven’t followed the installation procedere exactly and used NodeJs 6.3 since I’m developing my own software on this device too and therefor prefer to use the latest version.

I hope that’s not interfering with pimatic since these issues are all ui related.

That’s probably the reason then. Node.js 6.3 and npm 3 do some things differently, and this can impact e.g. the way modules are installed, mobile-frontend is setup and assets are loaded. Pimatic 0.9 currently targets Node.js 4 LTS, so this hasn’t really been tested.

Please try with a Node.js 4 LTS install and report back whether this fixes it for you. Thanks!

Hi,

I did as you asked today. I removed nodejs 6.3 via apt-get remove --purge, reinstalled nodejs 4 via apt. Removed the whole pimatic folder, reinstalled pimatic, reinstalled the hue plugin and restarted.

error [pimatic-mobile-frontend]: Client error: Cannot read property ‘length’ of undefined
11:43:13error [pimatic-hue-zll]: Can’t initialize device wohnzimmer-lamp-1 because the Hue API failed to initialize: Hue bridge username/key unavailable
11:42:56error [pimatic]: (not @variables[variable.name]?)
11:42:56error [pimatic-hue-zll]: Can’t initialize device schlafzimmer-lamp-1 because the Hue API failed to initialize: Hue bridge username/key unavailable
11:42:21error [pimatic-mobile-frontend]: Client error: Cannot read property ‘length’ of undefined
11:42:21error [pimatic]: listener must be a function
11:41:36error [pimatic-mobile-frontend]: Client error: Cannot read property ‘__ko__1470735533279’ of null
11:41:10error [pimatic-hue-zll]: Can’t initialize device schlafzimmer-lamp-1 because the Hue API failed to initialize: Hue bridge username/key unavailable

Since the auto discovery already listed my lamps the error from the pimatic-hue plugin is completely wrong (bug?)

@tlindener said in Frontend issues with v0.9 and Hue Binding issues (may be related):

I did as you asked today. I removed nodejs 6.3 via apt-get remove --purge, reinstalled nodejs 4 via apt. Removed the whole pimatic folder, reinstalled pimatic, reinstalled the hue plugin and restarted.

So I assume with that, the frontend issues you were seeing are gone now?

11:41:10error [pimatic-hue-zll]: Can’t initialize device schlafzimmer-lamp-1 because the Hue API failed to initialize: Hue bridge username/key unavailable

Since the auto discovery already listed my lamps the error from the pimatic-hue plugin is completely wrong (bug?)

So you didn’t copy the old configuration (config.json)? This was fully auto-discovered from an empty configuration, and it found your lamps but still gave this error?
Is the Hue API username (key) listed in the pimatic-hue-zll configuration section now?

No, they aren’t. As you can see from the log this:

error [pimatic-mobile-frontend]: Client error: Cannot read property ‘length’ of undefined

still appears when I try to add the item to the favorites page (which at least partly worked before anyway)

11:41:36error [pimatic-mobile-frontend]: Client error: Cannot read property ‘__ko__1470735533279’ of null

This was there before too, I simply wasn’t able to reproduce it, which is why I left it out.

So you didn’t copy the old configuration (config.json)? This was fully auto-discovered from an empty configuration, and it found your lamps but still gave this error?

No, I copied only the sample config and reconfigured everything accordingly. I wasn’t aware of the differences between node 4 and 6, which is why I assumed I could do this before. Now I’m reproducing everything on a (really) clean environment.

Is the Hue API username (key) listed in the pimatic-hue-zll configuration section now?

Yes

@tlindener said in Frontend issues with v0.9 and Hue Binding issues (may be related):

No, they aren’t. As you can see from the log this:

error [pimatic-mobile-frontend]: Client error: Cannot read property ‘length’ of undefined

still appears when I try to add the item to the favorites page (which at least partly worked before anyway)

11:41:36error [pimatic-mobile-frontend]: Client error: Cannot read property ‘__ko__1470735533279’ of null

This was there before too, I simply wasn’t able to reproduce it, which is why I left it out.

It’s hard to say where in the frontend these messages are coming from unfortunately.

So you didn’t copy the old configuration (config.json)? This was fully auto-discovered from an empty configuration, and it found your lamps but still gave this error?

No, I copied only the sample config and reconfigured everything accordingly. I wasn’t aware of the differences between node 4 and 6, which is why I assumed I could do this before. Now I’m reproducing everything on a (really) clean environment.

Weird. It seems something is still going wrong with your install, but we don’t have much to go on. You said you installed nodejs 4 from apt, but at least raspbian jessie (for raspberry pi) which most people here are using, doesn’t have nodejs in apt. What distribution are you running pimatic on? Ubuntu 16.04 as well?

(pimatic can run fine in all sorts of environments of course, just trying to figure out what’s different here.)

Can I someone increase the log level? As you may have imagined the installation is for testing only, so I can easily crash it with some changes…

I’m running Debian Jessie(armbian.com) on a cubietruck (same armhf like raspi 2 just with ethernet, 2 gig ram and an ssd) with nodesource packages of nodejs 4.4.7 (latest).

I appreciate your help!

@tlindener said in Frontend issues with v0.9 and Hue Binding issues (may be related):

Can I someone increase the log level? As you may have imagined the installation is for testing only, so I can easily crash it with some changes…

Yes, pimatic’s global settings, as well as both pimatic-mobile-frontend and pimatic-hue-zll (plugin settings) have a “debug” setting that you can enable. Worth a try.

Also check your browser console for clues perhaps.

I’m running Debian Jessie(armbian.com) on a cubietruck (same armhf like raspi 2 just with ethernet, 2 gig ram and an ssd) with nodesource packages of nodejs 4.4.7 (latest).

I’m using the nodesource 4.4.7 debian packages on raspbian jessie as well.

Ok, new developments. Debug mode was useless to find more issues

I’ve reinstalled pimatic again. This time I ensured to always use sudo (i don’t think that’s a good idea but I did anyway). And this is slightly better…

The issue with:
16:51:27error [pimatic]: listener must be a function
appears really often… and I found out when, it’s when I e.g. delete the device I just added.
Than I get a 400 Bad Request with this response:
{success: false, message: “listener must be a function”}

Afterwards the device is not listed anymore but I can’t create the same device again:
16:52:12error [pimatic]: Duplicate device id “schlafzimmer-lamp-1”

I still get lots of those:
error [pimatic-hue-zll]: Can’t initialize device schlafzimmer-lamp-2 because the Hue API failed to initialize: Hue bridge username/key unavailable
16:52:12error [pimatic-hue-zll]: Can’t initialize device schlafzimmer-lamp-1 because the Hue API failed to initialize: Hue bridge username/key unavailable
16:51:53error [pimatic]: (not @variables[variable.name]?)
16:51:53error [pimatic-hue-zll]: Can’t initialize device schlafzimmer-lamp-1 because the Hue API failed to initialize: Hue bridge username/key unavailable
16:50:55error [pimatic-hue-zll]: Can’t initialize device schlafzimmer-lamp-1 because the Hue API failed to initialize: Hue bridge username/key unavailable

But the good news: Using color items now works…

Is it supported to run pimatic.js as none root use (e.g. on port 8080) and then use a reverse proxy?

@tlindener said in Frontend issues with v0.9 and Hue Binding issues (may be related):

Ok, new developments. Debug mode was useless to find more issues

I’ve reinstalled pimatic again. This time I ensured to always use sudo (i don’t think that’s a good idea but I did anyway). And this is slightly better…

The issue with:
16:51:27error [pimatic]: listener must be a function
appears really often… and I found out when, it’s when I e.g. delete the device I just added.
Than I get a 400 Bad Request with this response:
{success: false, message: “listener must be a function”}

Afterwards the device is not listed anymore but I can’t create the same device again:
16:52:12error [pimatic]: Duplicate device id “schlafzimmer-lamp-1”

I haven’t seen this yet but I’ll try if I can replicate this.

Is it supported to run pimatic.js as none root use (e.g. on port 8080) and then use a reverse proxy?

Yes. Some plugins (like pimatic-homeduino) need root access for some things by default, but pimatic-hue-zll doesn’t. I’m running a dev instance as non-root on a high port without issues. Instead of a reverse proxy you could also use an iptables DNAT rule, or use “setcap” to allow it to bind port 80.