You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IF you make a change to the httpRoot setting in settings.js for node red then when the system tries to serve up the list of discovered entities it tries to pull it from the wrong URL
// The following property can be used in place of 'httpAdminRoot' and 'httpNodeRoot',
// to apply the same root to both parts.
httpRoot: '/node-red',
On line 47 of server-events-state-changed.html - we can see the url it fetches to show entities, as it does not take into account httpRoot variable I have done a quick and dirty hard code - I am sure there must be a better way of fixing this but I am not a coder :-( as you can see below all I have done is manually put in the additional info for my installation.
The text was updated successfully, but these errors were encountered:
schford
changed the title
Does not take into account any changes to httpRoot in node-red config to serve up list of entities pulled form Home Assist
Does not take into account any changes to httpRoot in node-red config to serve up list of entities pulled from Home Assist
Jun 25, 2018
IF you make a change to the httpRoot setting in settings.js for node red then when the system tries to serve up the list of discovered entities it tries to pull it from the wrong URL
For my install it is trying to pull from
http://192.168.0.19:1880/homeassistant/entities
rather than
http://192.168.0.19:1880/node-red/homeassistant/entities
as I made this change in settings.js
On line 47 of server-events-state-changed.html - we can see the url it fetches to show entities, as it does not take into account httpRoot variable I have done a quick and dirty hard code - I am sure there must be a better way of fixing this but I am not a coder :-( as you can see below all I have done is manually put in the additional info for my installation.
The text was updated successfully, but these errors were encountered: