Updated to 0.92.0
Integration Manifest.
Cheers,
us
Updated to 0.92.0
Integration Manifest.
Cheers,
us
I renamed to ācustom_components/beokā and changed to āplatform: beokā in the climate.yaml but got the following config error:
āIntegration beok not found when trying to verify its climate platform.ā
Renaming or removing the broadlink.py from the new beok folder made no difference either.
@ clementTal , thks for your work and this fantastic component
I was trying to use the āset_scheduleā, so I check the file ā/srv/homeassistant/lib/python3.5/site-packages/BroadlinkWifiThermostat/init.pyā
and I see that the ātempā only has two posible values (āhome_tempā / āaway_tempā), could be possible to set individual values for ātempā for each diferent parameter(week_start_1, week_stop_1ā¦ week_stop_3 ā¦ weekend_stop)?
In that way we could select differents periods with different temperatures for each period.
Sorry if this is a nosense, unfornutaley iām not good at python.
custom_components/beok/climate.py not broadlink.py.
Now the name of the py file has to be the domain : switch, climate, media_player ā¦
I also have a __init.py__ that contains DOMAIN = ābeokā but it shouldnāt be needed
Thanks, but itās still not working.
I have custom_components/beok with the following inside:
init.py
climate.py
Is there an updated link to Clementalās code, or is there another version someone else has made to replace it, or do I need to modify the contents of the climate.py or something?
Iām confused - it just should work.
Could you try this?
I have just bought one of these thermostats, and am wondering if the PR is ever going to make it to release, or if I should just install as a custom component?
I hope iāll find time to finish it, taking care of every review from the community and every returns from this topic. Should be done within the month
Brilliant,
Iām not in a hurry to add a custom component then if its only going to be a month. I have plenty of other things to sort out in the mean time
Thanks
Ben
Iām using the latest code from post #174. Nothing more.
Hello Guys,
would this compoment work also with this thermostat ?
Since updating to 92.2 itās working again for me
Me too but itās not working for me
Itās strange- Iām using the latest code I have the entry in my configuration.yml - yet no errors in logs, successful loading of the component, doesnāt show in the entity list
It looks like what I had in 0.92, thatās why I tried 0.91.4. (coming directly from 0.86 !)
0.92 has major change in the Broadlink component, maybe itās the cause and the 0.92.2 solved that ? I guess there were changes in the library before, my SC1 became unreliable lately. I may try 0.92.2 soon.
Hi, I have the same problem but canāt find the relevant portion in the climate.py. Did you manage to solve this yet?
Thanks
Thanks,
I have an error climate.broadlink platform not found
And Works for me in version 0.92.2 and 0.93 , rename broadlink folder to beok and in configuration.yaml change platform: broadlink to beok
Thnks
That good news. Iām running 0.92.2 āonlyā, will be upgrading to 93 soon.
Have you created a manifest.json and did you add the āDOMAINā directive in the __init.py__ ? Iām still not sure if theyāre needed and what for !!
Not necesary for me do it, I only update version broadlink.py of march '19 and rename to beok and work fine