-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSS3110 Energy is UTC #36
Comments
Hey @lclc98, |
Update: I'm planning to add the ability to correctly set the device timezone in my code anyway, since when your devices are 'off' the meross infrastructure you'll have no easy way to adjust it. |
I looked at the traces file, it seems like the timezone isn't set on my device, I will see if I can set it manually |
I was able to sit down and look through your code and others. Setting only timezone didn't work for me, I also had to set a variable called "timeRule". TimeRule is explained here, https://github.com/arandall/meross/blob/master/doc/protocol.md#appliancesystemtime Meross does have an endpoint for it /v1/Rule/getTimeRuleByTz with the param "tz", but as this is a lan plugin, that probably won't work. |
Thank you very much: this is a very interesting info. |
UPDATE: |
Hi @krahabb, I'm using a mss310 switch to monitor the power usage of my server and was going to report the same midnight issue reported here. Mine wasn't as obvious either as Irish summer time is only 1 hour off UTC and after you pushed the last version I went to the integration configuration for that device and set the device time zone to "Europe/Dublin" and thought that would be it. I checked again now a week later and the graph is still showing a 1 hour gap from midnight to 1am with 0 increase in energy consumed even though the server has a pretty steady consumption. Did I misunderstand/misconfigure the device or should it be working like this? Thanks, |
Hey @markuskorbel , See you! |
Hello @markuskorbel ,
|
Hi @krahabb ,
I did notice however that the other plug monitoring my desktop computer doesn't have the hour gap from 00:00-01:00, both were set to the same timezone setting. I didn't check the desktop that often as it often isn't running around that time whereas the server obviously is. I have re-set the timezone on the server plug to see if it fixed it. Ah, maybe found something else just before posting this: there is a hardware/firmware difference between the two switches. The one that seems to work correctly is a mss310 2.0.0, fw 2.1.14 Not sure what differences you encountered when it comes to these two generations of devices, but I might just switch out the server plug with another 2.0.0 switch from a device I don't care about recording the power consumption of. |
Hello @markuskorbel , I'll have a look at the logic of 'midnight-energy-timezone-roundtripping' and see if I could patch it in software (this was my original intention before knowing this: #36 (comment)) but this could take some time..I'm leaving for a couple of days so I'd expect to 'push' something by the end of the week |
Version of the custom_component
Master branch
Describe the bug
I am currently using an MSS310, it seems that home assistant is looking for the next day after midnight, but due to the device using UTC for "Appliance.Control.ConsumptionX", it seems to miss out on the first 10 hours of my day (UTC+10). I haven't had the time to look into the code to see where the problem is caused, but I have noticed it is still going up using MQTT to listen.
The text was updated successfully, but these errors were encountered: