d3 client page not coming up

[claudiuo]

I upgraded to the new 1.5 version on a Linux Mint v15 laptop following the steps Marshall gave me: % npm config set strict-ssl false % npm update npm -g % npm config set strict-ssl true % sudo /etc/init.d/steward stop % cd steward % git pull % cd steward % rm -rf node_modules % npm -l install % sudo /etc/init.d/steward start -> actually this doesn't work for me, instead I run the steward using sudo ./run.sh

The steward starts without any errors, the only thing I see in the console is a warning: * WARNING * The program 'node' uses the Apple Bonjour compatibility layer of Avahi. * WARNING * Please fix your application to use the native API of Avahi! * WARNING * For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node * WARNING * The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. * WARNING * Please fix your application to use the native API of Avahi! * WARNING * For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister

However, the d3 page doesn't come up, I tried http://localhost:8887, http://127.0.0.1:8887 and http://:8887.

Is there anything else I can check? Thank you in advance for all your help!

[claudiuo]

Trying to figure out what may be happening, I started looking around and found that steward/clients/d3 folder was empty (apart from a readme file saying the source of the d3 client is in ../../steward/sandbox/d3/. Went to this folder, and copied all the files to steward/clients/d3. Restarted the steward and the d3 page now comes up.

I am not sure why the d3 folder was empty to start with but I guess this can be closed.

[aallan]

Couple of things, the Avahi warnings are normal and the init.d command will only work if you've deployed the init.d startup scripts, which if you've installed from source, you probably won't have…

If you're running the browser and steward on the same machine, then post start up the d3 client should show up on port 8887. If the browser is on a different machine you should use https (rather than http) and go to port 8888.

However moving the d3 client from steward/sandbox/d3/ to steward/clients/d3/ shouldn't have worked. It's supposed to be in the sandbox directory.

Can you copy-and-paste the entire startup output from the ./run.sh script so I can take a look?

[claudiuo]

This is very strange... I wanted to get the startup output from before when the d3 client wasn't loading so I deleted all the files in steward/clients/d3, started the steward and... everything is fine, the d3 pages comes up when I go to http://localhost:8887/d3/index.html. I don't get it, I tried several times before and it didn't work. Then I copied the files to the d3 folder and it worked. Now I deleted these files and it still works... So basically all is well now.

Anyway, not sure if this helps, I remember when running ./run.sh before that the output seemed to end with some info: [server] prompts. When it started working last night and now, after those prompts there are also info: [discovery] and info: [sensor] prompts.

Since all is fine, I assume the output won't help you at all but here it is just in case. As a side note, probably not important at all, in the console output I see that both my Chromecast and my Roku were discovered but in the d3 client only Chromecast shows up for some reason. But I don't think this has any bearing in this issue.

Thanks again for all you do, your help and patience!

~/steward/steward $ sudo ./run.sh info: running on Linux Debian wheezy/sid ( 3.8.0-19-generic x86_64) info: using node v0.10.25 * WARNING * The program 'node' uses the Apple Bonjour compatibility layer of Avahi. * WARNING * Please fix your application to use the native API of Avahi! * WARNING * For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node * WARNING * The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. * WARNING * Please fix your application to use the native API of Avahi! * WARNING * For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister info: [devices] loading climate driver debug: [climate] begin info: [devices] loading gateway driver info: [devices] loading indicator driver info: [devices] loading lighting driver info: [devices] loading media driver debug: [media] begin info: [devices] loading motive driver debug: [motive] begin info: [devices] loading presence driver info: [devices] loading sensor driver info: [devices] loading switch driver info: [devices] loading wearable driver debug: [wearable] begin info: [climate] loading ecobee-control driver info: [climate] loading flower-power-sensor driver info: [climate] loading koubachi-sensor driver info: [climate] loading nest-control driver info: [climate] loading netatmo-sensor driver info: [climate] loading oregon-scientific-sensor driver info: [climate] loading samsung-control driver info: [climate] loading yoctopuce-co2 driver info: [climate] loading yoctopuce-light driver info: [climate] loading yoctopuce-meteo driver info: [climate] loading yoctopuce-voc driver info: [discovery] SSDP listening on http://0.0.0.0:1900 info: [gateway] loading automatic-cloud gateway info: [gateway] loading ecobee-cloud gateway info: [devices] failing ecobee-cloud gateway (continuing) diagnostic=Cannot find module 'ecobee-api' info: [gateway] loading flower-power-cloud gateway info: [gateway] loading insteon-9761 gateway info: [gateway] loading koubachi-cloud gateway info: [gateway] loading lockitron-cloud gateway info: [gateway] loading nest-cloud gateway info: [gateway] loading netatmo-cloud gateway info: [gateway] loading openzwave-usb gateway info: [gateway] loading reelyactive-reel gateway info: [gateway] loading rfxcom-usb gateway info: [gateway] loading tesla-cloud gateway info: [gateway] loading wink-cloud gateway info: [gateway] loading yoctopuce-hub gateway info: [gateway] loading zigbee-gmo gateway info: [discovery] reelyactive-reel driver listening on udp://:7018 info: [indicator] loading dweetio-sensor driver info: [indicator] loading irtoy-infrared driver info: [indicator] loading mqtt-text driver info: [indicator] loading nma-text driver info: [indicator] loading prowl-text driver info: [indicator] loading wink-dial driver info: [indicator] loading wink-nimbus driver info: [indicator] loading xively-sensor driver info: [lighting] loading blink1-led driver info: [lighting] loading blinkstick-led driver info: [lighting] loading heroicrobotics driver info: [lighting] loading hue driver info: [lighting] loading insteon-led driver info: [lighting] loading robosmart-led driver info: [lighting] loading tabu-lumen driver info: [lighting] loading tcpi-led driver ** WARNING * The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. * WARNING * Please fix your application to use the native API of Avahi! * WARNING *\ For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister info: [lighting] loading yoctopuce-color driver info: [lighting] loading yoctopuce-powercolor driver info: [discovery] PixelPusher listening on udp://:7331 info: [media] loading audio-sonos driver info: [media] loading camera-axis driver info: [media] loading video-appletv driver info: [media] loading video-chromecast driver info: [media] loading video-roku driver info: [motive] loading automatic-vehicle driver info: [motive] loading crazyflie-3d driver info: [motive] loading irobot-floor driver info: [motive] loading lockitron-lock driver info: [motive] loading tesla-model-s driver info: [presence] loading fob driver info: [presence] loading mobile-mqtt driver info: [presence] loading reelyactive-tag driver info: [switch] loading insteon-dimmer driver info: [switch] loading insteon-onoff driver info: [switch] loading wemo-onoff driver info: [switch] loading wink-onoff driver info: [switch] loading wink-pivot-power-genius driver info: [switch] loading zwave-dimmer driver info: [switch] loading zwave-onoff driver info: [wearable] loading watch driver notice: [steward] start uuid=2f402f80-da50-11e1-9b23-00226811d0c0 info: [server] listening on wss://:8888 info: [server] listening on wss://:8887 info: [server] listening on http://:80 info: [server] loading console route info: [server] loading manage route info: [server] loading oneshot route info: [server] loading root route info: [server] loading ble discovery info: [server] loading mac discovery info: [server] loading owl discovery info: [server] loading portscan discovery info: [server] loading ssdp discovery info: [server] loading tsrp discovery info: [discovery] OWL driver listening on multicast udp://224.192.32.19:22600 info: [discovery] SSDP listening on http://192.168.1.100:1900 info: [discovery] TSRP listening on multicast udp://224.0.9.1:22601 info: [discovery] UPnP listening on http://192.168.1.100:8886 info: [sensor] loading nest-smoke driver info: [sensor] loading texas-instruments-sensortag driver info: [sensor] loading wemo-motion driver info: [sensor] loading wink-spotter driver info: [sensor] loading yoctopuce-4-20mA-Rx driver info: [discovery] UPnP Tavi's Chromecast url=http://192.168.1.101:8008 info: [devices] found Tavi's Chromecast deviceID=1, deviceType=Eureka Dongle warning: [steward] place/1 Home event=getWeather, diagnostic=check in 2174.882 seconds info: [discovery] UPnP Roku Streaming Player url=http://192.168.1.107:8060/ info: [devices] found Roku Streaming Player deviceID=2, deviceType=urn:roku-com:device:player:1-0 info: [discovery] PORT starting scan info: [discovery] PORT finished scan

[aallan]

While the Roku is detected, and is supported, the API it offers is really very minimal. I don't think it's supposed to show up in the d3 client for that reasons. However if you want to make use of it you can still do so from your own clients.

Looks like you're good however, so I'm going to close the ticket.