[SOLVED] CT30 Thermostat SetCool Reverting? (due to UoM QuantityType vs. DecimalType)

[POB21 (Paul O)]

Any help would be appreciated, I hope it’s something simple. I have two of these thermostats (CT30), and both started exhibiting the same issue - SetCool commands don’t take affect on the thermostat.

Example: Thermostat says 75F, I will change the SetPoint to 72F, The temperature on the thermostat never changes but the network activity icon blinks, next polling period OH receives a command to change the SetCool back to 75F. Again, the actual temp on the thermostat never changed.

This was working at one time, which is strange. Current temp channels and FAN channels are working fine. I can toggle the HVAC fans on and off without issue. Again, i feel I am missing something simple. This started after loading the latest refactoring binding and re-adding all of my things. Scale settings correctly report Fahrenheit in HABmin and PaperUI. Because I’m using the refactoring dev binding, I thought about posting this there, but on the chance it was something unrelated, I started a new topic - moderators feel free to move as needed. Thanks to anyone who can help. Items, Sitemaps and logs below for reference:

Setpoint item=upstairs_setcool
               Setpoint item=downstairs_setcool
               Setpoint item=upstairs_setheat
               Setpoint item=downstairs_setheat
               Selection item=downstairs_fan label="Downstairs HVAC Fan" mappings=[0="AUTO", 1="ON"]
               Selection item=upstairs_fan label="Upstairs HVAC Fan" mappings=[0="AUTO", 1="ON"]

Number upstairs_setcool "Upstairs Set Cool Temp. [%.0f F]" <temperature_cold> {channel="zwave:device:512:node36:thermostat_setpoint_cooling"}

Number upstairs_setheat "Upstairs Set Heat Temp. [%.0f F]" <temperature> {channel="zwave:device:512:node36:thermostat_setpoint_heating"}

Number downstairs_fan "Downstairs HVAC Fan" <fan> {channel="zwave:device:512:node8:thermostat_fanmode"}

Number downstairs_temp "Downstairs Temp. [%.0f F]" <temperature> [ "CurrentTemperature" ] {channel="zwave:device:512:node8:sensor_temperature"}

Number downstairs_setcool "Downstairs Set Cool Temp. [%.0f F]" <temperature_cold> [ "TargetTemperature" ] {channel="zwave:device:512:node8:thermostat_setpoint_cooling"}

events.log (the first line was initiated by me, the second was not)

2018-08-22 09:55:16.548 [vent.ItemStateChangedEvent] - upstairs_setcool changed from 76 to 73
2018-08-22 09:56:21.899 [vent.ItemStateChangedEvent] - upstairs_setcool changed from 73 to 76

[POB21 (Paul O)]

I’ve since tried clearing the cache, excluding and re-including the thermostat and completely reloading the JAR file to no avail.

[chris (Chris Jackson)]

You should check the debug logs to try and find out what is happening. At the moment, you can only see that something IS happening - the debug logs should tell you WHAT is happening…

[POB21 (Paul O)]

Roger that. Thank you for your help. Below is what resulted immediately following a setpoint command - Note that since I’ve done a re-inclusion, the node is now 40 (not 8 as shown in my items file). Looks like the problem is related to the ‘Unknown Channel’ entry? The channel shows to be correctly linked in HABmin and PaperUI.

[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Command received zwave:device:512:node40:thermostat_setpoint_cooling --> 70
2018-08-22 12:17:33.150 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Command for unknown channel zwave:device:512:node40:thermostat_setpoint_cooling with DecimalType
2018-08-22 12:17:51.383 [WARN ] [io.openhabcloud.internal.CloudClient] - Jetty request 12878868 failed: null
2018-08-22 12:18:07.143 [WARN ] [io.openhabcloud.internal.CloudClient] - Jetty request 12878906 failed: null

Here is a snip-it from the polling session following the above:

2018-08-22 12:18:47.775 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 40: Received COMMAND_CLASS_THERMOSTAT_SETPOINT V1 THERMOSTAT_SETPOINT_REPORT
2018-08-22 12:18:47.778 [DEBUG] [.ZWaveThermostatSetpointCommandClass] - NODE 40: Thermostat Setpoint report Scale = 1
2018-08-22 12:18:47.780 [DEBUG] [.ZWaveThermostatSetpointCommandClass] - NODE 40: Thermostat Setpoint Value = 78
2018-08-22 12:18:47.783 [DEBUG] [.ZWaveThermostatSetpointCommandClass] - NODE 40: Thermostat Setpoint Report, Type Cooling (2), value = 78
2018-08-22 12:18:47.785 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Got an event from Z-Wave network: ZWaveThermostatSetpointValueEvent
2018-08-22 12:18:47.788 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_THERMOSTAT_SETPOINT, value = 78
2018-08-22 12:18:47.791 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Updating channel state zwave:device:512:node40:thermostat_setpoint_cooling to 78 °F [QuantityType]
2018-08-22 12:18:47.796 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Commands processed 1.
2018-08-22 12:18:47.801 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@15b1b12.
2018-08-22 12:18:47.803 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: Command verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@15b1b12.
2018-08-22 12:18:47.806 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 40: notifyTransactionResponse TID:439 DONE
2018-08-22 12:18:47.809 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-08-22 12:18:47.812 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1
2018-08-22 12:18:47.815 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

[chris (Chris Jackson)]

A few thoughts…

What version of OH are you running, and what version of the binding is it? (I think from the log you have the new development version of ZWave - so what is the runtime)?

The other thing to look at is if there are any error during initialisation.

When you changed to the dev binding, did you delete the thing and add it back? This version uses the UoM for setpoints.

[POB21 (Paul O)]

OH Version 2.3.0-1: Yes, I am running your latest version of the 8/18 Dev binding 2.4.0 … Did I just cast a spotlight on my noobness - Does this dev binding version require the 2.4 exp runtime?

I will look for initialization errors. Yes, I deleted all things and re-added. In the case of one of these thermostats, I even excluded / re-included.

[chris (Chris Jackson)]

@POB21

Does this dev binding version require the 2.4 exp runtime?

No - it will run with 2.3 runtime.

The development binding is found in the following thread - read the first 6 or so messages…

OH2 Z-Wave refactoring and testing... and SECURITY

The latest version of the development binding dated 8th Sep 2018 is here. Toward the end of last year I spent some time doing some initial refactoring of the ZWave binding in OH2. This focussed on rewriting the way transactions work as this is an enabler for other areas of the code. At the same time I also restructured the different layers of the binding to make things cleaner, and done some changes to support a system of autocoding the command classes directly from the Z-Wave standard which s…

[POB21 (Paul O)]

Great, Thank you! I will make the move from the 8/18 binding to the 8/23 binding when I get home this evening and report back regarding my setpoint issue. Also, I couldn’t find any initialization errors when I reviewed the log (not to say they weren’t there beyond a shadow of a doubt… just saying that I didn’t find them).

As an aside, is it expected that devices using security require re-inclusion when changing to a new version of the dev binding? My locks generally don’t work when the things are re-added, even though PaperUI and HABmin report ‘using security’. But re-including them does the trick.

[chris (Chris Jackson)]

@POB21

is it expected that devices using security require re-inclusion when changing to a new version of the dev binding?

If you keep the same key, then you shouldn’t need to reinclude.

Note though that if you weren’t previously using the development binding, then security won’t have worked in the previous binding.

[POB21 (Paul O)]

I was using the previous development binding, and I seemed to have forgotten about that key along the way - Thanks for reminding me. I copied it before I deleted all Things, put it back and low & behold, I didn’t have to re-include. Stupid me…

So I have put the latest development binding ‘in service’ so-to-speak, but I’m afraid to report that my setpoint issue persists - I’m completely baffled. The same thing appears in the log:

2018-08-23 22:12:46.048 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Command received zwave:device:512:node40:thermostat_setpoint_cooling --> 72
2018-08-23 22:12:46.056 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Command for unknown channel zwave:device:512:node40:thermostat_setpoint_cooling with DecimalType

The only other questionable things I see in the log are below:

2018-08-23 21:47:38.242 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'home.sitemap'
2018-08-23 21:47:46.758 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:47:46.762 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:47:46.765 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:06.121 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:06.127 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:06.133 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:07.584 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:07.591 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:07.597 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:10.241 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:10.247 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:10.256 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:18.932 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:18.937 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:18.942 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:20.319 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:20.324 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:20.328 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:22.635 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:22.641 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:22.646 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:24.329 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:24.334 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:24.339 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:25.698 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:25.705 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:25.711 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:50.302 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:50.308 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:50.320 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:55.052 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:55.060 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:55.067 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:57.977 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:57.984 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:48:57.989 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:49:21.361 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 21:49:28.494 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:49:28.500 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:49:28.506 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:49:59.014 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:49:59.021 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:49:59.028 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:50:31.035 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:50:31.042 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:50:31.048 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:51:01.593 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:51:01.600 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:51:01.605 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:51:32.208 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:51:32.215 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item 'entry_lights' for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:51:32.220 [ERROR] [ui.internal.items.ItemUIRegistryImpl] - Cannot retrieve item for widget org.eclipse.smarthome.model.sitemap.Switch
2018-08-23 21:52:47.180 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'home.items'
2018-08-23 21:52:47.251 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:upstairs_temp in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.265 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:downstairs_temp in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.271 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:downstairs_setcool in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.278 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:downstairs_setheat in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.286 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:living_room_fan in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.298 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:master_bedroom_fan in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.306 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:front_door_lock in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.313 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:back_door_lock in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.321 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:door_announcements in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.327 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:kitchen_light in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.343 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:entry_table_outlet in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.350 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:dining_light in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.356 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:dining_room_light in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.363 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:living_room_light in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.369 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:living_room_lamp in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.377 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:fire_place_light in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.384 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:fire_place_light_color in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:52:47.393 [WARN ] [mon.registry.AbstractManagedProvider] - Could not update element with key _tags:master_bedroom_light in ManagedMetadataProviderImpl, because it does not exists.
2018-08-23 21:58:02.879 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 21:58:34.776 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 21:59:02.531 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 21:59:37.835 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:00:23.680 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:00:26.593 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:04:57.613 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:06:08.422 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:06:18.805 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$EmptySet, genericType=class java.util.Collections$EmptySet.
2018-08-23 22:06:24.642 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:06:53.911 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:06:56.766 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:07:16.944 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:07:32.003 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:09:49.927 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.
2018-08-23 22:10:21.348 [ERROR] [e.internal.WriterInterceptorExecutor] - MessageBodyWriter not found for media type=text/plain, type=class java.util.Collections$UnmodifiableCollection, genericType=class java.util.Collections$UnmodifiableCollection.

[POB21 (Paul O)]

I think I would have noticed this before, so i think this is strange and likely new. Both of the setpoints say ‘Heating’ in Habmin. They don’t appear that way in paperUI.

[POB21 (Paul O)]

So, just playing around with some options, I created a Selection element on a Sitemap, pointing to the setpoint Item:

 Selection item=downstairs_setcool mappings=[74F="74 F", 75F="75 F", 78F="78 F"]

I also performed a few tests with and without the [%.0f F] in the Item definition. This successfully sent the temperature to the thermostat! Inspecting the log, It can be seen that this value that was sent (and worked) as the F appending it. The value without the F reported by me earlier in the thread clearly weren’t working. So, my limited knowledge leaves me wondering how the value selected from the Setpoint sitemap element be combined with a simple F after it. Again, what’s odd is that this was working okay before I applied the 8/18 build. As always, thank you everyone!

[chris (Chris Jackson)]

The binding was changed a while back to use the QuantityType (ie UoM) and it seems that most of the time you’re not sending QuantityType data and this is why it’s not working. I’m not especially familiar with how this works in the UI side, so I’m not really able to answer those questions (sorry).

The degF/degC option that you see in HABmin will be removed - it’s not used any more. The units have to come from the command that you send to the binding.

I’m not sure why it says “Heating Setpoint”. In the database, the two labels for these channels are called “Setpoint (heating)” and “Setpoint (cooling)”…

[POB21 (Paul O)]

Thank you so much for helping me zero in on this! I’m not sure if what I did was appropriate, but I modified the Thing.json file and replaced the QuantityType with DecimalType for both of my thermostats. This worked!

Did I have another option? I’m just glad that I can manage my thermostats again for the time being.

[chris (Chris Jackson)]

@POB21

what’s odd is that this was working okay before I applied the 8/18 build.

Nothing has changed with this recently - the UoM changes were made a little while ago. and fixes were made to the setpoints about a month back (see the thread below). Do you know what version you used before this one?

[SOLVED] Heatit z-trm2 anyone tried it in OH2?

Is it just the state with the %unit% you added or was there something else ? I guess this could also be added in your items file? I forget why I didn’t add this when I updated the channels - there was a reason at the time, but I forget what it was now . It is always available on the first post of the dev binding thread.

@POB21

I modified the Thing.json file and replaced the QuantityType with DecimalType for both of my thermostats. This worked!

I’m not sure that I really understand what’s happening. Previously, you said that only the QuantityType were working (ie the ones that had the F on the end of the values). Now you’ve changed all the QuantityTypes to DecimalTypes?

In the binding, it only deals with QuantityType, so I guess that in the framework, something is re-converting these to QuantityType - can you check the log to see what it shows is being received in the ZWave binding (it prints a message when a command is received).

@POB21

Did I have another option?

I’m not sure to be honest, but I can say that if this is the only option, it’s not a good one . I think that there’s possibly some configuration issue with your things, but I’d like to understand what is being sent to the binding so at least we can rule that out. I went through this a while back with some others to ensure that the UoM worked ok with setpoints (as per the link above).

If we can work out what is coming into the binding at least, then we can split the problem and try and understand it…

[shady9191 (Bryan)]

Paul,

So your solution was both to change the json file to DecimalType and send 72F to the thermostat?

[POB21 (Paul O)]

Yes, I modified the type for each thermostat in the …Thing.json file. I changed:

binding:*:QuantityType

to

binding:*:DecimalType

for the entries related to the thermostat setpoints.

I believe that the command being sent to the binding is just the number, without the “F”. Were you having a similar issue?

[chris (Chris Jackson)]

I’m not sure what versions everyone here is using, but sending DecimalType with the latest binding (2.4 M4 and later) will not work (or will not work properly). I would strongly recommend to try and configure the UoM properly, and send the correct format commands - recommending something else is not likely to be a long term route to success

[shady9191 (Bryan)]

Chris, can you elaborate on “configure the UoM properly”? I don’t know what else to try here. Please see the other thread I created.

Thanks

Z-Wave - Updated to 2.4 - Lost ability to change heat and cool set points

Have two Radio Thermostat CT100 plus units. Went from 2.2.0 snapshot to 2.4.0. They poll just fine, but I can’t change the heating or cooling setpoint. I CAN change the mode. I removed one from openhab and the z-wave stick, re-added it, the problem still exists. Log is in debug, right around when I tried to change heat setpoint on Node 20: 26-Oct-2018 16:55:44.735 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 20: Command received zwave:device:16018d21b22:node20:therm…

[bigboxer23 (Matt Jones)]

When i moved to the 2.4 binding, i had to make the following changes to get it to work:
Number HeatingSetpoint "Heating Setpoint" (Climate) {channel = "zwave:device:512:node86:thermostat_setpoint_heating"} to Number:Temperature HeatingSetpoint "Heating Setpoint" (Climate) {channel = "zwave:device:512:node86:thermostat_setpoint_heating"} changed the type sent from decimal to quantity, then the command i sent went from 65 to 65.0 °F