Comfigurator 2.9.13 Beta

[juwi_uk]

In the known bugs for 2.9.13 you say \"5. Sensor Responses are not Written to Comfort\".

Is there any workaround for this right now so you can write them somehow to Comfort or do Sensor Responses just not work at the moment, period? I tried Selective Write too as this has a checkbox for Sensor Responses but that didnt seem to work either.

J

[juwi_uk]

I\'ve seen some symptoms like Wexfordman today where Responses contain the wrong Actions but they seemed to be ones (not created by myself) that came in with the original template I used way back to create my solution. Nonetheless they\'ve only corrupted someway along the betas.

I only noticed today when a couple showed as red in the list and when I investigated these they only showed \"Do\";  where the rest of the statements went is a  mystery.  I then looked at others and saw some strange effects like Smartfit commands showing up in IR responses etc.    The ones I\'ve created though look fine.

Using \"fix all responses\" too by the way as you suggested.

[juwi_uk]

By way of an enhancement request it would be nice if we could block select items in areas such as responses lists so you can do bulk actions where appropriate; ie delete.

Comfigurator decided to do a funny on me today and create lots of responses past 1023 which it then showed as invalid (red).  Deleting each one individually was a laborious pain.

J

[slychiu]

In the known bugs for 2.9.13 you say \"5. Sensor Responses are not Written to Comfort\". Is there any workaround for this right now so you can write them somehow to Comfort or do Sensor Responses just not work at the moment, period? I tried Selective Write too as this has a checkbox for Sensor Responses but that didnt seem to work either.

You can enter the Locations manually as a workaround until the next version
In the bottom left of the screen, you will see eg
(1852)= 0,1
This means that the value 0 should be written to Location 1852 and 1 to Location 1853
Go to Location Menu in Engineer Menu 7,4,1, \"enter location and # key\", enter the location eg 1852#. Keypad says the current value eg 0
Enter the new value 0#
Then enter the next Location eg 1853# and the new value into that

Needless to say, be careful when doing this, not to enter the wrong value or enter the wrong location

[slychiu]

Comfigurator decided to do a funny on me today and create lots of responses past 1023 which it then showed as invalid (red). Deleting each one individually was a laborious pain.

Do you know how you created response past 1023? It should not allow that

[slychiu]

I\'ve seen some symptoms like Wexfordman today where Responses contain the wrong Actions but they seemed to be ones (not created by myself) that came in with the original template I used way back to create my solution. Nonetheless they\'ve only corrupted someway along the betas. I only noticed today when a couple showed as red in the list and when I investigated these they only showed \"Do\"; where the rest of the statements went is a mystery. I then looked at others and saw some strange effects like Smartfit commands showing up in IR responses etc. The ones I\'ve created though look fine. Using \"fix all responses\" too by the way as you suggested.

The bug is when you ADD a response, it uses Response 1 which pushes the other Response numbers up, eg Response 2 becomes 3, 3 becomes 4 etc
In the new Response if it has a DO Response, that Response number references the old Response number before it was pushed up, eg Do Response 3 actually ends up as Do Response 2
Hence Do Response will reference the Response number which is numbered before the one that you need

[wexfordman]

So, I\'m not going mad then   I know I can fix responses, but will this work if I still have to ADD responses ? Is there a quick fix for this ?

Thanks,
Eamon

[slychiu]

When you ADD a response, make sure that all other Responses are fixed so that if you have DO Response actions, the Response number is not changed by the new Response
When you Edit a Response and add new actions, this causes the Response to be unfixed. When you complete editing FIX the response again
This should prevent any problems

[juwi_uk]

Yep it\'s really easy to go past 1023.

The reason is because I\'ve now used fix all responses as you recommended to wexfordman.

If you say have 950 responses and you edit response 200 (Response Wizard), when that saves it\'ll renumber to 951 (presumably because 200 is locked somehow);  it\'s always done that though hasnt it.  So extend that up if you already have 1023 responses it\'ll create 1024, 1025 etc etc as you create new responses.

If in the above example I hadnt fixed all responses then when I edit response 200 the Actions go against response 200!!

So having to remember to manually \"unfix all responses\" then do my editing then \"fix all responses again\"

J


{update: Oh I\'ve just read your reply to wexfordman so I guess it\'s catch 22 then as unlocking before edit sounds worse thing to do as it messes up DO\'s}

[juwi_uk]

Yeah,  let us know as soon as there\'s a 2.9.14 or whatever that fixes...