[innogy] Update to new API 1.1 and new devices tested

Thanks a lot, but it is not working anyway.

Regards Chris

Reboot Raspi complete

Now it works. The magic step was to clean the cache (openhab-cli clean-cache) before installing the binding new.

Thanks a lot.

1 Like

I run snapshot #1771. The binding works basically but i lost the connection of the bridge last night. Had to input a new token in the morning to get it online again. Will observe if this happens again.

The variable energy_day_euro mentioned above is still always " - " after Hilbrand’s update.

BR Willi

The changes were not yet available in that snapshot.

Hello Hilbrand,

thanks for the information. Lost the connection again today and then the token field is empty and the binding requires a new token to be entered. Don’t know if this is already solved or not?

Have upgraded to snapshot #1774 and will test furthermore. The daily Euros are present now. Thanks for this fix.

BR Willi

Hi Hilbrand,

i think, i have found another (old) bug in the binding.
when you Change the value of a dimmer, (in this case from 0 to 35) the binding will set the value from 0 to 100 and then from 100 to 35.

In the debug log, you can see, that this is not coming from the api. the api changes the value correct directly to 35.

see the log?

12:01:44.546 [DEBUG] [ogysmarthome.internal.InnogyWebSocket] - innogy WebSocket onMessage() - {"sequenceNumber":87746,"type":"StateChanged","desc":"/desc/device/ISD2.RWE/1.0/capability/DimmerActuator/event/StateChanged","namespace":"CosipDevices.RWE","timestamp":"2019-12-13T11:01:44.5056720Z","source":"/capability/53ac14a9012147b6a2ec6b2d0568a11c","properties":{"dimLevel":35}}
12:01:44.548 [DEBUG] [.internal.handler.InnogyBridgeHandler] - Event no 87746 found. Type: StateChanged
12:01:44.549 [DEBUG] [.internal.handler.InnogyDeviceHandler] - onDeviceStateChanged called with device Licht Ralph/fa1cda6804af4d21aacf0573321d3d4b
12:01:44.551 [DEBUG] [.internal.handler.InnogyDeviceHandler] - ->capability:53ac14a9012147b6a2ec6b2d0568a11c (DimmerActuator/Dimmer Actuator)
12:01:44.552 [DEBUG] [.internal.handler.InnogyDeviceHandler] - Dimlevel state 35
12:01:44.553 [DEBUG] [.internal.handler.InnogyDeviceHandler] - ->capability:8642e133911e4cbb9e8ed6713ff3c1c4 (PushButtonSensor/ISD2)
12:01:44.554 [INFO ] [smarthome.event.ItemStateChangedEvent] - DS_AZ_Ralph changed from 0 to 100
12:01:44.562 [DEBUG] [.internal.handler.InnogyDeviceHandler] - Pushbutton index null count 58
12:01:44.562 [INFO ] [home.event.GroupItemStateChangedEvent] - GR_Licht_AZ changed from OFF to ON through DS_AZ_Ralph
12:01:44.563 [DEBUG] [.internal.handler.InnogyDeviceHandler] - State for PushButtonSensor is STILL NULL!! cstate-id: 8642e133911e4cbb9e8ed6713ff3c1c4, c-id: 8642e133911e4cbb9e8ed6713ff3c1c4
12:01:44.564 [INFO ] [smarthome.event.ItemStateChangedEvent] - DS_AZ_Ralph changed from 100 to 35
12:01:44.565 [INFO ] [home.event.GroupItemStateChangedEvent] - GR_Licht_OG changed from 0 to 1 through GR_Licht_AZ
12:01:44.566 [INFO ] [home.event.GroupItemStateChangedEvent] - GR_Licht changed from 0 to 1 through GR_Licht_OG

do you have an idea ?

ralph

I also lose connection almost every second/third day… the only thing that helps me in such case is to disable/enable the thing via PaperUI

Here’s what trace log looks like when i lose connection … you can see that at 12:29 i disabled and then again enabled the binding via paperui, and that’s when i started to work again… @hilbrand can you just take a look if this 404 error is handled properly in the code, as it seems that maybe innogy’s api sometimes responds with 404 and after that the binding probably doesn’t reconect to service or smth…?

2019-12-16 08:49:37.036 [DEBUG] [b.binding.innogysmarthome.internal.InnogyWebSocket] - innogy WebSocket onError() - null
2019-12-16 08:49:37.036 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - IO error: null
2019-12-16 08:49:37.037 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR)
2019-12-16 08:49:37.037 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:DiningRoomRSTRight bridge status OFFLINE
2019-12-16 08:49:37.037 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR)
2019-12-16 08:49:37.037 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:KitchenRST bridge status OFFLINE
2019-12-16 08:49:37.038 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR)
2019-12-16 08:49:37.038 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:KidsRoomRST bridge status OFFLINE
2019-12-16 08:49:37.038 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR)
2019-12-16 08:49:37.039 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR)
2019-12-16 08:49:37.039 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:BedroomRST bridge status OFFLINE
2019-12-16 08:49:37.039 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Scheduling reinitialize in 30 seconds.
2019-12-16 08:49:37.039 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR)
2019-12-16 08:49:37.039 [INFO ] [b.binding.innogysmarthome.internal.InnogyWebSocket] - Connection to innogy Webservice was closed abnormally (code: 1006). Reason: WebSocket Read EOF
2019-12-16 08:49:37.039 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:LivingRoomRST bridge status OFFLINE
2019-12-16 08:49:37.040 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Scheduling reinitialize in 30 seconds - ignored: already triggered in 29 seconds.
2019-12-16 08:49:37.040 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR)
2019-12-16 08:49:37.040 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:OfficeRST bridge status OFFLINE
2019-12-16 08:49:37.040 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:DiningRoomRSTLeft bridge status OFFLINE
2019-12-16 08:50:07.040 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Initializing innogy SmartHome client...
2019-12-16 08:50:07.040 [DEBUG] [nding.innogysmarthome.internal.client.InnogyClient] - Get innogy SmartHome status...
2019-12-16 08:50:07.293 [DEBUG] [nding.innogysmarthome.internal.client.InnogyClient] - [601] Statuscode is NOT OK: 404
2019-12-16 08:50:07.293 [TRACE] [nding.innogysmarthome.internal.client.InnogyClient] - Response error content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.294 [WARN ] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Unexcepted API error: Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

org.openhab.binding.innogysmarthome.internal.client.exception.ApiException: Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.handleResponseErrors(InnogyClient.java:262) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.request(InnogyClient.java:187) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.executeGet(InnogyClient.java:140) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.refreshStatus(InnogyClient.java:120) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.startClient(InnogyBridgeHandler.java:229) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
2019-12-16 08:50:07.300 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Scheduling reinitialize in 30 seconds - ignored: already triggered in 0 seconds.
2019-12-16 08:50:07.300 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.300 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:DiningRoomRSTRight bridge status OFFLINE
2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:DiningRoomRSTLeft bridge status OFFLINE
2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:KitchenRST bridge status OFFLINE
2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:KidsRoomRST bridge status OFFLINE
2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:BedroomRST bridge status OFFLINE
2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:LivingRoomRST bridge status OFFLINE
2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - bridgeStatusChanged OFFLINE (COMMUNICATION_ERROR): Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

2019-12-16 08:50:07.301 [DEBUG] [nogysmarthome.internal.handler.InnogyDeviceHandler] - initializeThing thing innogysmarthome:RST:ishbridge:OfficeRST bridge status OFFLINE
2019-12-16 08:50:07.300 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Error initializing innogy SmartHome client.
org.openhab.binding.innogysmarthome.internal.client.exception.ApiException: Invalid JSON syntax in error response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Not Found</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Not Found</h2>
<hr><p>HTTP Error 404. The requested resource is not found.</p>
</BODY></HTML>

	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.handleResponseErrors(InnogyClient.java:262) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.request(InnogyClient.java:187) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.executeGet(InnogyClient.java:140) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.client.InnogyClient.refreshStatus(InnogyClient.java:120) ~[?:?]
	at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.startClient(InnogyBridgeHandler.java:229) ~[?:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]
2019-12-16 12:29:52.064 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Disposing innogy SmartHome bridge handler 'ishbridge'
2019-12-16 12:29:52.067 [TRACE] [b.binding.innogysmarthome.internal.InnogyWebSocket] - Stopping websocket ignored - was not running.
2019-12-16 12:29:52.067 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - innogy SmartHome bridge handler shut down.
2019-12-16 12:29:52.073 [DEBUG] [org.openhab.binding.innogysmarthome               ] - ServiceEvent UNREGISTERING - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=482, service.bundleid=191, service.scope=singleton} - org.openhab.binding.innogysmarthome
2019-12-16 12:29:53.683 [DEBUG] [org.openhab.binding.innogysmarthome               ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.discovery.DiscoveryService}={service.id=483, service.bundleid=191, service.scope=singleton} - org.openhab.binding.innogysmarthome
2019-12-16 12:29:53.685 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Initializing innogy SmartHome BridgeHandler...
2019-12-16 12:29:53.686 [DEBUG] [nogysmarthome.internal.handler.InnogyBridgeHandler] - Initializing innogy SmartHome client...
2019-12-16 12:29:53.686 [DEBUG] [nding.innogysmarthome.internal.client.InnogyClient] - Get innogy SmartHome status...
2019-12-16 12:29:57.612 [DEBUG] [nding.innogysmarthome.internal.client.InnogyClient] - [1] Statuscode is OK.

I Have The Problem since today upgrade to OpenHAB 2.5 that the Operation Mode in Climated Actors doesn’t work. Have you the same Problem? Only in the iOS App there’s an arrow to a empty side. In the Basic UI it works, but no Map Transformation.

@hilbrand: Which Binding should we install in OH 2.5? The Innogy Binding in Paper UI or latest from Github?

Thx
Tobi

I guess the Dimmer Item operates from 0 to 100 and that is what is passed, but when the api only goes to 35 it will report that value back when it’s state is retrieved. But this is just guessing. I’m currently short on time so can you make a issue on openhab2-addons GitHub repository and tag me in the description so this doesn’t get buried here in this thread and I can have a look at it later on.

What version of the binding are you running? The latest version should recover better from errors. But it still might miss this variant. If you’re running the latest or the one in the 2.5 release and still have this problem can you make a issue on openhab2-addons GitHub repository and tag me in the description so this doesn’t get buried here in this thread and I can have a look at it later on as I’m currently short on time.

The version on GitHub and in the 2.5 release can be considered the same. So if you run 2.5 release it should not be different from the binding on GitHub. If there is different behavior from different apps this might indicate a problem with that app. Based on your information it’s not clear if it doesn’t work at all or if it doesn’t work for specific apps. You can run with debug log level to see what the binding does and if there is a problem or if there is a problem with an app.

@hilbrand: ok - i have created a new issue. ralph

1 Like

Hi Hilbrand,

have tested snapshot #1774 furthermore but it looses connection every couple of days and doesn’t reconnect without pulling a new token. This behaviour is new. Never lost connection since a have Oliver’s binding (at least 2 years). There is still something going on.

Best regards,

Willi

Can you run it with log level debug on the binding (org.openhab.binding.innogysmarthome) so it will give more information why it looses connection. This should give a hint on how to fix this. You can send the log via direct message if you prefer.

Hi @Hilbrand,

in the actual beta version of the binding the low battery-channels are not working correct. if a device sends a low battery-state, then the bridge is going offline…

in a previous version of the binding, this was tested correctly by me and told to Ollie.
Can you take a look on this ?

the debug log is showing the following error:

22:49:06.097 [DEBUG] [.internal.handler.InnogyBridgeHandler] - Error with Event: null
java.lang.NullPointerException: null
        at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.handleNewMessageReceivedEvent(InnogyBridgeHandler.java:655) ~[bundleFile:?]
        at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.onEvent(InnogyBridgeHandler.java:533) [bundleFile:?]
        at org.openhab.binding.innogysmarthome.internal.InnogyWebSocket.onMessage(InnogyWebSocket.java:141) [bundleFile:?]
        at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_231]
        at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_231]
        at org.eclipse.jetty.websocket.common.events.annotated.CallableMethod.call(CallableMethod.java:70) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.annotated.OptionalSessionCallableMethod.call(OptionalSessionCallableMethod.java:72) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.JettyAnnotatedEventDriver.onTextMessage(JettyAnnotatedEventDriver.java:251) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:65) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.JettyAnnotatedEventDriver.onTextFrame(JettyAnnotatedEventDriver.java:243) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:150) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:321) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:202) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:226) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.Parser.parseSingleFrame(Parser.java:262) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:582) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:441) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:428) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:426) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:320) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:158) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918) [bundleFile:9.4.20.v20190813]
        at java.lang.Thread.run(Unknown Source) [?:1.8.0_231]
22:49:06.102 [DEBUG] [.internal.handler.InnogyBridgeHandler] - Unknown exception
java.lang.NullPointerException: null
        at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.handleNewMessageReceivedEvent(InnogyBridgeHandler.java:655) [bundleFile:?]
        at org.openhab.binding.innogysmarthome.internal.handler.InnogyBridgeHandler.onEvent(InnogyBridgeHandler.java:533) [bundleFile:?]
        at org.openhab.binding.innogysmarthome.internal.InnogyWebSocket.onMessage(InnogyWebSocket.java:141) [bundleFile:?]
        at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.8.0_231]
        at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_231]
        at org.eclipse.jetty.websocket.common.events.annotated.CallableMethod.call(CallableMethod.java:70) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.annotated.OptionalSessionCallableMethod.call(OptionalSessionCallableMethod.java:72) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.JettyAnnotatedEventDriver.onTextMessage(JettyAnnotatedEventDriver.java:251) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:65) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.JettyAnnotatedEventDriver.onTextFrame(JettyAnnotatedEventDriver.java:243) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:150) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:321) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:202) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:226) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.Parser.parseSingleFrame(Parser.java:262) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:582) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:441) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:428) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:426) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:320) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:158) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782) [bundleFile:9.4.20.v20190813]
        at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918) [bundleFile:9.4.20.v20190813]
        at java.lang.Thread.run(Unknown Source) [?:1.8.0_231]

thanks
ralph

1 Like

Hello, does the Innogy api.services for getting a auth-code doesn’t work anymore?

Best greetings. Paul-Joachim Haucke

Hello, I am wondering that my RST2 (new thermostat) does not show the battery status as an RST (old one) does. During startup, an RST reports to the log file

/var/log/openhab2/events.log:2020-03-21 19:01:06.018 [.ItemChannelLinkAddedEvent] - Link 'FF_Bedroom2_RST_LoBatt-innogysmarthome:RST:SMARTHOME04:f61a4d563c32472598727361c79abb5d:battery_low' has been added.
/var/log/openhab2/events.log:2020-03-21 19:02:50.853 [vent.ItemStateChangedEvent] - FF_Bedroom2_RST_LoBatt changed from NULL to OFF

whereas the RST2 does not get any ItemStateChangesEvent:

/var/log/openhab2/events.log:2020-03-21 19:01:05.976 [.ItemChannelLinkAddedEvent] - Link 'FF_Bedroom1_RST_LoBatt-innogysmarthome:RST2:SMARTHOME04:0168edd3b979409a9479ad5b1eb737eb:battery_low' has been added.

Its state remains NULL all the time.
Anybody else experiencing this behavior? Or can somebody confirm it’s working correctly?

Unfortunately, battery status is not shown on https://home.innogy-smarthome.de; only a message when batteries go low… I am using the “old” Smart Home Controller SHC 1.0.

Best regards, Rupert

That is outdated. Have a look at updated doc: https://github.com/openhab/openhab-addons/pull/6998

Sorry, I replied to pjhaucke’s post rather than opening a new question in the thread. Sorry!
-Rupert

Hi Rupert, it’s a problem of the device firmware.
The RST2 doesn’t report the battery state.