Thank you very much @GBoulvin !! Let’s see if this suits @pierre-gilles for the release !!
Is it still being debated? I thought it was settled… ![]()
Shall we bring it up again? ![]()
Hi @Terdious!
I’m coming back to this topic because I managed to tinker with the ‹ Aubess 16A Power Monitoring Plug › to get it running Tasmota.
I was therefore able to successfully test the changes you made to the Tasmota integration.
Can’t wait for the release ![]()
Hi everyone ![]()
Before I went on vacation
Hi @pierre-gilles,
The most recent, more comprehensive tests were positive.
If I’m not mistaken, we were just missing your approval for the PR…
This comment by @AlexTrovato from July 16 is unanswered: Add features energy on Tasmota devices, fixes features on server and fixes i18n units energies front by Terdious · Pull Request #1526 · GladysAssistant/Gladys · GitHub
The question was: what about migrating the existing data that isn’t in the correct format?
I had replied on this point and run the tests. It’s only me, indeed, but I didn’t encounter any issues.
I’ll retest and get back to you in an hour… Just a substitution of my production DB, is that correct?
@GBoulvin,
Install the device in your prod database, copy them to the test database and check how it looks as-is. See if the device still works and if the data on the dashboard is consistent with before.
Then go into the integration and update your device. Normally you should find everything as before but with the correct voltage in particular.
Also check the scenes too; I don’t know if there was an update affecting the decimals, but the value will necessarily not be the same since it was poorly stored before (mV instead of V).
@pierre-gilles if you can confirm that this is enough to validate. Thanks in advance.
There, tested, all approved.
The value I’m tracking on the dashboard, the voltage, automatically displayed in volts, finally correctly.
In the integration, a single click on ‹ update › was enough to go from 4 available values to, uh, I forgot to count but at least 9, with all values and units correct.
In the scenes, I indeed couldn’t use the voltage because 0.234 V was displayed.
In the graphs… Darn, I didn’t think to go check…
I was referring to this message from @AlexTrovato:
Currently in the PR there are no database migrations to fix the data already entered in the DB with the wrong format, so someone who adds this type of device ends up with « hybrid » data, and on their sensor charts it’s wrong (there will be a jump between before and after, right?)
What do you think?
My bad,
In this case I’ll look into doing that!! Indeed, I didn’t intend to touch the old data but for the graphs it might indeed be necessary ^^
The code that @AlexTrovato proposed is very good
You just need to add a concurrency to Promise.map as I suggested in the PR, and that should do the job. Test it afterwards!
Hello!
Another resurrected thread, I’m afraid…
Is @pierre-gilles’s last comment really a blocker?
Indeed, the improvements proposed here would really be welcome…
I’m still up for doing tests if needed!
Hi @GBoulvin! Indeed it’s old, the PR was even closed by the Stale Bot due to inactivity.
There may have been a small communication issue about the status of the PR.
The best would be to reopen the PR + rebase onto the current master + rebuild the Docker image + test this build in a real environment.
Hello !! I’m following up on this topic !! Thank you very much to @VonOx and @AlexTrovato for following the PR.
@GBoulvin, if I set up a Docker image, will you be able to test?
I’ve updated the branch and made a few changes. I’ll push it later today.
Docker image for the PR: docker pull terdious/gladys:tasmota-POW-R2-features-fixes
[https://hub.docker.com/layers/terdious/gladys/tasmota-POW-R2-features-fixes](https://hub.docker.com/layers/terdious/gladys/tasmota-PO
Quick off-topic, what do you use to measure the pH of your pool?
iopool probe !! + Bluetooth/wifi module + Node-Red
[Probe + Gateway](Analyseur d’eau - Sonde connectée Piscine et Spa Premium - EcO Start and Connect - Pack Comprenant sonde, Relais Wi-F
Ok thanks!
Wi‑Fi isn’t for me; I’ll wait for a manufacturer to adopt Zigbee! ![]()
