S_HVAC device on vera doesnt set set point to arduino

[korttoma]

@petewill yeah it seems like the GW was completely frozen so i it was not window cover related. I think it froze from the commands I tried to send to the heater (I think the version of the GW is 1.5 so I'm not sure if the HVAC device is handled). I was looking in to updating my GW yesterday but I could not get the 1.5.4 GW to compile using codebender.

Did you already build the thermostat device?

I was thinking should it be presented as HVAC device or is it stil ok to use HEATER like in my example. Hocking up some serial logging to my live thermostat is not something I'm prepared to do, I usually do debugging like this on a smal system at work but I will not have access to this till next week.

[petewill]

@korttoma

I was looking in to updating my GW yesterday but I could not get the 1.5.4 GW to compile using codebender.

Hmm. I always use the arduino IDE and download the code form Github so I'm not sure about this one.

Did you already build the thermostat device?

It is currently a work in process. I have an A/C device as well so I'm doing quite a bit of coding for that. I am using the HVAC device instead of the heater device. Heater should still work though I would think.

[korttoma]

I have been hapily using codebender for the last 2 years so my IDE vad on v. 1.0.5 witch did not compile either. Updated IDE to 1.6.2 now and it compiles. Maybe I can find time to do the update to night or tomorrow.

[korttoma]

@petewill I managed to get my hands on the log file from the VeraPlus when trying to send setpoint value. It seems like the HEATER device is not working and gives the "No implementation" Error.

08	03/10/16 12:27:26.352	JobHandler_LuaUPnP::HandleActionRequest device: 44 service: urn:upnp-org:serviceId:TemperatureSetpoint1 action: SetCurrentSetpoint <0x71f83520>
08	03/10/16 12:27:26.355	JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=44 <0x71f83520>
08	03/10/16 12:27:26.356	JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:TemperatureSetpoint1 <0x71f83520>
08	03/10/16 12:27:26.356	JobHandler_LuaUPnP::HandleActionRequest argument action=SetCurrentSetpoint <0x71f83520>
08	03/10/16 12:27:26.356	JobHandler_LuaUPnP::HandleActionRequest argument NewCurrentSetpoint=72.5 <0x71f83520>
08	03/10/16 12:27:26.356	JobHandler_LuaUPnP::HandleActionRequest argument rand=0.4705214786808938 <0x71f83520>
02	03/10/16 12:27:26.357	Device_LuaUPnP::HandleActionRequest 44 none of the 1 implementations handled it <0x71f83520>
02	03/10/16 12:27:26.357	JobHandler_LuaUPnP::RunAction device 44 action urn:upnp-org:serviceId:TemperatureSetpoint1/SetCurrentSetpoint failed with 501/No implementation <0x71f83520>

fyi, for this test I did not have your latest implemented fix for the HVAC devcie but I guess that does not matter.

How is your setup coming along?

btw, I'm working on updating my old Veralite to UI7 so that I can have a separate test system but the update just do not seem to want to work, I requested Vera support to do it for me now so I just have to wait until they get to it.

[petewill]

@korttoma
Hmm. This is getting beyond my ability. Are you on 1.5 on your gateway and the sensor now? Can you test with the fix I submitted? It actually could make a difference because the mode states are used by both the Header device and the HVAC device.

If you increase the temp at your thermostat does Vera update?

I am still on UI5 so maybe that is part of the problem?

My project is at a standstill for the moment. I hope to resume it soon but life is getting in the way :)

[korttoma]

@petewill
I now have 1.5.4 on both the GW and heater device but this does not matter since the command newer leves the Vera. I'm sure I will be able to get this working but I need to get my Veralite updated first so I can have a proper test system. Yes UI7 is part of the problem since UI5 worked fine for me to (I think something related to the used SetPoint variables were changed). The current setpoint in the device is reported to Vera under the Variable "CurrentSetpoint Heat" so this part looks fine.

Yeah, sometimes life gets in the way but that is OK ;)

[korttoma]

I finally got my Veralite updated to UI7 so I could take a look at this and I can now send setpoint value to my heater device.

Here is the additions I made to I_Arduino1.xml

<action>
      	<serviceId>urn:upnp-org:serviceId:TemperatureSetpoint1</serviceId>
      	<name>SetCurrentSetpoint</name>
      	<job>
      		if (p ~= nil) then p.Setpoint(lul_device, lul_settings.NewCurrentSetpoint)  end
  			return 4,0
  		</job>
    </action>

And here is what I added to L_Arduino.lua

function Setpoint(device, NewCurrentSetpoint)
	sendCommand(luup.devices[device].id,"HVAC_SETPOINT_HEAT",NewCurrentSetpoint)
end

Unfortunately if I change the setpoint locally on the heater device I do not get the new value to the device in the vera dashboard since the value is reported to the variable "CurrentSetpoint Heat" instead of "CurrentSetpoint".

Anyhow, I'm gona try the HVAC device type to see how it performs as comparison.

[korttoma]

@petewill I tried to add my changes to github but I could not figure out how. I get "Failed to sync this branch" when I tried to sync what I committed. I have not contributed anything for 2 years so I don't remember how.

[petewill]

@korttoma Glad you got it working!

Unfortunately I can't offer much help with GitHub. I don't use it enough to have the process memorized. It's always trial and error for me too. Did you sync with the UI7 branch before you tried to upload your changes? Sorry I can't be more help...

[korttoma]

finally managed to work out the GitHub part, I had to update the desktop software and remove the 2 year old project I had there, I stil find it quite confusing.