You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest that you look to improve the usability (processability) of the battery data for batteries attached to the Solarflow hubs.
Today you send all battery parameters as a jason formatted string in the parameter "packData".
The form that you send this information in is extremely difficult to process if you only have simple processing tools availble to you (e.g. blocky scripts in IOBroker). Although I have managed to build a working solution based on the data currently received it is not idea/efficient and requires a load of "unnecessary" code to be written and maintained.
The biggest issues I come across are:
The elements sent in the JSON text are in random order - sometime battery 1 and then battery 2, other times battery 2 then battery 1, other time just one of the batteries.
The battery can only be identified by its serial number - meaning you somehow need to know and code which battery has which serial number.
You never get a full set of values sent - only the changed values are sent with each update. Sometime you only get the serial number sent for a battery and no other values which is very strange
I fully appreciate the way/reasoning behind how you have built the interface today, and the fact that only changed vaues are generally sent in order to reduce the traffic bandwith. However, it would help me (and probably a lot of other users) if you could make some simple, but effective, changes in respect to the sending of the Battery information.
I would like to see:
Separate paramters for each of the individual batteries. By this I mean instead of seding everything mixed up in a single PackData field you replace (or supplement) this with individual fields for each battery. That means you would have 4 extra/new fields such as battery1Data, battery2Data, battery3Data and battery4Data. The 1,2,3,4 should match the battery assignment in the App.
Secondly, every few minutes send the full set of values and not just the changed ones (requested also in one of my other tickets) as its important to be able to resync the data every so often.
Thanks for considering my request for one of the next releases.
Peter.
The text was updated successfully, but these errors were encountered:
ppitkin
changed the title
Suggestion fro improvement on the Solarflow feed.
Suggestion for improvement on the Solarflow feed.
Mar 19, 2024
I would like to suggest that you look to improve the usability (processability) of the battery data for batteries attached to the Solarflow hubs.
Today you send all battery parameters as a jason formatted string in the parameter "packData".
The form that you send this information in is extremely difficult to process if you only have simple processing tools availble to you (e.g. blocky scripts in IOBroker). Although I have managed to build a working solution based on the data currently received it is not idea/efficient and requires a load of "unnecessary" code to be written and maintained.
The biggest issues I come across are:
I fully appreciate the way/reasoning behind how you have built the interface today, and the fact that only changed vaues are generally sent in order to reduce the traffic bandwith. However, it would help me (and probably a lot of other users) if you could make some simple, but effective, changes in respect to the sending of the Battery information.
I would like to see:
Separate paramters for each of the individual batteries. By this I mean instead of seding everything mixed up in a single PackData field you replace (or supplement) this with individual fields for each battery. That means you would have 4 extra/new fields such as battery1Data, battery2Data, battery3Data and battery4Data. The 1,2,3,4 should match the battery assignment in the App.
Secondly, every few minutes send the full set of values and not just the changed ones (requested also in one of my other tickets) as its important to be able to resync the data every so often.
Thanks for considering my request for one of the next releases.
Peter.
The text was updated successfully, but these errors were encountered: