Invalid config for [sensor.template]: expected dictionary for dictionary value @ data['sensors']. Got None
extra keys not allowed @ data['average_hashrate_24h']. Got None
extra keys not allowed @ data['value_template']. Got "{{ (state_attr('sensor.ethermineinfo_wallet','average_hashrate_24h') | float(default = 0)/1000000)| round(2)}}". (See ?, line ?).
Invalid config for [sensor.template]: expected dictionary for dictionary value @ data['sensors']. Got None
extra keys not allowed @ data['current_hashrate']. Got None
extra keys not allowed @ data['value_template']. Got "{{ (state_attr('sensor.ethermineinfo_wallet','current_hashrate')| float(default = 0)/1000000)| round(2)}}". (See ?, line ?).
Invalid config for [sensor.template]: expected dictionary for dictionary value @ data['sensors']. Got None
extra keys not allowed @ data['reported_hashrate']. Got None
extra keys not allowed @ data['value_template']. Got "{{ (state_attr('sensor.ethermineinfo_wallet','reported_hashrate')| float(default = 0)/1000000)| round(2)}}". (See ?, line ?).
Invalid config for [sensor.template]: expected dictionary for dictionary value @ data['sensors']. Got None
extra keys not allowed @ data['friendly_name']. Got 'unpaid'
extra keys not allowed @ data['unpaid_in_local_currency']. Got None
extra keys not allowed @ data['value_template']. Got "{{ (state_attr('sensor.ethermineinfo_wallet','unpaid_in_local_currency'))}}". (See ?, line ?).
Invalid config for [sensor.template]: expected dictionary for dictionary value @ data['sensors']. Got None
extra keys not allowed @ data['friendly_name']. Got 'paid'
extra keys not allowed @ data['paid_on']. Got None
extra keys not allowed @ data['value_template']. Got "{{ (state_attr('sensor.ethermineinfo_wallet','paid_on'))}}". (See ?, line ?).
As I understand it, this is an issue with the template, not the component (unless you count naming the component 2minersInfo, in which case it is)
Jinja/HomeAssistant is interpreting the name in the sensor instead of simply reading it as a whole. Try another method to expose attributes as sensors, this worked for me just now:
state_attr('sensor.wallet_id', 'unpaid')
The ' marks force homeassistant to read the name of the sensor as it is written, instead of trying to interpret the name, and that’s where things are getting messy.
If this works, pleas let me know and I’ll update the documentation.
I will try to make something similar to this Topic in order to replace what was done with ETH in ethermine but with 2miners, I’ll try to have a look to Flexpool also but since I’m mining on 2Miners…
Hello, delighted Thomas, I’m trying to modify your code base to be able to implement firo in 2miners. Change the api address from zxc to firo.2miners. since it was outdated and an infinite number of things. But I can’t get it to work. Could you help me get firo working at 2miners.com Thank you very much. PS any advice would also help me