Kimmo Huoman

@Ethal Manufacturer ID is already defined in my current version, defaulting to None. @romor There will be those functions, as `Storage.save_device(Device)`, `device = Storage.load_device(device_id)`, `[devices] = Storage.get_devices()` and `Storage.remove_device(device_id)`. So...

Hmm, I'm struggling a bit with this. The original proposal saved the data as hex strings. However, this is a compromise for speed, as more conversions would be required (hex...

I would also like to store it as an integer, but unfortunately integer keys aren't allowed in JSON ;)

Sorry for the late reply, been extremely busy. `transmitter_offset` is used, as it's easier (and faster) to handle with the related lists (`used_transmitter_offsets` etc). I might however remove the `used_transmitter_offsets`...

My current storage with the latest commits in storage-branch looks like this: ``` json { "used_transmitter_offsets": [], "storage_version": 1, "devices": { "01:81:B7:44": { "eep_type": 5, "eep_rorg": 165, "eep_func": 2, "manufacturer_id":...

I have (at least so far) left this out on purpose, as in my use-case I have implemented a similar solution in elsewhere in my code. Of course, it wouldn't...

Yeah, seems like it's worth implementing with issue #26. I'm currently returning a dictionary from the storage, which is not nice :( As I'm currently implementing the storage, the prototype...

Oh, and also to note, I'm currently implementing the storage to `enocean/storage`. As the `Device` isn't part of the protocol, in my opinion it should not go to `enocean/protocol`, so...

Thanks, I'm actually in the progress of implementing something fairly similar as part of storage (issue #26 ). I'm more likely to implement a very basic `storage.Device` at first, then...

This is most likely related to this: https://github.com/kipe/nordpool/issues/17 I guess we'll wait a day or two, just to see if it's once again a mistake. If not, I'll try and...