Skip to content
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

Enhacement: Internal temperature Home Assistant discovery #1188

Closed
f-vicente opened this issue Apr 22, 2024 · 7 comments
Closed

Enhacement: Internal temperature Home Assistant discovery #1188

f-vicente opened this issue Apr 22, 2024 · 7 comments
Labels
enhancement New feature or request

Comments

@f-vicente
Copy link

Describe the bug
An enhacement related with #1125

Will be great a flag that enables the internal temperature to be published, and generates the appropriate HASS discovery.

At this moment you need to create the timmer to publish the variable value (like shown on #1125), then create the appropriate sensor manually in home assistant. Will be great if this could be automated.

Firmware:

  • Version 1.17.553
  • Chip/model: BK7231N
@openshwprojects openshwprojects added the enhancement New feature or request label Apr 23, 2024
@openshwprojects
Copy link
Owner

Sure, it's planned and I can add it for you, but first, are you aware that this internal temperature is not a perfect measurement and should not be really relied upon? As far as I know it' even has serious issue on one of the platforms. The fix is still pending.

@f-vicente
Copy link
Author

Great!

Yes I know that the sensor is very inaccurate, but I like to have statistics about it, and use the values to trigger alarms if they get very high values that could reflect any problem. I only have bk7231n devices and those seem to work reasonably fine.

@f-vicente
Copy link
Author

Thanks for adding it.

@pablacho
Copy link

Hi! I am on the latest version of OpenBK7231T. I have re-discovered all my devices to add the new sensors, but they only update on restart! should I add repeating events for each sensor? what are their variable names? I am asuming $intTemp should go to topic 'temp', (so running "addRepeatingEvent 300 -1 publishFloat temp $intTemp" should do the trick), but what are the others?

@f-vicente
Copy link
Author

Hi! I am on the latest version of OpenBK7231T. I have re-discovered all my devices to add the new sensors, but they only update on restart! should I add repeating events for each sensor? what are their variable names? I am asuming $intTemp should go to topic 'temp', (so running "addRepeatingEvent 300 -1 publishFloat temp $intTemp" should do the trick), but what are the others?

I haven’t done anything in special, just update and the new sensors appeared.

@pablacho
Copy link

pablacho commented May 29, 2024

Hi! I am on the latest version of OpenBK7231T. I have re-discovered all my devices to add the new sensors, but they only update on restart! should I add repeating events for each sensor? what are their variable names? I am asuming $intTemp should go to topic 'temp', (so running "addRepeatingEvent 300 -1 publishFloat temp $intTemp" should do the trick), but what are the others?

I haven’t done anything in special, just update and the new sensors appeared.

do they update every now and then? Mine stay the same (14mins and counting), I am checking the MQTT log but no messages arrive. I have also tried running the command I suggested but the info goes to <dev_topic>/temp/get instead of <dev_topic>/temp so HA ignores it...

@f-vicente
Copy link
Author

Hi! I am on the latest version of OpenBK7231T. I have re-discovered all my devices to add the new sensors, but they only update on restart! should I add repeating events for each sensor? what are their variable names? I am asuming $intTemp should go to topic 'temp', (so running "addRepeatingEvent 300 -1 publishFloat temp $intTemp" should do the trick), but what are the others?

I haven’t done anything in special, just update and the new sensors appeared.

do they update every now and then? Mine stay the same (14mins and counting), I am checking the MQTT log but no messages arrive. I have also tried running the command I suggested but the info goes to <dev_topic>/temp/get instead of <dev_topic>/temp so HA ignores it...

Yes, the update as expected.

I have experienced the issue on one of them, it didn’t show anything, but it was fixed when I disconnected from power and connected again. I have a few devices that always give me those kind of errors after the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants