openweather plugin ?

[Crille]

@ronluna I thought so as well. That’s why I thought any device configured as a thermostat in homebridge would have the same characteristics and your plugin would support it.
My “thermostat” is another homebridge plugin for MELCloud (Mitsubishi cloud for my WiFi connected inverters).

Here is the json response:

luup_log:17: homebridge2openluup debug: concat_response_body 1 = {"aid":60,"iid":8,"uuid":"0000004A-0000-1000-8000-0026BB765291","type":"Thermostat","humanType":"Thermostat","serviceName":"Övervåningen","serviceCharacteristics":[{"aid":60,"iid":10,"uuid":"0000000F-0000-1000-8000-0026BB765291","type":"CurrentHeatingCoolingState","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Heating Cooling State","value":1,"format":"uint8","perms":["pr","ev"],"maxValue":2,"minValue":0,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":11,"uuid":"00000033-0000-1000-8000-0026BB765291","type":"TargetHeatingCoolingState","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Heating Cooling State","value":1,"format":"uint8","perms":["pr","pw","ev"],"maxValue":3,"minValue":0,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":12,"uuid":"00000011-0000-1000-8000-0026BB765291","type":"CurrentTemperature","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Temperature","value":23,"format":"float","perms":["pr","ev"],"unit":"celsius","maxValue":100,"minValue":0,"minStep":0.1,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":13,"uuid":"00000035-0000-1000-8000-0026BB765291","type":"TargetTemperature","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Temperature","value":22,"format":"float","perms":["pr","pw","ev"],"unit":"celsius","maxValue":38,"minValue":10,"minStep":0.1,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":14,"uuid":"00000036-0000-1000-8000-0026BB765291","type":"TemperatureDisplayUnits","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Temperature Display Units","value":0,"format":"uint8","perms":["pr","pw","ev"],"maxValue":1,"minValue":0,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":15,"uuid":"00000029-0000-1000-8000-0026BB765291","type":"RotationSpeed","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Rotation Speed","value":60,"format":"float","perms":["pr","pw","ev"],"unit":"percentage","maxValue":100,"minValue":0,"minStep":1,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":16,"uuid":"0000006C-0000-1000-8000-0026BB765291","type":"CurrentHorizontalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Horizontal Tilt Angle","value":0,"format":"int","perms":["pr","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":17,"uuid":"0000007B-0000-1000-8000-0026BB765291","type":"TargetHorizontalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Horizontal Tilt Angle","value":0,"format":"int","perms":["pr","pw","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":true,"ev":true},{"aid":60,"iid":18,"uuid":"0000006E-0000-1000-8000-0026BB765291","type":"CurrentVerticalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Current Vertical Tilt Angle","value":-45,"format":"int","perms":["pr","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":false,"ev":true},{"aid":60,"iid":19,"uuid":"0000007D-0000-1000-8000-0026BB765291","type":"TargetVerticalTiltAngle","serviceType":"Thermostat","serviceName":"Övervåningen","description":"Target Vertical Tilt Angle","value":-45,"format":"int","perms":["pr","pw","ev"],"unit":"arcdegrees","maxValue":90,"minValue":-90,"minStep":1,"canRead":true,"canWrite":true,"ev":true}],"accessoryInformation":{"Manufacturer":"Mitsubishi","Model":"Default-Model","Name":"Övervåningen","Serial Number":"1805118279","Firmware Revision":"0.3.4"},"values":{"CurrentHeatingCoolingState":0,"TargetHeatingCoolingState":0,"CurrentTemperature":0,"TargetTemperature":10,"TemperatureDisplayUnits":0,"RotationSpeed":0,"CurrentHorizontalTiltAngle":-90,"TargetHorizontalTiltAngle":-90,"CurrentVerticalTiltAngle":-90,"TargetVerticalTiltAngle":-90},"instance":{"name":"homebridge","username":"CC:22:3D:E3:CE:43","ipAddress":"127.0.0.1","port":51826,"services":[],"connectionFailedCount":0},"uniqueId":"8f37721c51dc9fd6b15aad7024d6a8460038b1ee7e6fb23c732f1abc5bcfb8fd"}

[ronluna]

@crille Please test the latest commit on github.

[Crille]

@ronluna Sorry, but it does not work.

I believe the MELCloud plugin only accepts "TargetTemperature" for changing Setpoint

luup_log:17: homebridge2openluup debug: response_body PUT 1 = {"statusCode":400,"message":"Invalid characteristicType. Valid types are: 'TargetHeatingCoolingState', 'TargetTemperature', 'TemperatureDisplayUnits', 'RotationSpeed', 'TargetHorizontalTiltAngle', 'TargetVerticalTiltAngle'.","error":"Bad Request"}

and not

luup.variable_set:: 18.urn:upnp-org:serviceId:TemperatureSetpoint1_Heat.CurrentSetpoint was: 22 now: 18 #hooks:0

This is only if you want to support the MELCloud provisioned thermostat, otherwise do not put to much energy in to it.

For me it would be at great way to control my temperature triggered by house modes since there is no MELCloud plugin for openLuup.

[ronluna]

@crille said in Homebridge to Openluup:

TargetTemperature

That's characteristicType the plugin is trying to set for your plugin. Can your share what are the Manufacturer, Model and Type variables set to?

[Crille]

@ronluna Ok, maybe I'm not understanding the logs correct then

[ronluna]

@crille are you certain you are using the latest L_Homebridge2openluup1.lua from github?

line 813 should read:

elseif thermostatManu == "Mitsubishi" and thermostatModel == "Default-Model" then -- FOR Mitsubishi

[Crille]

@ronluna Yes, but I think I found the issue.
I uploaded to /cmh-ludl/files/ first install and manual update but the AltAppstore version runs from /cmh-ludl?
where I get a permission denied when trying to replace the files.

[akbooer]

That looks like a permissions issue due to the folder structure having been created undera different user from the one that you're running under now. A quick fix should be to open up the permissions in that folder tree.

[ronluna]

@akbooer just to be sure. Plugin files that resides in "cmh-ludl/" have a higher priority then "cmh-luld/files" right? in case the plugin was manually transferred but later installed from the AltUI app store and the user forgot to delete the plugin's file in "cmhd-ludl/files"

[akbooer]

@ronluna said in Homebridge to Openluup:

Plugin files that resides in "cmh-ludl/" have a higher priority then "cmh-luld/files" right?

Here's the ground truth on search path order lifted straight from the openLuup file loader...

  local f = open "openLuup/"        -- 2016.06.18  look in openLuup/ (for AltAppStore)
    or open "./"                    -- current directory (cmh-ludl/) 
    or open "../cmh-lu/"            -- look in 'cmh-lu/' directory
    or open "files/"                -- 2016.06.09  also look in files/
    or open "www/"                  -- 2018.02.15  also look in www/
    or open ("built-in/", vfs)      -- 2019.05.29  also look in built-in/ for 'last chance' files

[Crille]

Yes, changing owner and updating files in cmh-ludl/ solved it all. It's working great now! Thank you @akbooer and @ronluna
Only issue now is renaming a device, the name is reset to THERMOSTAT_uuid on luup reload.

[ronluna]

@crille said in Homebridge to Openluup:

THERMOSTAT_uuid

That's odd... It shouldn't do that...

is your deviceList Variable ending with a semicolon ";" after your uuid ?

[Crille]

@ronluna I only mapped 2 devices with

T:uuid,uuid

also tried

T:uuid,uuid;

[ronluna]

@crille I've been renaming renaming devices on my end without experiencing what you are describing. Are both Mitsubishi thermostat? Do you mind sharing an entire log output after an engine reload, additional 5 second log for the first device've value refresh and log output while rename a homebridge device from within openluup?

[Crille]

@ronluna Yes, both are provisioned by the same plugin and is of same physical model.

All those logs is too long to post or PM. My guess is that the luup.chdev.append overwrites the name.

2021-03-25 12:04:20.863   openLuup.scheduler:: [23] Homebridge2openLuup device startup
2021-03-25 12:04:20.863   luup_log:23: homebridge2openluup debug: luaStartUp running
2021-03-25 12:04:20.863   luup_log:23: homebridge2openluup debug: 0 --> Connected
2021-03-25 12:04:20.863   luup.variable_set:: 23.urn:ctrlable-com:serviceId:homebridge2openluup1.Connected was: 1 now: 0 #hooks:0
2021-03-25 12:04:20.863   luup_log:23: homebridge2openluup debug: 0.1 --> PluginVersion
2021-03-25 12:04:20.863   luup_log:23: homebridge2openluup debug: http://127.0.0.1:8581/ --> homebridgeURL
2021-03-25 12:04:20.863   luup_log:23: homebridge2openluup debug: DeviceList Values = T:bc2e86fa8031082fd9d44cd9baf66c5dfd56b96165eae2b7fc26f4314230bf7f,8f37721c51dc9fd6b15aad7024d6a8460038b1ee7e6fb23c732f1abc5bcfb8fd;
2021-03-25 12:04:20.863   luup.chdev.append:: [bc2e86fa8031082fd9d44cd9baf66c5dfd56b96165eae2b7fc26f4314230bf7f] THERMOSTAT_bc2e86fa8031082fd9d44cd9baf66c5dfd56b96165eae2b7fc26f4314230bf7f
2021-03-25 12:04:20.863   luup.chdev.append:: [8f37721c51dc9fd6b15aad7024d6a8460038b1ee7e6fb23c732f1abc5bcfb8fd] THERMOSTAT_8f37721c51dc9fd6b15aad7024d6a8460038b1ee7e6fb23c732f1abc5bcfb8fd
2021-03-25 12:04:20.863   luup.chdev.sync:: [23] Homebridge2openLuup, syncing children
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: URL request result: r = 1
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: URL request result: c = 201
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: URL request result: h = table: 0x55af4d7c10b0
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: response_body 1 = {"access_token":"XXXXX","token_type":"Bearer","expires_in":28800}
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: Returned web page data is : {"access_token":"XXXXX","token_type":"Bearer","expires_in":28800}
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: XXXXX --> access_token
2021-03-25 12:04:20.866   luup.variable_set:: 23.urn:ctrlable-com:serviceId:homebridge2openluup1.access_token was: XXXXX now: XXXXX #hooks:0
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: Bearer --> token_type
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: response_body_parse access_token = XXXXX
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: response_body_parse token_type = Bearer
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: response_body_parse expires_in = 28800
2021-03-25 12:04:20.866   luup_log:23: homebridge2openluup debug: 1 --> Connected

[ronluna]

@crille said in Homebridge to Openluup:

luup.chdev.append

I'm really puzzled by this... Your logs looks just fine... The devices should not get renamed back when luup.chdev.append runs . if the devices where getting re-created the engine should be getting reloaded right away... What openluup version are you running?

Wondering if @akbooer sees something weird in how the plugin is syncing the devices after the append runs that could be causing it... at line 601 of L_Homebridge2openllup1.lua as it is something I'm not experiencing on my end... and I'm not sure where else to look...

[Crille]

@ronluna I'm running the openLuup version from development branch 2021.03.25b
So your log says THERMOSTAT_uuid as well on the luup.chdev.append? If so I'm guessing wrong
Is there any possibility to set the name from homebridge since it's picking up serviceName in startup?

2021-03-26 13:47:13.306   luup_log:23: homebridge2openluup debug: homebridgeGetDevices91 = uniqueId bc2e86fa8031082fd9d44cd9baf66c5dfd56b96165eae2b7fc26f4314230bf7f Type : Thermostat serviceName : Källaren
2021-03-26 13:47:13.306   luup_log:23: homebridge2openluup debug: homebridgeGetDevices92 = uniqueId 8f37721c51dc9fd6b15aad7024d6a8460038b1ee7e6fb23c732f1abc5bcfb8fd Type : Thermostat serviceName : Övervåningen

Otherwise I can live with the default name, your great plugin is doing what I needed and is intended to operate in automations in the background for my implementation of it anyway.

[akbooer]

@ronluna said in Homebridge to Openluup:

Wondering if @akbooer sees something weird in how the plugin is syncing the devices

I've not been following this discussion (although I am about to install Homebridge in a Docker to give it a whirl.)

Can you briefly summarize the issue?

[ronluna]

@crille currently the plugin relies on an initial manual configuration and the current mechanism creates the children in a very dumb way. It is possible to build a more sophisticated interface although the plugin still in a "proof of concept state".

Yes, the devices are named DeviceType_UUID by default when they are created for the first time but after that I can rename them any way I want and the names remain persistent after engine reloads.

My understanding is that once a device is renamed on your setup it will get renamed back to the default deviceType_uuid after the engine reloads right? and that's what I can't replicate on my end.

[ronluna]

@akbooer apparently on @Crille environment renaming plugin's children are not persistent after the engine reloads. although I can't replicate it on my end.