Request: Access to Alterative Attributes within a Sensor Field

[Dukat-Gul]

I am curious to understand how to access some of the alternative Attributes

For example;

Attributes:

UpperQuantity
TotalPercentageUsed
TotalCharge
TotalAdditionalCharge
TotalDataUsed
TotalDataRemaining
UnitType
IsFinal
IsRechargeRequired
UpperQuantityDisplay
TotalDataUsedDisplay
TotalDataRemainingDisplay
IsThrottled
DataUsedThisDevice
DataUsedThisDeviceDisplay
PercentageUsedThisDevice
DataUsedOthers
DataUsedOthersDisplay
PercentageUsedOthers
Trusted
SingleService

I attempted to adjust myself by editing the /config/custom_components/optus/sensor.py file
specifically I adjusted optus_sharedtierdatausage section where it was listed as ;

    def get_value(self, ftype):
        if ftype == "state":
            if self.sensor == "daysRemaining":
                return self.coordinator.data[self.sensor]
            elif self.sensor == "smsUsage":
                return self.coordinator.data[self.sensor]["amount"]
            elif self.sensor == "mmsUsage":
                return self.coordinator.data[self.sensor]["amount"]
            elif self.sensor == "tierVoiceUsage":
                return self.coordinator.data[self.sensor]["totalCharge"]
            elif self.sensor == "tierDataUsage":
                return self.coordinator.data[self.sensor]["totalDataUsed"]
           elif self.sensor == "sharedTierDataUsage":
                return self.coordinator.data[self.sensor]["totalDataUsed"]
                #return self.coordinator.data[self.sensor]["DataUsedThisDeviceDisplay"]

The last line is commented out now, but its what I tried and it didnt work, and the entry just showed up with Unknown for its values.

[smarthomesydney]

@Dukat-Gul Did you get anywhere with adding additional attributes in the end?

Looks like @itchannel has more than likely moved to Telstra and dropped the project

[itchannel]

@smarthomesydney I've stopped development of this integration at the moment because after the Optus hack they restructured how their oauth flow works. To the point where my phone barely ever logs in to My Optus even on a good day. So it has made debugging and fixing this very hard. Given that barely anyone uses this integration I've put it on the back burner for now.

[smarthomesydney]

@itchannel Understand mate.
They have put 2FA in there via SMS.
If your having issues uninstall the app on Android anyway. Restart phone and install again. That worked for me,now it doesn't ask for 2fa every time. 👍

Happy to test for you if you have the time to revisit. Especially with NBN etc also there and shared data etc. 🤟

[itchannel]

@itchannel Understand mate. They have put 2FA in there via SMS. If your having issues uninstall the app on Android anyway. Restart phone and install again. That worked for me,now it doesn't ask for 2fa every time. 👍

Happy to test for you if you have the time to revisit. Especially with NBN etc also there and shared data etc. 🤟

I'll have a look. I can make it work by capturing the bearer token from the app. However this wouldn't be practical for most users so will try and deconstruct the oauth v3 flow they now use at some point this week.

[itchannel]

They now use Akamai sensor data generated on the device/mobile application when authenticating against the initial oauth endpoint "/api/identity/moa/v2/oauth/token". Which makes it very hard to bypass short of me disassembling the application and working out what data endpoints are used. Which would violate CMA.

The only way I can see around this would be to login via the mobile app, then capture the refresh token using a proxy and then use that token inside the HA integration which should then theoretically keep working until the user signs out of the mobile application. However this isn't really practical for 99% of people.

[smarthomesydney]

That should be easy enough if we login via desktop chrome and have developer tools open. right? pull the token from the network tools header

or is mobile app unique from website?