-
Notifications
You must be signed in to change notification settings - Fork 16
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
TrueComfort / Device discovery #205
Comments
Hi, |
Hi Claude
Thanks for your reply. The model number is indeed different. I will try to
add the value and let you know if it works.
I changed the host in init file to make it connect to truecomfort with
success.
Have a great one
Pier-Paul Levesque
***@***.***
…On Thu, Jan 18, 2024 at 09:39 Claude Gelinas ***@***.***> wrote:
Hi,
If the login address is different maybe I can set a parameter in the
neviweb130 config with fefault to neviweb.com but with the possibility to
change it to truecomfort.neviweb.com.
Next if the device is not discovered it is because the model number is
different. neviweb130 need the device model number to discover the device.
So can you go to truecomfort.neviweb.com and check in the info section of
your thermostat to get the model number I'll add it to the floor
thermostats group. Also I will probably need some more info once the device
is discovered as it is possible that some parameter are not available or
have a different name in truecomfort.neviweb.com.
I'll be out until 4 pm so tonight I can make a fix for your device if I
get the information.
—
Reply to this email directly, view it on GitHub
<#205 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIOGGBIW2NAMSSDMZZ4UYPDYPEX35AVCNFSM6AAAAABB7SU7XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGYYDMNZWG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
What is the model number of that thermostat. I'm gonna create an account with truecomfort.neviweb.com to see how it work compared to neviweb.com |
Look like it is a Flextherm FLP55 which is already supported in Neviweb130. Model 738 |
Hi Claude
The model that I bought is named PS120-240WF but inside the device, there
is a sticker indicating Sinope TH1310WF. This is the same device but
probably flashed with an image from Stelpro.
When browsing on the TrueComfort mobile app which is truecomfort.neviweb.com,
the model number shown for this device is
True Comfort Inc PS120_240WF
As a difference, Sinope seems to support HomeKit locally but this one isn’t
discovered and doesn’t have a QR code to add it directly to Apple Home.
Pier-Paul Levesque
***@***.***
…On Thu, Jan 18, 2024 at 22:53 Claude Gelinas ***@***.***> wrote:
Look like it is a Flextherm FLP55 which is already supported in
Neviweb130. Model 738
—
Reply to this email directly, view it on GitHub
<#205 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIOGGBK7WH64Q333DUKT2XDYPHUZZAVCNFSM6AAAAABB7SU7XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJZGY2TCMBRGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi Claude i cannot find where to add a product matching to see if my device from True Comfort can be managed. Is there a way to pull the api response data and add the corresponding string to model 738. The device is indeed similar. |
In the js code of truecomfort.neviweb.com I can see this
|
Hi,
I just bought the Wifi Floor thermostat Stelpro TrueComfort PS120/240 which is a Sinopé TH1310WF under the hood. The only diffrence I've noted it that they target a diffrent host which is truecomfort.neviweb.com.
I've setup the custom_component, I can see that the component is able to login successfully and match the location in Home Assistant logs but no integration/device/entities gets discovered afterwards.
How could I force the discovery process?
The text was updated successfully, but these errors were encountered: