This page last changed on Oct 06, 2015 by paul.cannon.

I just converted to the Professional Designer. I was setting up the z-wave integration but have had some issues. I had the z-wave devices working in the open release. The z-wave.log is currently empty so the system is not getting far enough to initialize it I believe. Here is the error that keeps repeating in the boot log.

RACE 2015-10-05 22:58:03,341 : Unable to retrieve controller identity
org.openremote.controller.exception.ConnectionException: The required password for user '<username>' was not found. Password manager error : Password for user 'org.openremote.security.PasswordManager$PasswordNotFoundException: Implementation Error: password alias '<username>' does not correspond to secret key entry in the keystore.' was not found
at org.openremote.controller.service.BeehiveCommandCheckService$BeehiveCommandChecker.connect(Unknown Source)
at org.openremote.controller.service.BeehiveCommandCheckService$BeehiveCommandChecker.httpRequest(Unknown Source)
at org.openremote.controller.service.BeehiveCommandCheckService$BeehiveCommandChecker.httpPost(Unknown Source)
at org.openremote.controller.service.BeehiveCommandCheckService$BeehiveCommandChecker.getControllerIdentity(Unknown Source)
at org.openremote.controller.service.BeehiveCommandCheckService$BeehiveCommandChecker.getRemoteCommandService(Unknown Source)
at org.openremote.controller.service.BeehiveCommandCheckService$BeehiveCommandChecker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:744)

I feel this is caused due to having the opensource version and then installing the new version. Not sure what to clean up to fix this though.

I had the same problem with a Pro-beta version. There I had to install the JCE (Java Cryptography Extension) package for my Java version. That helped.
The problem occured again for me with the Pro 1.2.0 release. I did install JCE, but this time it did not cure the problem. I wrote to Eric about this a couple of weeks ago, and again a two days ago. No response yet.

In my last mail I asked explicitly how to stop my controller from connecting back to Beehive, since I don't think I do need that.

Posted by pz1 at Oct 06, 2015 12:43

I am having the same issue with the pro release, have not found a solution.

Posted by drewscm at Oct 06, 2015 12:58

Maybe its specific to our setup

I am runningon a Rasberry Pi 2 (java 8)

Posted by paul.cannon at Oct 06, 2015 13:44

@Paul
Pro version 1.2.0 ?

Posted by pz1 at Oct 06, 2015 13:51

Yes latest version

Posted by paul.cannon at Oct 06, 2015 14:02

Can you guys go to the controller folder (under webapps) and remove the files .user and .keystore ?
Then do a sync with the online designer again.

There should be something addressing that in Pro 1.3.0 release and I'll post a more detailed explanation then.

Posted by ebariaux at Oct 15, 2015 09:38

OK, done. Do you have a release date for 1.3?
edit: The messages no longer occur in the logs

Posted by pz1 at Oct 15, 2015 09:50

Pro 1.3.0 is released.

Posted by ebariaux at Oct 16, 2015 08:36

I now get these messsages in my boot.log

DEBUG 2015-10-18 14:07:44,340 : Connecting user '<username>' to 'https://designer.openremote.com/ccs/rest/commands/301' 
  Connection Timeout : 15,000 
  Response Timeout : 10,000
TRACE 2015-10-18 14:07:44,541 : Remote command check waiting for next connection attempt in 30,000 ms...
TRACE 2015-10-18 14:07:44,541 : Remote command check waiting for next connection attempt in 30,000 ms...

How can I block these call backs? I don't think I need those

Posted by pz1 at Oct 18, 2015 13:12

Check the config.properties file and look for the controller.performBeehiveSyncing parameter.
Setting it to false should stop communication with Beehive.

Posted by ebariaux at Oct 19, 2015 13:37

I did edit webapps\controller\WEB-INF\classes\config.properties to:

#Should the controller announce himself and discovered devices to Beehive
controller.performBeehiveSyncing=false

Stopped and started controller on my Synology box. Unfortunately still getting the same messages.
update Even a restart of my Synology box did not change the situation

Posted by pz1 at Oct 19, 2015 16:11

I'll look into that.

In the meantime, maybe try setting the remote.command.request.interval to a big value, so e.g. 12h instead of 30s

Posted by ebariaux at Oct 28, 2015 07:53

I'll look into that.

Thanks

In the meantime, maybe try setting the remote.command.request.interval to a big value, so e.g. 12h instead of 30s

My configuration is now

remote.command.service.uri=https://designer.openremote.com/ccs/rest
remote.command.request.interval = 12h
remote.command.connection.timeout = 15s
remote.command.response.timeout = 10s

Strange, nothing changed! Even not after a complete reboot of the Synology server which hosts my OpenRemote controller.

Posted by pz1 at Oct 28, 2015 12:56

Doubled check and controller.performBeehiveSyncing is NOT taken into account for that specific call. Need to review implementation of that bit anyway.

Regarding remote.command.request.interval parameter, only ms, s and m are supported as units. Can you try changing the value to 720m instead ?

Posted by ebariaux at Oct 29, 2015 10:57

Can you try changing the value to 720m instead

It looks like that one is going to work

TRACE 2015-10-29 12:04:55,705 : Remote command check waiting for next connection attempt in 43,200,000 ms...

Thanks

Posted by pz1 at Oct 29, 2015 11:08

I don't know if this helps you guys find a solution....

I loaded Java 1.8 with security patch into my Pro Controller and the identity error stopped instantly.

But so did the Drools.

So I'm back to Java 1.6, with the security patch.

Now I have working Drools and the constant identity error.

Posted by mdar at Nov 16, 2015 20:29
Document generated by Confluence on Jun 05, 2016 09:34