Thanks for the info guys. This will be fixed in the next release. This was a bug on my part by not handling the device pending/error/success state.
1 Like
Thanks a lot to everybody. I look forward for the next release
Just a last question, When do you plan to launch yhe next release?
Thanks a lot
In a few days. I was hoping to begin publishing later today but I’m not certain if it’ll be ready or not. I’ll let you know.
Was the fix published ?
Is there a change log we can view?
I have updated Designer to Version 3.12.0.0 and my Android app is set to auto update.
I still have the issue we described in this thread.
Many Thanks
I have tryed to download 3.12.0.0 version, but what I get is an .msi for installation of 3.9.9.0 version, that when trying to install gives an error:
“Pídele al desarrollador un nuevo paquete de la aplicación. Este paquete puede entrar en conflicto con un paquete instalado previamente, depende de cosas no instaladas aquí (dependencias del paquete) o está hecho para una arquitectura diferente (0x80073CF3)” (I’m sorry, it is in spanish).
I have unistalled rthe previous version in the computer, and the proble remais, so, I am now without the posibility to install any version of the HR designer.
What I have done wrong?
Yes, this should have been fixed in 3.12.0.
@cw-kid Would you mind letting me connect to your system so I can see exactly what is happening in real-time?
@APPA You do not need the Designer to see if this release fixes the issue for you. Can you please update your phones & tablets to 3.12.0 & see what happens? Does it still temporarily show the new requested setpoint & then bounce back to the old after a couple seconds?
That error you are seeing says there is a conflict with an existing install. Double-check & make sure your previous install has been removed. Try rebooting your PC also.
Regarding version, the installer version & actual software version aren’t in sync right now. Installer version 3.9.9.0 is Designer version 3.12.0.0. Ideally, I would like to keep them in sync but there is currently a weird MSIX bug in the latest Windows 10 version.
Yes I’m sure we could arrange that.
Just trying it again now.
My Thermostat was set to 10.
I used the up arrow and changed it to 23.5
I did say 23.5 for longer than before maybe 20 seconds or so.
Now it says 10 again.
When my Thermostat has woken up to accept the command and changes to 23.5, then Home Remote Android app also then changes back to 23.5.
You want to Team Viewer on to my laptop or something ?
Cheers.
Finally, I have done it. The problem was that the previous version was not uninstalled completely. Now I will try to see what happens with the thermostat.
@cw-kid Send me your project if you could. My plan was to open it on my PC & connect with my debugger. The Home Remote uses dataversion & loadtime query parameters which filters those results. We can’t really replicate that process in a web browser.
Just changed thermostat from 23.5 to 10.
Stays on 10 for about 30 seconds, then goes. Back to 23.5.
Thermostat wakes up later and HR app then changed to 18 then to 13 then to 10 very quickly.
OK. I see what’s happening. The next release will have this fixed for good, hopefully. I just tested with @cw-kid’s thermostat & the change I made a little bit ago appears to be working well.
Here’s why it’s still happening with the changes I made last week. As I said earlier, The Home Remote isn’t really polling in a traditional sense. It’s monitoring events / changes. Below are all of the thermostat events that happened after I changed the setpoint to 15. Initially, it’ll post a “Pending” state of 2 which is fine. That’s what we expect to see after sending a new setpoint. However, a short time after that we begin seeing a few events with a state of ‘-1’. I was treating ‘-1’ as a completed state which would update the state of the setpoints to match the JSON.
What the next release will do is treat ‘-1’ as another possible “Pending” state. It won’t begin using those values in the JSON until we get either a completed state of ‘4’, an error state of ‘3’, or after 15 minutes. After 15 minutes it’ll just show what’s in JSON, regardless of what the state is.
Changing setpoint to 15 at 11/8/2020 9:42:58 PM
Event at 11/8/2020 9:43:08 PM
{
"altid": "57",
"id": "189",
"subcategory": "2",
"room": "8",
"parent": "1",
"mode": "HeatOn",
"commands": "heater_setpoint",
"configured": "1",
"commFailure": "0",
"batterylevel": "40",
"temperature": "18.10",
"setpoint": "14.00",
"heat": "14.00",
"cool": "14.00",
"state": "2",
"comment": "Thermostat: Waiting for wakeup to send commands"
}
Event at 11/8/2020 9:43:21 PM
{
"altid": "57",
"id": "189",
"subcategory": "2",
"room": "8",
"parent": "1",
"mode": "HeatOn",
"commands": "heater_setpoint",
"configured": "1",
"commFailure": "0",
"batterylevel": "40",
"temperature": "18.10",
"setpoint": "14.00",
"heat": "14.00",
"cool": "14.00",
"state": "2",
"comment": "Thermostat: Waiting for wakeup to send commands"
}
Event at 11/8/2020 9:43:34 PM
{
"altid": "57",
"id": "189",
"subcategory": "2",
"room": "8",
"parent": "1",
"mode": "HeatOn",
"commands": "heater_setpoint",
"configured": "1",
"commFailure": "0",
"batterylevel": "40",
"temperature": "18.10",
"setpoint": "14.00",
"heat": "14.00",
"cool": "14.00",
"state": "-1",
"comment": ""
}
Event at 11/8/2020 9:46:16 PM
{
"altid": "57",
"id": "189",
"subcategory": "2",
"room": "8",
"parent": "1",
"mode": "HeatOn",
"commands": "heater_setpoint",
"configured": "1",
"commFailure": "0",
"batterylevel": "40",
"temperature": "18.10",
"setpoint": "14.00",
"heat": "14.00",
"cool": "14.00",
"state": "-1",
"comment": ""
}
Event at 11/8/2020 9:47:48 PM
{
"altid": "57",
"id": "189",
"subcategory": "2",
"room": "8",
"parent": "1",
"mode": "HeatOn",
"commands": "heater_setpoint",
"configured": "1",
"commFailure": "0",
"batterylevel": "40",
"temperature": "18.10",
"setpoint": "15.00",
"heat": "15.00",
"cool": "15.00",
"state": "4",
"comment": "Thermostat: SUCCESS! Transmit was OK"
}
That’s great thank you for looking further in to the issue.
hello,
I have investigating further the behaviour of the thermostat with the Danfoss radiator head, and I ve found a couple of things, that may be will help you:
1.- I have the thermostat and the radiator head in 25º. When I give two clicks in a button to increase in 1º steps, HR display jumps to 25º, stay there for a while, and then go back to 23º. If now I look at the variables in VERA, CurrentSetpoint and CurrentSetpointHeat show 25, and SetpointTarget 23. If you wait for 10 or 15 minutes, all the values go to 23, and HR displys alss 23.
2.- If instead os using 1º steps, I change to 0.5º steps, supported by the Danfoss unit, when going from 23 to 25, I found the following valus shown in HR:
1st clik: 23
2nd click: 235.5
3d click: 2355.5
4d click: 23555.5
Hope with will be of help
Regards
@APPA Both of your issues will be fixed in the next release.
#1 is most likely related to the same issue I reported a couple days ago.
#2 is a new bug I wasn’t aware of until now. I have found & fixed the issue. It’ll work correctly in the next release.
1 Like
Thanks a lot. I`ll wait for the next release.
The 3.12.1 release with the changes is available to test.
Hi
I’ve just tested this and it is working now with only one issue.
If you are in the Home Remote app and you change your thermostat from say 10 to 23, now the app will remain displaying 23.
You can leave the thermostat device and navigate around to other areas of the home remote app and then go back in to the thermostat device and its still at 23 setpoint, even though the thermostat is still waiting to wake up to accept the new command.
So this works and it is fixed.
However if you switch to another Android app on your phone and then switch back to Home Remote, then the setpoint value goes back to the current / old value of 10.
Thanks
Correct, switching apps will force a full refresh & show the value in the JSON. I’m not sure if I want to change that behavior.
1 Like
I have checked the new version, and the opeation is OK for me.
Thanks a lot.
1 Like