MindrustUK / Heatmiser-for-home-assistant

Heatmiser Neo-Hub / Neostat support for home-assistant.io
87 stars 33 forks source link

Any chance of updating Heatmiserneo #3

Closed Trouble-51 closed 4 years ago

Trouble-51 commented 5 years ago

Hi, I am using the original version for 11 thermostats. Any chance of sophisticating the project with more options that are available on the app from Heatmiser?

Trouble-51 commented 5 years ago

This is the screen shot of my Mitsubishi airco with the MELCLOUD climate.py file

Screenshot 2019-11-04 at 22 55 28
haakonstorm commented 5 years ago

Error in climate.py. Hmmm. After all, everybody is talking about massive climate change, right?

haakonstorm commented 5 years ago

Sorry, just had to.

Let me search github issues a bit on the error messages you provided and see if I can come up with something to try.

If that don't go anywhere I'm here to offer up to try and rather see if I can help one on one in some way or another, via Teamviewer, VPN or external access somehow we can get working.

I was generously helped live some time back by one of the devs behind hass-cli, when it misbehaved and should'nt have. He remoted my raspberry pi 3b+ from across the vast internets and raced her around like she had only earlier ever been driving out in fresh air once a week. On sundays. By old ladies. Hung over from pear cider. My angel raspberry woke up that day and yet as she was no longer yesterdays sweet little baby girl she was not yet a proper woman, either. The next handful of days my eyes grew dry and self-loathing by witnessing this malplaced beauty slaving my cheap IKEA light bulbs on and off, on and off and, once every single hour, overcome her fears and drag her tiny feet down to the humid cellar and give climate.py the solid kick in its libraries needed for keeping it from dozing and never wake up to get than last patch for a breaking change. Finally I manned up and did what any other true man would have done in my place, I set her free and replaced her by chaining a new raspberry pi 4b to her old prison, and flashed her SD card with a new full time engagement more fit for quenching her new and righfully awoken thirst to dip her tongue in the mysterious wells of the world wide webs. She's happy now. She was flashed with the pi-hole docker container and smiles, nods with recognition, dims my IKEA lights and turns on the lounge jazz at once any time my imac.config.VPN state turns on.

Anyways, I was about to do my bit and search for similarly themed issues here on the hub, be right back.

haakonstorm commented 5 years ago

I see now that the error message you get:

File "/config/custom_components/heatmiserneo/climate.py", line 14, in
from homeassistant.components.climate.const import (
ImportError: cannot import name 'STATE_AUTO' from 'homeassistant.components.climate.const'

implies that the climate.py version your hass is loading has to be an old version, because STATE_AUTO is not imported in the current version of this component.

I'm not very well versed in python, but I do know that there is a fair bit of caching going on. That's why I was so specific in the instructions above in order to be 100% sure to get rid of your old install and 100% sure the newest version from the repo was the only code, cached or otherwise, running on your hass. Could you please try doing the procedure as above and try again?

I might be totally wrong in any of my assumptions, but one thing is for sure and that is that hass is complaining about something this component used to ask for but no longer does.

My guess is doing the above, or at least successfully somehow getting the newest version of the component running in your hass, will get everything up and running again.

turning on the VPN

PhillyGilly commented 4 years ago

I thought I would give you an update. Herewith the new screenshot, with buttons on the thermostat card. None of the buttons are functional, and I receive the following message when I click on any of them.

Failed to call service climate/set_operation_mode

Also the boiler device which is configured as a clock still has the idle setpoint as "238".

heatmiserneo_latest

Simon, did you get anywhere with your 238 problem? I've got the same here (see below) homeautoheatmiser The two rows represent a Bedroom with a Bathroom that has electric underfloor heating and an on/off towel rail. I think that the controller on Towel Rail 2 is a neoStat-hw v1 but on Towel Rail 3 it is a v2. In an ideal world I'd like to bring the neoSat-e as Thermostats displaying the air temperature but the neoStat-hw as Binary Sensors. I'm guessing this will require a bit of work on the climate.py. Should I tackle this by detecting TIMECLOCK_MODE in [INFO] or is it a DEVICE_TYPE property?

Trouble-51 commented 4 years ago

Hi All,

Shouldn’t there be an “Idle” mode? All my thermostats show “heat” as the “state" while most of them should show “idle” because these rooms are in away mode on the Heatmiser App.

I get the same message when pushing the heat button (Failed to call etc.) and nothing happens when pushing the away and none buttons.

Thanks

On 29 Nov 2019, at 18:59, PhillyGilly notifications@github.com wrote:

I thought I would give you an update. Herewith the new screenshot, with buttons on the thermostat card. None of the buttons are functional, and I receive the following message when I click on any of them.

Failed to call service climate/set_operation_mode Also the boiler device which is configured as a clock still has the idle setpoint as "238".

https://user-images.githubusercontent.com/10942706/56982919-4f2c5b80-6b7a-11e9-86fe-dee9c9128fde.jpg Simon, did you get anywhere with your 238 problem? I've got the same here (see below) https://user-images.githubusercontent.com/56273663/69885930-9842ba80-12d7-11ea-9185-6eb581c5566e.jpg The two rows represent a Bedroom with a Bathroom that has electric underfloor heating and an on/off towel rail. I think that the controller on Towel Rail 2 is a neoStat-hw v1 but on Towel Rail 3 it is a v2. In an ideal world I'd like to bring the neoSat-e as Thermostats displaying the air temperature but the neoStat-hw as Binary Sensors. I'm guessing this will require a bit of work on the climate.py. Should I tackle this by detecting TIMECLOCK_MODE in [INFO] or is it a DEVICE_TYPE property?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MindrustUK/Heatmiser-for-home-assistant/issues/3?email_source=notifications&email_token=AGL2HVBAMUEGTD4FVQDEXBDQWFRB5A5CNFSM4GYNNFT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPNYRY#issuecomment-559864903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGL2HVDKUPLX7IFBVQMICBTQWFRB5ANCNFSM4GYNNFTQ.

Trouble-51 commented 4 years ago

Correction: when I push away on one of the thermostats all 11 thermostats go to Away Active. When I push then none on one of them, the ones that were on Standby Enabled go either to Standby Enabled again or Away Active. When I go to the app and push on AWAY and turn off “Permanently Away” the ones that were on Away Active go back to Standby Enabled.

The ones that were not on Standby Enabled before i started pushing buttons go back to heating mode, but not actually heating when the set temperature has been reached.

A bit confusing I am afraid, but i had to experiment a couple of times to actually understand what was happening.

On 1 Dec 2019, at 18:09, Jos josderaaij@gmail.com wrote:

Hi All,

Shouldn’t there be an “Idle” mode? All my thermostats show “heat” as the “state" while most of them should show “idle” because these rooms are in away mode on the Heatmiser App.

I get the same message when pushing the heat button (Failed to call etc.) and nothing happens when pushing the away and none buttons.

Thanks

On 29 Nov 2019, at 18:59, PhillyGilly <notifications@github.com mailto:notifications@github.com> wrote:

I thought I would give you an update. Herewith the new screenshot, with buttons on the thermostat card. None of the buttons are functional, and I receive the following message when I click on any of them.

Failed to call service climate/set_operation_mode Also the boiler device which is configured as a clock still has the idle setpoint as "238".

https://user-images.githubusercontent.com/10942706/56982919-4f2c5b80-6b7a-11e9-86fe-dee9c9128fde.jpg Simon, did you get anywhere with your 238 problem? I've got the same here (see below) https://user-images.githubusercontent.com/56273663/69885930-9842ba80-12d7-11ea-9185-6eb581c5566e.jpg The two rows represent a Bedroom with a Bathroom that has electric underfloor heating and an on/off towel rail. I think that the controller on Towel Rail 2 is a neoStat-hw v1 but on Towel Rail 3 it is a v2. In an ideal world I'd like to bring the neoSat-e as Thermostats displaying the air temperature but the neoStat-hw as Binary Sensors. I'm guessing this will require a bit of work on the climate.py. Should I tackle this by detecting TIMECLOCK_MODE in [INFO] or is it a DEVICE_TYPE property?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MindrustUK/Heatmiser-for-home-assistant/issues/3?email_source=notifications&email_token=AGL2HVBAMUEGTD4FVQDEXBDQWFRB5A5CNFSM4GYNNFT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPNYRY#issuecomment-559864903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGL2HVDKUPLX7IFBVQMICBTQWFRB5ANCNFSM4GYNNFTQ.

PhillyGilly commented 4 years ago

Further investigation: I've collected the JSON file sent by the heohub by copying it from my HA log, and then rearranged it into a spreadsheet showing rows for the items and columns for each device. Json.xlsx It's hard to see how the returned information is going to help determine what kind of neoStats are fitted (unless it is something that my installers did or didn't do when setting up the neoStats)

Trouble-51 commented 4 years ago

Interesting spreadsheet! Isn’t it true that a lot of the available fields are not used in the "Neostat support for home-assistant.io http://home-assistant.io/” and as it stands most of which are not needed, but some of which may make it a lot more useful? I see that only two of your devices have STANDBY as “true’ but how does that translate in the new away button. As I mentioned in my email all my 11 thermostats got to Away Active (on the iPhone app) when I press the button on one of them as opposed to STANDBY for the one I pressed. Do you have the same problem?

I don’t see an ‘idle” field in the spreadsheet, shouldn’t that be there or AUTO as it is called in the app? The app has three options AUTO, HOLD and STANDBY, it would be nice if those options were individually available for each thermostat.

I am just commenting as I am no programmer, but hopefully just giving some useful input as I have 11 thermostats.

On 2 Dec 2019, at 10:55, PhillyGilly notifications@github.com wrote:

Further investigation: I've collected the JSON file sent by the heohub by copying it from my HA log, and then rearranged it into a spreadsheet showing rows for the items and columns for each device. Json.xlsx https://github.com/MindrustUK/Heatmiser-for-home-assistant/files/3910857/Json.xlsx It's hard to see how the returned information is going to help determine what kind of neoStats are fitted (unless it is something that my installers did or didn't do when setting up the neoStats)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MindrustUK/Heatmiser-for-home-assistant/issues/3?email_source=notifications&email_token=AGL2HVBAAN3TZ3WYNBIOWFLQWTSRTA5CNFSM4GYNNFT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFTCZCY#issuecomment-560344203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGL2HVBARZSK3A7A5VZUYB3QWTSRTANCNFSM4GYNNFTQ.

PhillyGilly commented 4 years ago

Interesting spreadsheet! Isn’t it true that a lot of the available fields are not used in the "Neostat support for home-assistant.io <http://home-assistant.io/>” and as it stands most of which are not needed, but some of which may make it a lot more useful? I see that only two of your devices have STANDBY as “true’ but how does that translate in the new away button. As I mentioned in my email all my 11 thermostats got to Away Active (on the iPhone app) when I press the button on one of them as opposed to STANDBY for the one I pressed. Do you have the same problem? I don’t see an ‘idle” field in the spreadsheet, shouldn’t that be there or AUTO as it is called in the app? The app has three options AUTO, HOLD and STANDBY, it would be nice if those options were individually available for each thermostat. I am just commenting as I am no programmer, but hopefully just giving some useful input as I have 11 thermostats. On 2 Dec 2019, at 10:55, PhillyGilly @.***> wrote: Further investigation: I've collected the JSON file sent by the heohub by copying it from my HA log, and then rearranged it into a spreadsheet showing rows for the items and columns for each device. Json.xlsx https://github.com/MindrustUK/Heatmiser-for-home-assistant/files/3910857/Json.xlsx It's hard to see how the returned information is going to help determine what kind of neoStats are fitted (unless it is something that my installers did or didn't do when setting up the neoStats) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AGL2HVBAAN3TZ3WYNBIOWFLQWTSRTA5CNFSM4GYNNFT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFTCZCY#issuecomment-560344203>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGL2HVBARZSK3A7A5VZUYB3QWTSRTANCNFSM4GYNNFTQ.

Without too much in the way of computer skills, you should be able to create your own similar spreadsheet. If you add the following to your Home Automation configuration file it will start to capture the necessary data.

logger: default: warning logs: custom_components.heatmiserneo: debug

Go to Developer Tools and then select Logs. Then ask for the extended log. Be patient then it will look like this: image The info about your 11 thermostats is in the bit following json_response: Getting it into rows and columns involved a) finding and replacing comma-space with comma-cr-lf, and b) a bit of text to columns in excel. Don't leave it running like that for a long time or your log file will get unmanageable large!

Trouble-51 commented 4 years ago

I did create the spreadsheet but don't know whether it shows something that is helpful in solving the issue that all my thermostats go to standby when I press the away button on one of the 13 thermostats. JSON Jos.xlsx

ghost commented 4 years ago

Hi all

I have a heatmiser 2 channel RF receiver/switch. Will this plugin allow me to control it, well all i need is HW on and off. For CH , which heatmiser stat will work with this? If you need me to probe the receiver then tell me how to do it and what to do, and i will help.

Trouble-51 commented 4 years ago

with the latest update of Home assistant, version 0.110.1 I get the following message:

Log Details (WARNING) Logger: homeassistant.components.climate Source: components/climate/init.py:547 Integration: Climate (documentation, issues) First occurred: 13:07:04 (1 occurrences) Last logged: 13:07:04

ClimateDevice is deprecated, modify HeatmiserNeostat to extend ClimateEntity

Can you please help to solve this issue?

rosscullen commented 4 years ago

Same issue here. Any help greatly appreciated :-D

MindrustUK commented 4 years ago

Updated as per latest commit. Should resolve the issue.

Trouble-51 commented 4 years ago

Thanks very much for the speedy action. The message is gone!

MindrustUK commented 4 years ago

Closing issue. Lots of updates and this thread has become a bit of a unspecified collection of multiple issues.