Jorge Schrauwen

Having the accessories remember the last state they were in would be a great addition. Currently I do this by using a persistent node in front of them to save...

Is this something that will eventually be tacked? If so I will leave my horrible persistant nodes in place. While driving today I though of a way better way to...

I see two 'clean' solutions for this. Option 1, add a checkbox called `persist` to the service node. When this is set, the values are store everytime they are update...

I guess option 2 would replace the current textbox to set default values. (Keeping this backwards compatibly should be possible if you parse the json in that field and use...

Well that would make it even easier to keep backwards compatibility!

Something like: ``` .----------------.---------.---------.--------. | characteristic | restore | default | action | +----------------+---------+---------+--------+ | Active | [x] | (true) | {-} | | CurrentTemp | [ ] | (25...

Maybe also add a to colomn that lists the type of the characteristic? As there seem to be a few like book, unint8, ...

> List for information or choice? > If second then we can put value in characteristics properties as in the 0.5 > > Sent with [GitHawk](http://githawk.com) Just an informational field...

@iRonin I'm using this node https://flows.nodered.org/node/node-red-contrib-persist to store a copy of all the types of input I send to the homekit service I then trigger the restore of it at...

I think the concept still looks pretty spot on.