Jump to content

Error changing settings in nodeservers


glarsen

Recommended Posts

Hi @javi, I'm running into an error when changing setttings.  The request seems to execute properly, as the setting on the device does change, and the display is updated with the new value.  It seems to happen on several nodeservers that I've tried including some of my own.  The error is: java.lang.Error: Error: 404. URL:http://my.polisyurl.here:8080/rest/nodes/n022_controller/cmd/POWER/0/25. 404.  This is on the Android version.

I thought at first I had made an error in a profile config, but I see the same with other's nodeservers as well.  As I said, the command executes, only this error is returned.  If I manually enter the listed URL above in a browser I also get 404.

  Any thoughts?

Link to comment

Hi @glarsen,

The URL looks good, and I've only encountered a persistent 404 when the ISY is under heavy load. Does anything stick out in /rest/log/error?

Is this for PG2 or PG3? What is the PG version number? What is the Pol-ISY firmware? Does the error persist after Polisy is rebooted?  Do you have the Hue Emulator or ELK NS installed?

Link to comment

Just updated to 3.0.40 from 3.0.38 and can not replicate, can you send a copy of the ISY error log? I read there were issues with 3.0.39, did you update to 3.0.39 at any point before 3.0.40?

We can get to the next items after the error log.

There are reported issues with older versions of PyISY (used in the Hue Emulator). Does the issue persist if the Hue Emulator NS is disabled? There is also a report involving ELK, but just a correlation and not verified as the cause of any issues, so please also disable both Node Servers if disabling Hue does not work. 

Link to comment

@Javi, same thing with both ELK and Hue disabled.  I don't recall what the last version of PG3 was before installing 3.0.40. Each time I make attempt this is all that appears in the ISY error log:

Time                      	User     	Code	Message
Thu. 2022/02/10 04:29:00 PM	0	-170001	<s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>	
Thu 2022/02/10 04:30:10 PM	0	-170001	<s:Envelope><s:Body><u:GetSystemStatus xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetSystemStatus></s:Body></s:Envelope>

Thanks,

G

Link to comment

Sorry, @Javi, I'm not sure what you mean by "will any of the node servers work without hardware".  The fault does seem to be specific to PG3 nodeservers - I have a couple of the same ones running on both PG2 and PG3.  Another thing I notice is that it seems to be related somehow to editors or nls. I haven't checked enough times yet to confirm but it seems that when the item being set/changed/cleared has a uom of 25 with text in the nls, the error occurs.  Doing something like changing a temperature setpoint for instance, with a pure number, doesn't cause an error.

If you like I can send you the profile files of one of my PG3 nodeservers that is exhibiting this behaviour.

Thanks,

Link to comment

Hi @glarsen,

I was looking to install one of the offending Node Servers on my system. Check if I receive the same errors to eliminate the possibility it is related to the specific ISY or Polyglot instance.  If the URL is throwing the same error it's not an issue with UD Mobile, so I think at this point we can eliminate the client. 

I still think the ISY is under a heavy load somewhere as I have Node Servers with UOM 25 an no issues.  Do you have multiple instances of Polyglot (2/3) connected to the same ISY/ISY-Service? If you do does temporarily disconnecting all other instances fix the issue? Changing the address of the ISY in the instance and saving should be fine, without the need to shutdown.

Link to comment

Anything in the NodeServers log when set to debug? Maybe try to restart or install another instance to see if the nodes are being created without Warnings/Errors. Also verify the nodes are shown in Polyglot, not just in ISY.

If you ISY is connected to portal we could run a remote diagnostic if your interested.

 

Link to comment

Hi @Javi, As far as I can tell the node setup in both the ISY and PG look normal.  This happens with a NS I'm developing, as well as any of the others I have installed, whether or not they're mine.

If you'd like to try the remote diagnostic I'm open to it, I am indeed connected to the Portal.

Thanks.

G

Link to comment

Do you get the same error if you invoke the command from the admin console?   If so, then it's not a UD Mobile issue for sure.

It sounds like more of a PG3 or ISY on Polisy issue.    Just to cover everything, have you restarted the ISY after installing the node server?    There are known issues with node values with UOM 25 where not everything is fully configured until ISY is rebooted.  This doesn't sound like any of those issues, but just to be sure.

Link to comment
On 2/12/2022 at 7:00 AM, glarsen said:

Hi @Javi, As far as I can tell the node setup in both the ISY and PG look normal.  This happens with a NS I'm developing, as well as any of the others I have installed, whether or not they're mine.

If you'd like to try the remote diagnostic I'm open to it, I am indeed connected to the Portal.

Thanks.

G

PM Sent

Link to comment

Archived

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


×
×
  • Create New...