Jump to content

version 0.9.36 on pi


beninsteon

Recommended Posts

Posted

Hi,

I updated to v36 on my pi today. Seems to be working fine without any major quirks. FYI - on the main screen it says "NodeLink Server v0.10.0", rather than 0.9.36. I updated from 0.9.29 using the shell script.

Also I'm having a hard time getting the homeseer device working. I have homeseer running on the same pi as nodelink, on port 8091 (not the default 80). In address I have "192.168.0.122:8091". It won't accept it if I add http:// at the beginning or use "localhost". In the debug log all I'm getting is 

2019-10-12 14:55:51 - HS: Socket Error - Connect - Name or service not known [hs1]
2019-10-12 14:56:21 - HS: Reconnecting To Server [hs1]

Repeated over and over. The Homeseer server is definitely running at that address.

Thanks.

Posted

Then your system updated to the new NET Core 3 version of NodeLink, 0.10.0.  

To use the Homeseer you need to enable the ASCII interface in Homeseer's settings.  

Posted

Thanks!

I enabled ASCII control (did not change default port of 11000) and now I'm getting a different error:

2019-10-12 17:09:35 - HS: Reconnecting To Server [hs1]
2019-10-12 17:09:35 - HS: Connected - Credentials Sent [hs1]
2019-10-12 17:09:35 - HS: Data - error, no user or bad pass
 [hs1]
2019-10-12 17:09:35 - HS: Error Getting Devices - There was an error deserializing the object of type NodeLink.VRoot. Encountered unexpected character '<'. [hs1]
2019-10-12 17:09:36 - HS: Data - DC,1013,0,1
 [hs1]
2019-10-12 17:09:43 - HS: Data - DC,1021,0,1
 [hs1]

 

and I'm not seeing any devices under nodes. Are all homeseer device types supported or only some?

Posted
15 hours ago, beninsteon said:

Thanks!

I enabled ASCII control (did not change default port of 11000) and now I'm getting a different error:

2019-10-12 17:09:35 - HS: Reconnecting To Server [hs1]
2019-10-12 17:09:35 - HS: Connected - Credentials Sent [hs1]
2019-10-12 17:09:35 - HS: Data - error, no user or bad pass
 [hs1]
2019-10-12 17:09:35 - HS: Error Getting Devices - There was an error deserializing the object of type NodeLink.VRoot. Encountered unexpected character '<'. [hs1]
2019-10-12 17:09:36 - HS: Data - DC,1013,0,1
 [hs1]
2019-10-12 17:09:43 - HS: Data - DC,1021,0,1
 [hs1]

 

and I'm not seeing any devices under nodes. Are all homeseer device types supported or only some?

Very few devices are supported since each type will require a new nodedef.  

Once you get logged in you can send me a debug log which will give me your device list.  

Posted

Where do I configure the username and password in nodelink?

Is there a default combo I should be using?

I don't think I have any devices that you support but it would be great if Chromecast devices could be supported. The Chromecast poly for isy does not work any longer.

Posted

I wonder if it would be possible for you to configure nodelink to accept custom nodedefs for Homeseer devices. This would allow individual users to expand nodelink's capacity and share custom definitions. It would be a powerful option that would expand the ISY to accept all Homeseer devices/plugins... Without using state variables and Homeseer events, which I've found to be unreliable.

Posted

Hi,

Figured out I need to use the default credentials (default/default) for nodelink to connect. Unfortunately it doesn't seem to be getting the device list. Here's the debug log when I start nodelink:

2019-10-13 20:48:37 - ISY NodeLink Server v0.10.0 started
2019-10-13 20:48:37 - OS: Linux raspberrypi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
2019-10-13 20:48:38 - Web config server started (http://192.168.0.122:8090)
2019-10-13 20:48:38 - ISY resolved to 192.168.0.111 (5.0.15)
2019-10-13 20:48:38 - ISY Node Server config detected (profile 1)
2019-10-13 20:48:40 - ISY Warning: Duplicate node names exist on the ISY (Watch Kodi)
2019-10-13 20:48:40 - ISY Warning: Duplicate node names exist on the ISY (Watch TV)
2019-10-13 20:48:40 - ISY Warning: Duplicate node names exist on the ISY (MyGica Media Player)
2019-10-13 20:48:41 - HS: Error Getting Devices - There was an error deserializing the object of type NodeLink.VRoot. Encountered unexpected character '<'. [hs1]
2019-10-13 20:48:41 - HS: Connected - Credentials Sent [hs1]
2019-10-13 20:48:41 - HS: Data - ok
 [hs1]
2019-10-13 20:48:41 - HS: Data - 3.0.0.531
 [hs1]
2019-10-13 20:48:41 - HS: Error Getting Devices - There was an error deserializing the object of type NodeLink.VRoot. Encountered unexpected character '<'. [hs1]
 

Posted

When I use putty to access the ASCII server myself, here's what I get when I issue some basic commands including get devices

au,default,default
gs
1000,997,,Title,ChromecastPI,outside speakers|1001,997,,Artist,ChromecastPI,outside speakers|1002,997,,Image,ChromecastPI,outside speakers|1003,997,None,Application,ChromecastPI,outside speakers|1004,997,Unknown,Duration,ChromecastPI,outside speakers|1005,0,Connected to 192.168.0.15,Root,ChromecastPI,Living room speakers|1006,1005,10%,Volume,ChromecastPI,Living room speakers|1007,1005,Idle,Status,ChromecastPI,Living room speakers|1008,1005,,Title,ChromecastPI,Living room speakers|1009,1005,,Artist,ChromecastPI,Living room speakers|1010,1005,,Image,ChromecastPI,Living room speakers|1011,1005,None,Application,ChromecastPI,Living room speakers|1012,1005,Unknown,Duration,ChromecastPI,Living room speakers|1013,0,Connected to 192.168.0.3,Root,ChromecastPI,Basement speakers|1014,1013,50%,Volume,ChromecastPI,Basement speakers|1015,1013,Idle,Status,ChromecastPI,Basement speakers|1016,1013,,Title,ChromecastPI,Basement speakers|1017,1013,,Artist,ChromecastPI,Basement speakers|1018,1013,,Image,ChromecastPI,Basement speakers|1019,1013,None,Application,ChromecastPI,Basement speakers|1020,1013,Unknown,Duration,ChromecastPI,Basement speakers|1021,0,Connected to 192.168.0.13,Root,ChromecastPI,Ceiling speakers|1022,1021,20%,Volume,ChromecastPI,Ceiling speakers|1023,1021,Idle,Status,ChromecastPI,Ceiling speakers|1024,1021,,Title,ChromecastPI,Ceiling speakers|1025,1021,,Artist,ChromecastPI,Ceiling speakers|1026,1021,,Image,ChromecastPI,Ceiling speakers|1027,1021,None,Application,ChromecastPI,Ceiling speakers|1028,1021,Unknown,Duration,ChromecastPI,Ceiling speakers|1029,0,Connected to 192.168.0.7,Root,ChromecastPI,Basement TV|1030,1029,100%,Volume,ChromecastPI,Basement TV|1031,1029,Unknown,Status,ChromecastPI,Basement TV|1032,1029,,Title,ChromecastPI,Basement TV|1033,1029,,Artist,ChromecastPI,Basement TV|1034,1029,,Image,ChromecastPI,Basement TV|1035,1029,Backdrop,Application,ChromecastPI,Basement TV|1036,1029,Unknown,Duration,ChromecastPI,Basement TV|1037,0,Connected to 192.168.0.13,Root,ChromecastPI,First floor speakers|1038,1037,40%,Volume,ChromecastPI,First floor speakers|1039,1037,Idle,Status,ChromecastPI,First floor speakers|1040,1037,,Title,ChromecastPI,First floor speakers|1041,1037,,Artist,ChromecastPI,First floor speakers|1042,1037,,Image,ChromecastPI,First floor speakers|1043,1037,None,Application,ChromecastPI,First floor speakers|1044,1037,Unknown,Duration,ChromecastPI,First floor speakers|1045,0,Connected to 192.168.0.24,Root,ChromecastPI,Family Room TV|1046,1045,100%,Volume,ChromecastPI,Family Room TV|1047,1045,Unknown,Status,ChromecastPI,Family Room TV|1048,1045,,Title,ChromecastPI,Family Room TV|1049,1045,,Artist,ChromecastPI,Family Room TV|1050,1045,,Image,ChromecastPI,Family Room TV|1051,1045,Backdrop,Application,ChromecastPI,Family Room TV|1052,1045,Unknown,Duration,ChromecastPI,Family Room TV|1053,0,Connected to 192.168.0.20,Root,ChromecastPI,Bedroom speakers|1054,1053,50%,Volume,ChromecastPI,Bedroom speakers|1055,1053,Idle,Status,ChromecastPI,Bedroom speakers|1056,1053,,Title,ChromecastPI,Bedroom speakers|1057,1053,,Artist,ChromecastPI,Bedroom speakers|1058,1053,,Image,ChromecastPI,Bedroom speakers|1059,1053,None,Application,ChromecastPI,Bedroom speakers|1060,1053,Unknown,Duration,ChromecastPI,Bedroom speakers|1067,0,0,sMusicBasement.PlayState,ISY,Basement speakers|1069,0,0,sMusicBedroom.PlayState,ISY,Bedroom speakers|1071,0,0,sMusicCeiling.PlayState,ISY,Ceiling speakers|1074,0,0,sMusicFamilyRm.PlayState,ISY,Family Room TV|1076,0,0,sMusicFirstFloor.PlayState,ISY,First floor speakers|1078,0,0,sMusicLivingRm.PlayState,ISY,Living room speakers|1080,0,0,sMusicOutside.PlayState,ISY,outside speakers|1087,0,0,sMusicBasementTV.PlayState,ISY,Basement TV|1088,0,0,sMusicBasement.App,ISY,Basement speakers|1089,0,0,sMusicBasement.Volume,ISY,Basement speakers|1090,0,0,sMusicBasementTV.App,ISY,Basement TV|1091,0,0,sMusicBasementTV.Volume,ISY,Basement TV|1092,0,0,sMusicBedroom.App,ISY,Bedroom speakers|1093,0,0,sMusicBedroom.Volume,ISY,Bedroom speakers|1094,0,0,sMusicCeiling.App,ISY,Ceiling speakers|1095,0,0,sMusicCeiling.Volume,ISY,Ceiling speakers|1096,0,0,sMusicFamilyRm.App,ISY,Family Room TV|1097,0,0,sMusicFamilyRm.Volume,ISY,Family Room TV|1098,0,0,sMusicFirstFloor.App,ISY,First floor speakers|1099,0,0,sMusicFirstFloor.Volume,ISY,First floor speakers|1100,0,0,sMusicLivingRm.App,ISY,Living room speakers|1101,0,0,sMusicLivingRm.Volume,ISY,Living room speakers|1102,0,0,sMusicOutside.App,ISY,outside speakers|1103,0,0,sMusicOutside.Volume,ISY,outside speakers|1104,0,Connected to 192.168.0.19,Root,ChromecastPI,Bedroom home|1105,1104,60%,Volume,ChromecastPI,Bedroom home|1106,1104,Idle,Status,ChromecastPI,Bedroom home|1107,1104,,Title,ChromecastPI,Bedroom home|1108,1104,,Artist,ChromecastPI,Bedroom home|1109,1104,,Image,ChromecastPI,Bedroom home|1110,1104,None,Application,ChromecastPI,Bedroom home|1111,1104,Unknown,Duration,ChromecastPI,Bedroom home|1147,0,Connected to 192.168.0.6,Root,,Kitchen home|1148,1147,60%,Volume,,Kitchen home|1149,1147,Idle,Status,,Kitchen home|1150,1147,,Title,,Kitchen home|1151,1147,,Artist,,Kitchen home|1152,1147,,Image,,Kitchen home|1153,1147,None,Application,,Kitchen home|1154,1147,Unknown,Duration,,Kitchen home|997,0,Connected to 192.168.0.5,Root,ChromecastPI,outside speakers|998,997,30%,Volume,ChromecastPI,outside speakers|999,997,Idle,Status,ChromecastPI,outside speakers

 

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...